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

The query first applies .sort({ price: -1 }). In MongoDB, -1 specifies descending order, so the result stream is ordered from the highest price to the lowest: Laptop at 1500, Smartphone at 800, Tablet at 600, Monitor at 300, and Headphones at 200. The subsequent .limit(2) restricts the cursor to the first two documents in that sorted sequence. Therefore, only Laptop and Smartphone are returned. Option B identifies the two lowest-priced products rather than the highest. Option C reflects the sort but ignores the limit(2) stage. Option D shows the two lowest products in ascending order and therefore contradicts both the requested sort direction and the limit semantics. For a large collection, a single-field index on price could support this sort efficiently because MongoDB can traverse an index in either direction; an ascending index can be scanned backward to satisfy a descending sort and vice versa. The logical query result, however, is independent of whether such an index exists. Option A is the correct output.

Study Guide reference/topic:MongoDB Architecture and Core Operations - cursor sorting, limiting result sets, and query result ordering.

===========

The most direct evidence that storage capacity is approaching exhaustion is high filesystem utilization and explicit operating-system errors showing that no space remains. Sustained disk utilization above 90% is a practical warning threshold because the deployment has little headroom for database growth, index builds, temporary files, journal activity, or operational spikes. The errno:28 No space left on device message is even stronger evidence: the operating system rejected a write because the relevant filesystem could not allocate additional space. The other choices can correlate with workload growth but do not specifically prove a capacity problem. Query execution time can increase because of poor indexes, cache misses, lock or ticket contention, or CPU pressure. A rising document count says nothing about remaining free space without knowing document size, index size, and volume capacity. Low read/write ticket availability reflects storage-engine concurrency pressure rather than filesystem capacity. Administrators should therefore monitor disk-used and disk-free metrics, alert well before full utilization, and investigate any ENOSPC-style log events immediately. B and D are the two storage-capacity indicators.

Study Guide reference/topic:Performance Monitoring and Tuning - disk capacity, storage metrics, alerts, and diagnostic logs.

===========

db.currentOp() is the mongosh helper used to inspect operations currently executing on a MongoDB server. Passing true requests a broad view that includes all in-progress operations as well as additional idle/system entries, so it can be used when the administrator wants to see the complete current-operation picture. The database-command form, db.adminCommand({ currentOp: true }), invokes the corresponding administrative command and is also valid for obtaining in-progress operation information. Option A adds a filter restricting the result to operations whose op field is " command " ; it therefore does not represent all operation types. Option B is not valid currentOp command syntax, and option E uses an all field that is not the documented special form for this helper. In modern MongoDB administration, the $currentOp aggregation stage is generally preferred for richer filtering and aggregation, but the question is testing the traditional helper and command interfaces. Therefore, C and D are the two valid choices among those presented.

Study Guide reference/topic:Performance Monitoring and Tuning - current operations, currentOp, and administrative diagnostics.

===========

db.currentOp() reports information about operations that are currently in progress and accepts a filter document to restrict the output. The ns field in current-operation information identifies the namespace, typically in database.collection form. The regular expression /^qa\./ therefore matches namespaces beginning with qa., which isolates operations targeting collections in the qa database. Option C correctly supplies that namespace expression as a filter argument to db.currentOp(). Options A and B use a nonexistent db.listOps interface. Option D incorrectly treats ns as though it were a property or method chained from db.currentOp; filtering belongs inside the argument document. On current MongoDB versions, administrators are encouraged to use the $currentOp aggregation stage for more powerful filtering and composition, but the legacy helper remains the interface being tested here. Once the problematic operation is identified, the DBA can inspect details such as operation type, namespace, duration, waiting state, and client information before deciding whether additional action such as optimization or termination is justified. Thus C is the correct command.

Study Guide reference/topic:Performance Monitoring and Tuning - active operations, namespaces, long-running operation diagnostics, and currentOp.

===========

MongoDB stores records as BSON documents. BSON, short for Binary JSON, is a binary serialization format that preserves the JSON-like document model while supporting a richer set of data types required by database applications. Mongosh commonly displays documents using JavaScript or Extended JSON-like notation, which is why JSON is a tempting distractor, but the native stored representation is BSON. BSON supports types such as ObjectId, dates, binary data, timestamps, Decimal128, 32-bit and 64-bit integers, arrays, embedded documents, and other values that standard JSON does not represent natively. Base64 is an encoding technique often used to render binary data as text and is not MongoDB ' s document storage format. XML is also unrelated to MongoDB ' s native representation. Understanding BSON is fundamental for database administrators because document-size limits, type comparisons, index keys, serialization behavior, and driver interoperability all depend on BSON semantics. The flexible document model allows fields to contain scalar values, nested documents, and arrays within the same record structure. Therefore the encoded format used by MongoDB to store documents is BSON, making option C correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - BSON, document structure, data types, and JSON/BSON distinctions.

===========

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.

===========

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 describes oplog operations as idempotent. An idempotent operation can be reapplied without causing an unintended cumulative change beyond the intended final state. This property is important for replication and recovery because secondary members copy and apply oplog entries, and operational processes may need to reason safely about replay. MongoDB can represent client write activity in oplog-friendly forms specifically to preserve appropriate replication semantics. Natural ordering is relevant to the capped collection structure of the oplog, but it is not the attribute identified by the question as providing safe repeatable application behavior. Concurrency control governs simultaneous operations and storage-engine coordination rather than the defining form of oplog entries. Flow control is a replica-set mechanism that can regulate the primary ' s write throughput when replication lag threatens majority-commit behavior; it does not make individual oplog entries safe to replay. The idempotent nature of oplog operations supports deterministic replication and contributes to consistent secondary state as operations are applied in sequence. Therefore the correct attribute among the options is Idempotent, making D correct.

Study Guide reference/topic:Cluster Reliability and Data Resilience - the oplog, idempotent replication operations, replay, and consistency.

===========

MongoDB Enterprise auditing supports three standard destination values for audit events: syslog, file, and console. With the syslog destination, audit records are sent to the operating system ' s syslog facility where supported. With the file destination, events are written to a configured audit log path, and administrators can control the output format according to the supported audit configuration. With the console destination, audit events are emitted to standard output, which can be useful in containerized or centrally collected logging environments. A raw TCP/IP port is not itself an auditLog.destination value. Organizations can certainly forward logs over the network using operating-system or observability tooling, but that transport is external to MongoDB ' s destination setting. A MongoDB database is likewise not one of the supported audit destinations; keeping audit evidence independent from the system being audited is also preferable for integrity and compliance. Auditing records security-relevant actions and can be filtered to meet regulatory or operational requirements. Therefore the three valid destinations among the choices are syslog, file, and console: A, B, and E.

Study Guide reference/topic:Security, Networking, and Encryption - auditing, auditLog.destination, compliance logging, and audit configuration.

===========

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.

===========

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.

===========

MongoDB custom roles are defined in terms of privileges, and each privilege specifies a resource plus one or more allowed actions. For read/query access, find is a valid privilege action. To represent all normal collections in a specified database, MongoDB uses a resource document with the target database and an empty collection name, for example { db: " products " , collection: " " }. Option B therefore combines the correct resource scope with the find action and does not grant write capability. The distractors confuse built-in role names with privilege actions. read, readWrite, and readAnyDatabase are built-in roles or role concepts, not the appropriate action values for the privileges[].actions list shown here. Likewise, a literal " * " collection value is not the documented database-wide resource form for this custom privilege. In practice, an administrator could also assign MongoDB ' s built-in read role rather than creating a custom role if its permissions exactly match the requirement. Given the specific createRole() choices, however, option B is the technically correct construction.

Study Guide reference/topic:Security, Networking, and Encryption - RBAC, custom roles, resources, and privilege actions.

===========

The supported mongosh helpers for replica-set membership changes are rs.remove() and rs.add(). rs.remove(hostname) removes the member whose host string matches the supplied host:port, while rs.add() adds a new member using either a host string or a member configuration document that includes a host field. Option C uses those documented methods in the required sequence: remove node 1, remove node 2, then add node 1 back. The names rs.removeNode() and rs.addNode() shown in the other options are not standard MongoDB replica-set helper methods. Membership changes must be performed carefully because modifying voting or data-bearing membership can affect majority calculations, elections, and availability. Administrators normally execute membership changes while connected to the current primary, allow configuration propagation, and verify replica-set health afterward with rs.status() or related diagnostics. If a removed data-bearing node is later re-added, it may need to synchronize depending on how far its data has diverged from the current replica-set history. Among the choices, option C is the only valid command sequence.

Study Guide reference/topic:Cluster Reliability and Data Resilience - replica-set membership, rs.remove(), rs.add(), and topology changes.

===========

The --fork option starts mongod in daemon mode so the server process continues in the background. When --fork is used, MongoDB requires diagnostic output to be redirected through a logging destination such as --logpath or --syslog; the process cannot simply detach while continuing to use the normal foreground output stream. Option C supplies both --fork and a valid log path, while leaving the other server settings at their normal defaults unless they are configured elsewhere. Option A explicitly sets the default port but does not satisfy the logging requirement associated with --fork. Option B treats the literal word default as a filesystem path and does not provide the required log destination. Option D uses an unsupported --default switch. In production, MongoDB packages commonly use service managers such as systemd, and a configuration file is usually preferred over manually launching mongod with a long list of command-line options. Nevertheless, among the commands shown, C is the one that correctly daemonizes the server process and provides the logging configuration required for a successful fork.

Study Guide reference/topic:MongoDB Architecture and Core Operations - mongod startup, background execution, logging, and server configuration.

===========