{"id":23288,"date":"2026-09-28T04:48:04","date_gmt":"2026-09-28T04:48:04","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23288"},"modified":"2026-09-28T04:48:04","modified_gmt":"2026-09-28T04:48:04","slug":"mongodb-c100dba-practice-test-questions-and-exam-dumps-part5-q81-100","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/mongodb-c100dba-practice-test-questions-and-exam-dumps-part5-q81-100\/","title":{"rendered":"MongoDB C100DBA Practice Test Questions and Exam Dumps Part5 Q81-100"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/c100dba-exam-dumps\"><b>MongoDB C100DBA Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 81<\/b><\/h3>\n<p><b>Which command displays information about a MongoDB host system?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.hostInfo()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.systemInfo()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.machineStatus()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.nodeInfo()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.hostInfo() returns information about the operating environment hosting the MongoDB server. The output can include details about the operating system, hardware architecture, system memory, and other host characteristics. DBAs can use this information when investigating resource-related problems or verifying the environment in which MongoDB is running. Host-level information should be considered alongside operating-system monitoring because database commands provide only part of the overall system picture. Understanding CPU architecture, memory availability, and platform details can help administrators evaluate whether the host configuration is appropriate for the database workload.<\/span><\/p>\n<h3><b>Question 82<\/b><\/h3>\n<p><b>Which option determines the default MongoDB network port?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">bindIp<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">port<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">listenPort<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">servicePort<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The port configuration option specifies the TCP port on which the MongoDB server listens for client connections. MongoDB commonly uses port 27017 unless another value is configured. Administrators may change the port for environmental, organizational, or deployment-specific reasons, although changing it should not be considered a substitute for authentication or network security controls. Client connection strings must use the correct port when a non-default value is configured. DBAs should also ensure that firewalls and other network controls permit the selected port only from appropriate sources.<\/span><\/p>\n<h3><b>Question 83<\/b><\/h3>\n<p><b>What does a MongoDB capped collection enforce?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Automatic sharding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fixed collection size<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unique document keys<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Mandatory encryption<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A capped collection has a fixed maximum size and maintains documents according to its configured storage limits. When the collection reaches its capacity, older documents can be automatically overwritten as new documents are added. This behavior makes capped collections useful for certain bounded datasets, such as logs or continuously generated event records where retaining the newest information is more important than preserving unlimited history. Capped collections have behavioral restrictions compared with ordinary collections, so they should be selected only when their insertion and update characteristics match the application&#8217;s requirements.<\/span><\/p>\n<h3><b>Question 84<\/b><\/h3>\n<p><b>Which MongoDB feature automatically expires documents after a specified duration?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TTL index<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unique constraint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partial filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hashed index<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A TTL index allows MongoDB to automatically remove documents after a configured period or at a specified expiration time, depending on the index configuration. TTL indexes are commonly useful for temporary records such as session data, short-lived events, or application logs with defined retention requirements. Expiration is performed by a background process, so deletion does not necessarily occur at the exact instant a document reaches its expiration threshold. DBAs should account for this behavior when defining retention expectations and should ensure that the indexed date field and TTL configuration match the application&#8217;s intended lifecycle.<\/span><\/p>\n<h3><b>Question 85<\/b><\/h3>\n<p><b>Which parameter limits how long a database operation may execute?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">maxTimeMS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">operationLimit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">queryTimeoutMS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">executionWindow<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">maxTimeMS specifies a maximum execution time for supported MongoDB operations. If an operation exceeds the configured limit, MongoDB can terminate it rather than allowing it to continue indefinitely. This can help applications protect themselves from unexpectedly expensive queries or administrative operations. The setting can be applied to individual operations and should be chosen according to workload characteristics. A very aggressive limit may terminate legitimate operations, while an excessively high limit may provide little protection against inefficient workloads. Query analysis should therefore accompany the use of execution-time limits.<\/span><\/p>\n<h3><b>Question 86<\/b><\/h3>\n<p><b>Which command lists the indexes defined on a collection?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.indexCatalog()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.collection.getIndexes()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.showIndexList()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.listIndexesInfo()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.collection.getIndexes() returns information about the indexes defined for a collection. The output includes index keys and relevant properties, allowing administrators to review the current indexing structure. This is useful when troubleshooting query performance, checking whether expected indexes exist, or auditing index configurations before making changes. Reviewing existing indexes can also reveal overlapping or unnecessary definitions that increase storage and write-maintenance costs. DBAs should examine actual workload requirements before removing an index because an index that appears unused during one observation period may support less frequent but important queries.<\/span><\/p>\n<h3><b>Question 87<\/b><\/h3>\n<p><b>Which aggregation stage filters documents according to a condition?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$match<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$collect<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$filterDocs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$whereStage<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The $match stage filters documents according to specified query conditions within an aggregation pipeline. It is commonly placed early in a pipeline so that unnecessary documents are removed before later stages perform more expensive operations. When appropriate indexes can support the filtering predicate, an early $match may also improve overall efficiency. $match uses MongoDB query expressions and can therefore express conditions involving fields, comparisons, logical operators, and other supported predicates. Effective pipeline design often combines selective matching with suitable indexes and careful ordering of subsequent transformation stages.<\/span><\/p>\n<h3><b>Question 88<\/b><\/h3>\n<p><b>Which MongoDB command can return the current database name?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.name()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.databaseName()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.getName()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.currentDatabase()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.getName() returns the name of the database represented by the current database object. This can be useful in scripts, administrative sessions, and diagnostic workflows where code needs to identify the database context dynamically. MongoDB shell commands operate against a selected database, so confirming the current context can help prevent administrative actions from being performed against the wrong database. The method simply identifies the database name; it does not list collections or return database statistics. DBAs should always verify database context before executing commands that modify or remove database objects.<\/span><\/p>\n<h3><b>Question 89<\/b><\/h3>\n<p><b>Which MongoDB option enables detailed audit records for security activity?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Audit logging<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query profiling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Diagnostic capture<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connection tracing<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">MongoDB audit logging records security-related activities so administrators can review actions performed against the database environment. Depending on configuration and deployment capabilities, audit information can help track authentication events, authorization-related activity, administrative operations, and other security-relevant actions. Audit records are valuable for compliance, investigations, and operational accountability. DBAs should define appropriate audit filters to capture useful events without producing unnecessary volumes of data. Audit logs should also be protected from unauthorized modification or deletion because their value depends on maintaining trustworthy records of database activity.<\/span><\/p>\n<h3><b>Question 90<\/b><\/h3>\n<p><b>Which command can display the effective MongoDB configuration file settings?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.configuration()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.serverCmdLineOpts()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.runtimeConfig()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.settings()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.serverCmdLineOpts() reports the command-line options and configuration-file settings used by the running MongoDB server. This is particularly useful when an administrator needs to verify whether a server started with the expected configuration. It can help identify differences between configuration files, startup arguments, and assumptions made during troubleshooting. Reviewing effective configuration is valuable for diagnosing networking, storage, replication, and security issues. Because runtime metrics are provided by different commands, DBAs should use serverCmdLineOpts() specifically when investigating how the server was configured rather than treating it as a performance-monitoring command.<\/span><\/p>\n<h3><b>Question 91<\/b><\/h3>\n<p><b>Which aggregation stage groups documents according to specified expressions?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$combine<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$aggregateBy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">$cluster<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The $group stage combines input documents according to a specified grouping expression and can calculate accumulated values such as totals, averages, minimums, maximums, or counts. It is commonly used for reporting and analytical workloads where individual records need to be summarized into categories. Because grouping can require substantial memory and processing, administrators should consider the number of documents entering the stage and the complexity of accumulator expressions. Filtering unnecessary documents before grouping can reduce work. Appropriate aggregation design is particularly important when analytical pipelines run against large production collections.<\/span><\/p>\n<h3><b>Question 92<\/b><\/h3>\n<p><b>Which security control protects MongoDB traffic while it crosses a network?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage encryption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">TLS<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Collection validation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replica voting<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">TLS protects network communication between MongoDB clients and servers and can also secure communication among MongoDB deployment components when configured appropriately. It helps prevent unauthorized parties from reading or modifying data while it is transmitted across a network. TLS is different from encryption at rest, which protects stored data on disk. Administrators must configure certificates, trusted authorities, and appropriate server and client settings for secure communication. Network encryption should also be combined with authentication, authorization, firewall controls, and proper network segmentation to provide a comprehensive database security architecture.<\/span><\/p>\n<h3><b>Question 93<\/b><\/h3>\n<p><b>Which command can remove a specific database from MongoDB?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.removeDatabase()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.dropDatabase()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.deleteDatabase()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.eraseDatabase()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.dropDatabase() removes the current database and its collections. Because this operation is destructive, administrators should verify the active database context before executing it. In production environments, appropriate authorization and operational procedures should be followed, and backups should be considered before irreversible data removal. Dropping a database is different from dropping a collection because the database-level operation affects all collections belonging to that database. DBAs should also consider application dependencies, replication behavior, and recovery requirements before performing such an operation.<\/span><\/p>\n<h3><b>Question 94<\/b><\/h3>\n<p><b>Which replica set member property controls whether indexes are built on a secondary?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">buildIndexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">indexReplica<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">secondaryIndexes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">replicaIndexMode<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The buildIndexes replica set member setting determines whether a member builds indexes. A member configured with buildIndexes: false can be useful in specialized deployment scenarios, although it has important limitations and should not be treated as a general performance optimization. Such a member may not be suitable for normal application reads that depend on indexes. Administrators must understand the consequences for query performance, replication behavior, and member eligibility before using this configuration. In most standard replica set deployments, data-bearing members maintain indexes normally.<\/span><\/p>\n<h3><b>Question 95<\/b><\/h3>\n<p><b>Which MongoDB feature can automatically retry certain supported write operations after transient failures?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Retryable writes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Persistent writes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deferred writes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Duplicate writes<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Retryable writes allow supported write operations to be retried by MongoDB drivers when certain transient errors occur. The feature is designed to improve application reliability during temporary network interruptions, primary changes, or other supported failure conditions. Drivers use session and operation identifiers to help ensure that a retry does not unintentionally apply the same logical operation more than once. Not every write pattern or deployment configuration is eligible for retryable-write behavior, so applications should use compatible drivers and understand the supported operation types. Retryable writes complement, rather than replace, appropriate error handling.<\/span><\/p>\n<h3><b>Question 96<\/b><\/h3>\n<p><b>Which MongoDB component maintains metadata about a sharded cluster?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">mongos<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Config server replica set<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application server<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage engine<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The config server replica set stores metadata required to operate a sharded MongoDB cluster. This includes information about databases, collections, chunks, shard placement, and cluster configuration. mongos processes client requests and uses cluster metadata to route operations appropriately, but it does not serve as the authoritative persistent store for that metadata. Because config servers are critical to cluster operation, they should be deployed with appropriate redundancy and monitoring. Administrators should also ensure that configuration-server members have reliable connectivity and sufficient resources for the management workload generated by the sharded environment.<\/span><\/p>\n<h3><b>Question 97<\/b><\/h3>\n<p><b>Which command gracefully stops a MongoDB server process?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.shutdownServer()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.stopMongo()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.terminateServer()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.exitDatabase()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.shutdownServer() requests a controlled shutdown of the MongoDB server process. A graceful shutdown allows MongoDB to complete appropriate shutdown procedures rather than abruptly terminating the process. In a replica set, administrators should consider the member&#8217;s role before stopping it, especially when the target is the primary. Controlled maintenance procedures can reduce disruption and allow applications and replica set members to respond appropriately. Operating-system-level process termination should generally not be the first choice for routine maintenance because abrupt termination can create unnecessary recovery work and complicate operational troubleshooting.<\/span><\/p>\n<h3><b>Question 98<\/b><\/h3>\n<p><b>Which MongoDB command provides index usage statistics for a collection?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.collection.getIndexes()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.collection.indexStats()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.collection.indexUsage()<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">db.collection.indexReport()<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">db.collection.aggregate([{ $indexStats: {} }]) provides statistics describing index usage for the collection. These statistics can help DBAs identify indexes that are being accessed and evaluate whether existing indexes correspond to actual workload patterns. Index usage information should be interpreted over a meaningful observation period because counters may not represent infrequent workloads immediately. An index that receives little activity can still be valuable for occasional critical queries. Administrators should therefore combine index statistics with query analysis, application requirements, and maintenance costs before deciding whether an index should be retained or removed.<\/span><\/p>\n<h3><b>Question 99<\/b><\/h3>\n<p><b>Which MongoDB concept identifies a logical grouping of collections?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Namespace<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Database<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replica set<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Shard zone<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A MongoDB database provides a logical grouping for collections and related database objects. Collections belong to a database, and MongoDB uses the database name as part of the namespace associated with stored objects. Separating application data into appropriate databases can support organizational and administrative requirements, although database boundaries do not automatically provide complete workload or security isolation. Replica sets represent deployment topology, while shard zones describe placement policies in sharded environments. Understanding MongoDB&#8217;s database and collection hierarchy helps administrators correctly manage permissions, backups, naming, and operational procedures.<\/span><\/p>\n<h3><b>Question 100<\/b><\/h3>\n<p><b>Which feature allows a transaction to span multiple MongoDB documents?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Single-document atomicity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Multi-document transactions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Collection validation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index synchronization<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Multi-document transactions allow a group of supported database operations to execute with transactional guarantees across multiple documents. They are useful when an application needs several related changes to succeed or fail as a logical unit. Transactions can span multiple collections and, in supported deployments, multiple shards. They introduce additional coordination and resource overhead, so they should be used when atomic multi-document behavior is actually required rather than as a default replacement for good schema design. DBAs should monitor transaction duration, resource consumption, locking behavior, and application retry handling when supporting transactional workloads.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full MongoDB C100DBA Exam Dumps and Practice Test Dumps &nbsp; Question 81 Which command displays information about a MongoDB host system? db.hostInfo() db.systemInfo() db.machineStatus() db.nodeInfo() Correct Answer: 1 Explanation: db.hostInfo() returns information about the operating environment hosting the MongoDB server. The output can include details about the operating system, hardware architecture, system memory, and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23288"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=23288"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23288\/revisions"}],"predecessor-version":[{"id":23289,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23288\/revisions\/23289"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23288"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23288"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}