Free and Premium MongoDB C100DBA Dumps Questions Answers

The quantity condition is “less than or equal to 1000,” which maps to MongoDB ' s $lte comparison operator. The sales representative condition is “not equal to Anne,” which maps to $ne. When predicates on two different fields appear in the same query document, MongoDB applies an implicit logical AND, so both conditions must be true for a document to match. Option C therefore expresses exactly the requested filter: { quantity: { $lte: 1000 }, salesRep: { $ne: " Anne " } }. Options A and D use $neq, which is not MongoDB ' s inequality operator. Options B and D use $lt, which excludes documents whose quantity is exactly 1000 and therefore fails the “less than or equal” requirement. One nuance of $ne is that it can also match documents where the field is missing, because a missing field is not equal to the specified value. If the application requires salesRep to exist as well, an explicit existence predicate may be appropriate. For the wording shown, however, option C is the correct command.

Study Guide reference/topic:MongoDB Architecture and Core Operations - comparison predicates, $lte, $ne, and implicit AND semantics.

===========

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.

===========

db.collection.getIndexes() is the mongosh method used to return the definitions of all indexes that currently exist on a collection. The result is an array of index specification documents that can show fields such as the index name, key pattern, index version, uniqueness, partial-filter settings, sparse configuration, collation, and whether the index is hidden. This makes the method useful for index audits, troubleshooting, and confirming the physical indexes available to the query planner. Option A is not a documented method for enumerating collection indexes. Option B resembles the $indexStats aggregation stage, which reports usage statistics for indexes, but db.collection.indexStats() is not the method used to list full index definitions. Option C, findIndexes(), is also not the documented mongosh collection helper. Administrators should distinguish between listing index definitions, examining index usage, and inspecting an individual query ' s winning plan: getIndexes() addresses the first requirement, $indexStats addresses usage metrics, and explain() addresses query-planner behavior. Therefore option D is the correct command for listing all indexes on the collection.

Study Guide reference/topic:Indexing and Query Optimization - index administration, index metadata, and db.collection.getIndexes().

===========

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.

===========

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.

===========

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.

===========

Queryable Encryption is designed for client-side protection of sensitive fields while preserving supported query capabilities over encrypted values. With this model, appropriately configured client drivers encrypt selected fields before data is transmitted to the MongoDB server and decrypt authorized results on the client side. That architecture is well suited to highly sensitive PII such as government identification numbers, dates of birth, or regulated demographic information because the database server stores encrypted field values rather than plaintext for those protected fields. The Encrypted Storage Engine, option A, protects database files at rest but the server can still process decrypted data internally. TLS/SSL, option B, protects data while it is moving across the network, not the application field values from the database server itself. Role-Based Access Control, option C, restricts which authenticated principals can perform actions but does not itself cryptographically protect the field contents. Queryable Encryption complements, rather than replaces, TLS, authentication, authorization, auditing, and storage encryption. For the specific requirement of client-side encryption of sensitive application data, option D is the correct MongoDB feature.

Study Guide reference/topic:Security, Networking, and Encryption - Queryable Encryption, client-side encryption, sensitive fields, and key management.

===========

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.

===========

The query contains equality predicates on both city and occupation, so an efficient compound index should contain both fields. Options A and C include only one query predicate plus the unrelated name field, forcing MongoDB to perform additional filtering that the index cannot resolve. Options B and D both contain the complete predicate set. For a query consisting entirely of equality predicates, MongoDB does not require those equality keys to appear in a particular order relative to one another for the query itself; { city: 1, occupation: 1 } and { occupation: 1, city: 1 } can both support the two equality conditions effectively. The original question appears to expect B because it mirrors the field order used in the query, but that distinction is not technically required under MongoDB ' s equality-key guidance. Field order becomes much more significant when the workload also needs a particular index prefix, sort order, range predicate, or when one ordering better supports additional common queries. Accordingly, the technically accurate review result is B and D, with B being the likely intended exam choice.

Study Guide reference/topic:Indexing and Query Optimization - compound indexes, equality predicates, and index key ordering.

===========

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.

===========

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().

===========

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.

===========

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.

===========

When MongoDB ' s winning query plan uses a B-tree index, the plan includes an IXSCAN stage. That stage contains the index-specific information a DBA needs to identify how the query is being serviced, including the key pattern, index name, traversal direction, and index bounds. For example, keyPattern can show a compound definition such as { status: 1, createdAt: -1 }, making it straightforward to confirm which indexed keys participate in the chosen plan. A FETCH stage indicates that MongoDB is retrieving full documents, often after an index has produced candidate record identifiers; the fetch stage itself does not identify the index key. A COLLSCAN stage means MongoDB is scanning the collection and therefore is not using a normal index scan for the predicate. GROUP is unrelated to index selection. Effective DBA query analysis usually involves inspecting both queryPlanner.winningPlan and execution statistics such as totalKeysExamined, totalDocsExamined, and nReturned. But for the narrow question of which stage exposes the index key used by the winning plan, IXSCAN is the correct answer. Therefore option C is correct.

Study Guide reference/topic:Indexing and Query Optimization - explain output, winning plans, IXSCAN, key patterns, and index bounds.

===========

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.

===========

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.

===========

MongoDB can use a compound index to satisfy a multi-field sort when the sort keys appear in the same sequence as the index keys and the requested directions either match the index pattern or are the exact reverse of the entire pattern. The query sorts by { year: 1, rating: -1 }. Option B defines { year: -1, rating: 1 }, which is the complete inverse, so MongoDB can scan that index backward and produce year ascending with rating descending without a blocking in-memory sort. Option A puts title between year and rating; because there is no equality condition fixing title, the index cannot provide a global ordering by { year, rating } across all titles. Options C and D put rating before year, so their primary index ordering does not match the query ' s primary sort key. For multi-field sorts, field sequence is just as important as direction. Therefore B is the strongest index among the presented choices. A forward index { year: 1, rating: -1 } would also be ideal, but it is not offered.

Study Guide reference/topic:Indexing and Query Optimization - compound index sort order, reverse traversal, and index prefixes.

===========

The rnd field should lead the compound index because it is the query ' s equality predicate. MongoDB ' s common compound-index design rule is Equality, Sort, Range (ESR): fields tested for exact equality are typically placed first, followed by fields used for sorting and then range predicates, subject to workload-specific selectivity considerations. Here, rnd: 1234 is an equality condition. _id: { $lte: 1000 } is a range condition, and date: { $gte: ... } is also a range condition while the query additionally sorts on date. Leading with rnd sharply narrows the index region that must be scanned before MongoDB handles the sort/range dimensions. Starting with _id or date would place a range-oriented key ahead of the exact-match predicate and generally reduce the efficiency of index bounds for this query shape. The complete optimal key pattern may depend on whether avoiding the sort or maximizing range selectivity matters most, but the question asks only for the first field. Under ESR guidance, that first field is rnd, so option B is correct.

Study Guide reference/topic:Indexing and Query Optimization - compound indexes, selectivity, and the Equality-Sort-Range guideline.

===========