Practice Free C100DBA MongoDB Associate Database Administrator(Based on MongoDB 6.0 and 7.0+) Exam Questions Answers With Explanation

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.

===========

updateMany() distinguishes between documents that match the filter and documents whose stored data actually changes. The filter { diagnosis: " Hypertension " } matches Carlos Martinez and Maria Lopez, so matchedCount is 2. Carlos currently has room: 203, and $set: { room: 207 } changes his document, contributing one to modifiedCount. Maria already has room: 207. She still satisfies the filter and therefore counts as a match, but setting a field to the value it already contains does not produce a material modification, so she does not increment modifiedCount. Juan Perez has diagnosis Arrhythmia, so he is neither matched nor modified. The resulting acknowledged operation therefore reports matchedCount: 2 and modifiedCount: 1, corresponding to option D. This distinction is essential when validating whether an update actually changed stored values rather than merely identifying matching records. This distinction is operationally important: a large difference between matched and modified counts can indicate that many matching documents already contained the requested state, not that the update failed. DBAs should use both counters when validating bulk-update behavior.

Study Guide reference/topic:MongoDB Architecture and Core Operations - updateMany(), $set, matchedCount, and modifiedCount.

===========

MongoDB provides db.grantRolesToUser() specifically for assigning one or more additional roles to an existing user. The method takes the username as its first argument and an array of roles as its second argument, so db.grantRolesToUser( " user1 " , [ " customRole1 " ]) is the correct choice. A role can be supplied as a simple string when it belongs to the current database or as an explicit document such as { role: " customRole1 " , db: " admin " } when the database context must be specified. Option B uses db.createUser(), which is used to create a new user rather than modify the role membership of an account that already exists. Options A and C use method names that are not the documented mongosh interfaces for this operation. Administrators should also distinguish grantRolesToUser() from grantRolesToRole(): the latter makes a user-defined role inherit other roles, whereas the former directly changes a user ' s assigned roles. Least-privilege practice requires granting only roles necessary for the user ' s responsibilities. For the requested update to the existing user, option D is correct.

Study Guide reference/topic:Security, Networking, and Encryption - user administration, role assignment, RBAC, and grantRolesToUser().

===========

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.

===========

An upsert combines update behavior with conditional insertion. updateOne() first searches for a document matching { product: " laptop " }. If one exists, $set changes unitsInStock to 25. If none exists and the options document contains { upsert: true }, MongoDB inserts a new document based on the equality portions of the filter together with the update result. Option A uses exactly this pattern. Options B and C incorrectly use insertOne(), which inserts a supplied document and does not accept an update-operator document plus upsert semantics in this form. Option D uses the correct method and update structure but specifies True with a capital T. Mongosh uses JavaScript Boolean syntax, so the literal must be lowercase true. Upserts are useful when an application needs to ensure that a logical entity exists after an operation, but DBAs should consider a unique index on the identifying field when duplicate creation by concurrent requests must be prevented. Given the choices, updateOne(..., {$set:...}, {upsert:true}) is the valid operation, so A is correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - updateOne(), $set, upserts, and Boolean syntax.

===========

mongosh accepts a MongoDB host address in hostname:port form, so mongosh " node-1.cluster1.mycompany.local:27017 " is the valid choice among the commands shown. A canonical URI form such as mongosh " mongodb://node-1.cluster1.mycompany.local:27017 " is also valid, and the connection can alternatively be expressed using --host together with --port. Option A uses an unsupported --hostname switch rather than the documented --host option. Option B invents a --connect flag that is not the standard mongosh interface. Option C constructs an invalid string using an ampersand-style parameter rather than a MongoDB URI or a normal host:port target. Port 27017 is MongoDB ' s default server port, so it could often be omitted if the deployment uses the default, but explicitly including it is valid and removes ambiguity. In authenticated or TLS-enabled environments, the DBA would also supply credentials, authentication database, certificate settings, or a connection string carrying those parameters. For the simple host-and-port requirement in the question, option D is correct.

Study Guide reference/topic:Security, Networking, and Encryption - mongosh connectivity, host/port addressing, and connection options.

===========

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.

===========

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.

===========

The proposed index is a compound index across home_score and away_score. MongoDB supports compound multikey indexes, but it imposes an important restriction: for any one indexed document, no more than one field covered by the compound index may contain an array. Document 1 is valid because only away_score is an array. Document 2 is also valid because only home_score is an array. Document 4 contains scalar values for both fields. Document 3 contains arrays in both indexed fields: home_score: [5,8] and away_score: [9,6] . Indexing that document would require a compound multikey index to expand two independent array dimensions, which MongoDB prohibits. Therefore document 3 prevents the compound index from being valid. The restriction is important because a single multikey field already creates multiple index keys per document; allowing multiple independently array-valued keys in the same compound index would create ambiguous and potentially combinatorial key combinations. DBAs designing indexes over document schemas with arrays must understand these multikey constraints before building compound indexes. The failing document is _id:3, making option D correct.

Study Guide reference/topic:Indexing and Query Optimization - multikey indexes, compound multikey restrictions, and array-valued fields.

===========

The operation must update every matching document and use the $inc update operator with correct syntax. updateMany() applies the update to all documents matching { color: " green " }. The $inc operator must be the top-level update operator and receive a field-to-amount mapping, so the valid update document is { $inc: { price: 5 } }. Option C satisfies both requirements. The sweater price increases from 20 to 25, and the hat price increases from 12 to 17. Option B uses a syntactically correct $inc expression, but the legacy update() call shown does not explicitly request a multi-document update, so it does not meet the stated requirement to modify all green products. Options A and D place $inc beneath the price field instead of placing $inc at the update-operator level, which is not valid update syntax. $inc operates atomically on each affected document and can be used with positive or negative numeric increments. Therefore, the correct multi-document update is db.products.updateMany({color: " green " }, {$inc:{price:5}}), making C correct.

Study Guide reference/topic:MongoDB Architecture and Core Operations - updateMany(), update operators, filters, and $inc.

===========

For a compound index to satisfy a multi-field sort, the indexed fields must occur in the same sequence as the sort specification, and their directions must either match the requested pattern or be the complete reverse of it. The query sorts by { department: 1, salary: -1 }, so option B exactly matches both the key order and the requested directions. MongoDB can scan that index and return the results already ordered, avoiding a blocking in-memory sort. Option A uses { department: 1, salary: 1 }, which does not match the mixed-direction sort and is not its full inverse. Option D puts name before the two sort keys. Because the query has no equality predicate on name, that leading key prevents the later fields from directly providing the requested global sort. Option C is not a sensible index definition for this workload. Separately, the displayed projection mixes inclusion and exclusion (name:1, salary:1, department:0), which MongoDB normally disallows except for _id; that syntax issue should be corrected independently. It does not change the intended index answer for the sort, which is B.

Study Guide reference/topic:Indexing and Query Optimization - compound indexes, sort support, index prefixes, and key direction.

===========

The query filters only on the sizes field, so the most direct supporting index is a single-field index on sizes. Because sizes contains arrays, MongoDB automatically treats the resulting index as a multikey index and creates index entries derived from the array elements. That allows the query { sizes: " M " } to locate matching documents through the index rather than scanning every document in the collection. Option B indexes item, which is not part of the predicate and therefore does not help this query. Option C contains sizes, but _id is the leading key and the query provides no equality restriction on _id; this prevents efficient use of the later key as a standalone prefix for the query. Option D has the same structural problem because item precedes sizes and is not constrained. MongoDB ' s index-prefix rules make a targeted { sizes: 1 } index the strongest choice here. In a real workload, DBAs should also consider write overhead and whether additional queries can share a compound index before creating redundant indexes. For this single query pattern, option A is optimal.

Study Guide reference/topic:Indexing and Query Optimization - multikey indexes, array fields, index prefixes, and query support.

===========

db.collection.deleteOne() deletes a single document that matches the supplied filter, so the direct operation is db.scientificPapers.deleteOne({ doi: " 10.1000/xyz123 " }). The DOI is the identifying criterion, and no additional filter is required. Option A is dangerous and incorrect: drop() removes the entire collection and its indexes rather than deleting a filtered document. Option B uses findOneAndDelete(), which can delete a single matching document, but the displayed filter also requires a nonexistent or inappropriate field/value pair, scientificPapers: " orders " , so the target document would not match. Option D misunderstands the method signature. The second argument to deleteOne() is an options document for settings such as write concern, collation, or hint; it is not a second query predicate. In production, a unique index on DOI could also ensure that the business identifier is unique and make the deletion highly selective. Among the presented commands, only option C cleanly and correctly deletes the one scientific-paper document identified by the specified DOI.

Study Guide reference/topic:MongoDB Architecture and Core Operations - delete operations, deleteOne(), filters, and collection management.

===========

In MongoDB explain output, a COLLSCAN stage means the winning plan is scanning documents in the collection rather than traversing a suitable index. This is the clearest indicator that the query is not being serviced by a normal index scan for the relevant predicate. By contrast, IXSCAN explicitly indicates an index scan and typically includes details such as the index key pattern, direction, and bounds. A FETCH stage represents retrieval of full documents, often after an index has already identified candidate record locations; its presence does not imply that no index was used. GROUP relates to grouping behavior and is not the stage used to identify missing index support. A collection scan is not automatically wrong: for tiny collections or queries that return most documents, it can be efficient. However, on large collections with selective predicates, repeated COLLSCAN plans are a strong signal that the DBA should evaluate indexing. Administrators should compare totalDocsExamined, totalKeysExamined, execution time, and the winning/rejected plans before deciding to add an index. For the terminology tested by the question, COLLSCAN is the correct stage, so C is correct.

Study Guide reference/topic:Indexing and Query Optimization - explain plans, COLLSCAN, IXSCAN, and missing index diagnostics.

===========