C100DBA MongoDB Associate Database Administrator(Based on MongoDB 6.0 and 7.0+) Questions and Answers

logLevel is a MongoDB server parameter, and server parameters are retrieved through the administrative getParameter database command. The documented and unambiguous mongosh form is db.adminCommand({ getParameter: 1, logLevel: 1 }), which executes the command against the admin database and requests the current value of logLevel. The first numeric value activates the command, while the logLevel field identifies the parameter to return. Options B and C refer to a db.getParameter() helper that is not the documented interface. Option A uses db.runCommand() without explicitly switching to the admin database. Because getParameter is an administrative command, db.adminCommand() is the correct and reliable form among the choices. Administrators use server parameters to inspect and, where supported, tune aspects of mongod or mongos behavior. logLevel controls global diagnostic verbosity, while component-specific verbosity can be managed through the logging configuration. For this question, option D precisely matches the expected administrative syntax. Checking the current value before changing logging settings is also a sound operational practice during troubleshooting.

Study Guide reference/topic:Performance Monitoring and Tuning - runtime server parameters, logging configuration, and getParameter.

===========

A hidden index remains physically present and continues to be maintained as documents are inserted, updated, or deleted, but the query planner does not consider that index when choosing normal execution plans. This makes hidden indexes especially useful for safely testing whether an index can be removed. An administrator can hide the index and observe production query behavior as though the index were absent. If performance or plan quality degrades, the index can be unhidden immediately without rebuilding it because MongoDB has continued to maintain it in the background. Option A is incorrect because a hidden index is still an index and is not simply removed from index statistics. Option B is also incorrect; hiding an index can actually force collection scans or alternative plans if that index was previously important. Option D misunderstands the feature entirely: hiding an index has no effect on document visibility. Hidden indexes are therefore a risk-reduction mechanism for index lifecycle management, especially before dropping an index in a production environment. Option C accurately states that purpose.

Study Guide reference/topic:Indexing and Query Optimization - hidden indexes, query planner behavior, and safe index-removal testing.

===========

The grantPrivilegesToRole command requires privileges to be an array of privilege documents. Each privilege document must contain a resource document and an actions array. Option A uses exactly that structure: the resource targets testDB with an empty collection name, which represents the database-level collection scope used by MongoDB ' s privilege model, and the actions list contains " find " . Option B omits the required resource wrapper and incorrectly places db and collection directly in the privilege document. Option C supplies privileges as a single document rather than as the required array. Option D has the correct resource structure but supplies actions as a scalar string instead of an array. The find action grants the ability to perform supported read operations on the specified resource scope, subject to the role ' s other inherited privileges. The shown writeConcern and comment fields are legitimate command options and do not change the structural requirement. Consequently, option A is the only choice that conforms to MongoDB ' s documented privilege document format.

Study Guide reference/topic:Security, Networking, and Encryption - user-defined roles, privilege documents, resources, actions, and grantPrivilegesToRole.

===========

mongosh, the MongoDB Shell, is the interactive command-line environment used to connect to MongoDB deployments and perform administrative and data operations. Through mongosh, a DBA can run CRUD queries, aggregation pipelines, user and role administration, replica-set commands, server diagnostics, index operations, and many other management tasks. mongod, option B, is the MongoDB database server process itself; it stores data and serves requests but is not the interactive administration client. mongostat, option C, is a monitoring utility that reports a concise stream of server activity metrics such as operation rates, memory, connections, and queue information. mongotop, option D, reports time spent reading and writing data by namespace and is likewise a diagnostic utility rather than a general administration shell. DBAs may also use MongoDB Compass, Atlas interfaces, Ops Manager, or automation tooling depending on the deployment, but among these four command-line tools, mongosh is the one intended for broad interactive access and administration. Therefore option A is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - MongoDB Shell, administration tools, server processes, and monitoring utilities.

===========

Replica-set elections determine which eligible member serves as primary. An election can occur after the current primary becomes unavailable, after certain reconfigurations, during replica-set initialization, or when a primary is deliberately stepped down. Eligible voting members exchange election information and, when a candidate obtains the required support, that candidate transitions to primary and begins accepting writes. Option A describes asynchronous replication through the oplog, which is a separate mechanism. Option C is unrelated: index creation is an administrative database operation, not a function of elections. Option D is also incorrect because elections do not add members to the replica-set configuration; adding a secondary requires an explicit membership change such as rs.add() or equivalent configuration management. Elections are the foundation of automatic failover and are one reason MongoDB replica sets can provide high availability without a human manually designating a replacement primary after every failure. During an election there can be a brief period in which writes are unavailable, so applications should use retryable behavior and appropriate driver topology handling. The purpose described in option B is therefore correct.

Study Guide reference/topic:Cluster Reliability and Data Resilience - replica-set elections, primary selection, voting, and automatic failover.

===========

The $in query predicate matches a document when the queried field equals any value listed in the $in array. When the target field is itself an array, MongoDB compares the array elements against the values supplied to $in; one matching element is sufficient. Car 1 qualifies because its features array contains both " Leather Interior " and " 2WD " . Car 3 also qualifies because its array contains " Leather Interior " and " Auto Pilot " . Car 2 contains " Cloth Interior " , " Sun Roof " , and " XM Radio " , none of which are in the predicate array, so it is excluded. A common mistake is to read $in as requiring all values to be present. It does not: the semantics are an OR-style membership test. If the requirement were to ensure that several specified values were all present in an array, a different construct such as $all would be appropriate. Therefore, the result consists of the Toyota Celica and Tesla Model S documents only, making option A correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - querying documents, arrays, and the $in predicate.

===========

MongoDB supports a clean server shutdown through the shutdown administrative command and through the mongosh helper db.shutdownServer(). Option A uses db.adminCommand({ shutdown: 1 }), which executes the shutdown command against the admin database and requests an orderly termination of the server process. Option D explicitly switches to the admin database and calls db.shutdownServer(), the documented shell helper that wraps the same administrative behavior. Option B uses killOp, which terminates a specific database operation identified by an operation ID; port 27017 is not an operation ID and killing an operation is not equivalent to shutting down mongod. Option C uses killAllSessions, which ends logical sessions but leaves the server process running. A controlled shutdown is preferred over abruptly terminating the process because MongoDB can close resources and complete its shutdown procedures cleanly. In replica-set deployments, administrators should also consider whether the member is primary and whether a planned step-down is appropriate before maintenance. Among the commands shown, A and D are the two valid mongosh-based shutdown mechanisms.

Study Guide reference/topic:MongoDB Architecture and Core Operations - clean server shutdown, admin commands, and db.shutdownServer().

===========

MongoDB exposes server parameters that can be configured through the parameter framework. Among the choices, --setParameter is the option specifically designed to set a server parameter on the mongod command line, using syntax such as mongod --setParameter < name > = < value > . A configuration file can also contain a setParameter section, but --config by itself merely tells mongod which configuration file to load; it is not the parameter-setting mechanism identified by the question. Connection-string options control how clients connect and cannot be used to configure arbitrary server runtime parameters. Option D is also incorrect because the server must already be running for mongosh to issue administrative commands. A technical nuance is important: parameters that support modification while the process is already running are changed with the administrative setParameter command, for example db.adminCommand({setParameter:1, ...}). Such runtime changes may not persist across a restart unless the value is also configured for startup. Given the options provided and the exam wording, --setParameter is the intended method, so A is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - server parameters, --setParameter, configuration files, and runtime administration.

===========

Encryption at rest protects persisted database data on storage media, but it is not a complete defense against every form of data exposure or breach. MongoDB ' s encrypted storage capabilities protect files and storage-level data, yet applications and the database server must still process authorized data in usable form. A compromised application account, stolen database credentials, excessive privileges, or a malicious authorized user can therefore expose data even when the underlying storage is encrypted. Network traffic also requires separate transport protection such as TLS; encryption at rest does not secure data as it travels between clients and servers. Option B incorrectly describes transport encryption rather than an at-rest capability. Option A is too subjective and not an inherent limitation, particularly in managed deployments where storage encryption may be enabled automatically. Option D is similarly overstated; encryption adds cryptographic work, but severe performance impact is not an intrinsic defining limitation. The correct security model is defense in depth: combine at-rest encryption with TLS, strong authentication, least-privilege authorization, auditing, and secure key management. Among the choices, C best captures the limitation that at-rest encryption alone cannot prevent all data breaches.

Study Guide reference/topic:Security, Networking, and Encryption - encryption at rest, TLS, authorization, and defense in depth.

===========

Sharding is MongoDB ' s horizontal-scaling mechanism: it partitions a collection ' s data across multiple shards so a deployment can scale storage capacity and distribute query or write workload beyond the limits of one server. That directly supports deployments with very large datasets and high-throughput operations, making C correct. MongoDB also supports zone sharding, which associates ranges of shard-key values with selected shards. Zones can be used to keep particular data near a geographical region, satisfy locality requirements, or map data ranges to hardware tiers, so A is also correct. Option B overstates what sharding itself provides; cross-region consistency behavior depends on replication topology, read/write concerns, latency, and application design rather than simply enabling sharding. Option D describes a deployment that already fits comfortably in memory and meets performance goals, so sharding may add unnecessary operational complexity. Option E primarily describes replication: replica sets maintain redundant copies, provide elections, and improve availability. Production shards are themselves normally replica sets, but redundancy is a replication function rather than the defining purpose of sharding. Therefore the two functions represented here are geographic zone distribution and horizontal scale: A and C.

Study Guide reference/topic:Sharding Strategies and Scalable Deployments - horizontal scaling, large datasets, throughput, shard keys, and zone sharding.

MongoDB ' s flexible document schema is a defining distinction from the conventional fixed-table model associated with relational database systems. Documents in the same MongoDB collection can contain different fields, nested structures, arrays, or representations when the application domain requires that flexibility. MongoDB can still enforce schema rules through validation, so a flexible schema does not mean the absence of governance; it means the physical model is not inherently restricted to one rigid row structure for every record. The other choices are not sufficiently distinguishing. Relational database platforms can provide replication, authentication, and horizontal partitioning or sharding techniques, so those capabilities are not unique architectural differences. MongoDB ' s BSON document model also allows data that is commonly normalized across multiple relational tables to be embedded within one application-oriented document where that design is appropriate. This can reduce joins and map more naturally to object structures used by applications. DBAs must still choose schemas carefully based on access patterns, document growth, duplication, and consistency requirements. Among the choices, Flexible Schema most accurately represents a fundamental MongoDB-versus-RDBMS difference, so option D is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - document databases, BSON data modeling, flexible schemas, and relational-model differences.

===========

replaceOne() replaces the matched document ' s content with the replacement document, except that the immutable _id value is preserved when it is not explicitly changed. Ordinary application fields that are omitted from the replacement disappear. The required final document must retain userid, retain first, and change roles to " SuperUser " . Option B supplies all three fields and therefore produces the requested document structure. Option A omits userid, so that ordinary field would be removed from the replacement. Option C omits both userid and first, leaving only roles in addition to the preserved _id. Option D incorrectly uses the update operator $set inside a replacement document. $set belongs with update operations such as updateOne() or updateMany(); a replaceOne() replacement must be a replacement document rather than an update-operator document. This distinction is important for DBAs and application developers because accidental use of a partial replacement can delete fields that were intended to remain. If the goal is only to change one field, updateOne({userid:1}, {$set:{roles: " SuperUser " }}) would normally be safer. Given the choices, B is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - replaceOne(), full-document replacement, and update-versus-replacement semantics.

===========