{"id":23284,"date":"2026-09-28T04:47:17","date_gmt":"2026-09-28T04:47:17","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23284"},"modified":"2026-09-28T04:47:17","modified_gmt":"2026-09-28T04:47:17","slug":"mongodb-c100dba-practice-test-questions-and-exam-dumps-part3-q41-60","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/mongodb-c100dba-practice-test-questions-and-exam-dumps-part3-q41-60\/","title":{"rendered":"MongoDB C100DBA Practice Test Questions and Exam Dumps Part3 Q41-60"},"content":{"rendered":"

View Full <\/b>MongoDB C100DBA Exam Dumps<\/b><\/a> and Practice Test Dumps<\/b><\/h2>\n

 <\/p>\n

Question 41<\/b><\/h3>\n

Which WiredTiger feature periodically persists dirty data to disk?<\/b><\/p>\n

    \n
  1. Oplog rotation<\/span><\/li>\n
  2. Query planning<\/span><\/li>\n
  3. Journal replay<\/span><\/li>\n
  4. Checkpoint processing<\/span><\/li>\n<\/ol>\n

    Correct Answer: 4<\/b><\/p>\n

    Explanation:<\/b><\/p>\n

    WiredTiger uses checkpoints to create consistent on-disk snapshots of data files. During checkpoint processing, modified or dirty pages are written to disk, allowing MongoDB to maintain a recoverable storage state. Checkpoints work together with journaling rather than replacing it. Journaling records operations so recent changes can be recovered if a failure occurs before the next checkpoint completes. Understanding this distinction is important for DBA troubleshooting because checkpoints influence disk I\/O patterns and recovery behavior. Monitoring checkpoint activity can also help identify storage performance issues when workloads generate substantial amounts of modified data.<\/span><\/p>\n

    Question 42<\/b><\/h3>\n

    Which command displays the currently configured server startup options?<\/b><\/p>\n

      \n
    1. db.serverCmdLineOpts()<\/span><\/li>\n
    2. db.serverStatus()<\/span><\/li>\n
    3. db.currentOp()<\/span><\/li>\n
    4. db.hostInfo()<\/span><\/li>\n<\/ol>\n

      Correct Answer: 1<\/b><\/p>\n

      Explanation:<\/b><\/p>\n

      db.serverCmdLineOpts() reports the command-line options and configuration-file settings used by the running MongoDB server. This is useful when administrators need to verify operational configuration without inspecting the original startup environment directly. It can help confirm settings related to networking, storage, replication, security, and other server behavior. serverStatus() instead provides runtime metrics, while currentOp() focuses on active operations. hostInfo() provides host-level information. For troubleshooting configuration discrepancies between expected and actual server behavior, examining the effective startup options is an important diagnostic step.<\/span><\/p>\n

      Question 43<\/b><\/h3>\n

      What is the primary purpose of a hidden replica set member?<\/b><\/p>\n

        \n
      1. Accepting normal client reads<\/span><\/li>\n
      2. Providing an isolated replica<\/span><\/li>\n
      3. Becoming the preferred primary<\/span><\/li>\n
      4. Handling shard metadata<\/span><\/li>\n<\/ol>\n

        Correct Answer: 3<\/b><\/p>\n

        Explanation:<\/b><\/p>\n

        A hidden replica set member is configured so that applications do not normally discover it for client operations. It can still maintain a copy of the dataset and participate in replication, making it useful for specialized workloads such as dedicated backups, reporting, or analytics. Hidden members are commonly assigned priorities that prevent them from becoming primary. They continue receiving replicated operations from the set while remaining unavailable for ordinary application routing. This separation allows administrators to use the member for maintenance or secondary workloads without exposing those activities to normal client traffic.<\/span><\/p>\n

        Question 44<\/b><\/h3>\n

        Which read concern requests data acknowledged by a majority of replica set voting members?<\/b><\/p>\n

          \n
        1. local<\/span><\/li>\n
        2. majority<\/span><\/li>\n
        3. available<\/span><\/li>\n
        4. snapshot<\/span><\/li>\n<\/ol>\n

          Correct Answer: 2<\/b><\/p>\n

          Explanation:<\/b><\/p>\n

          The majority read concern allows reads to return data that has been acknowledged by a majority of voting members, providing stronger consistency guarantees than a simple local read. This is especially useful when applications need protection against reading data that could be rolled back after a primary failure. The exact behavior depends on the deployment and transaction context, but the central concept is that majority acknowledgment provides a stronger durability and consistency boundary. Read concern is distinct from write concern: write concern controls how writes are acknowledged, while read concern determines the consistency characteristics of returned data.<\/span><\/p>\n

          Question 45<\/b><\/h3>\n

          Which replica set member can intentionally lag behind other members?<\/b><\/p>\n

            \n
          1. Delayed member<\/span><\/li>\n
          2. Hidden router<\/span><\/li>\n
          3. Arbiter node<\/span><\/li>\n
          4. Config server<\/span><\/li>\n<\/ol>\n

            Correct Answer: 1<\/b><\/p>\n

            Explanation:<\/b><\/p>\n

            A delayed replica set member intentionally maintains a replication delay behind the primary. Administrators can configure the delay so that the member preserves an older version of the dataset for a defined period. This can provide a recovery option when unwanted changes, such as accidental deletions, are detected after they occur. A delayed member should generally be hidden and prevented from becoming primary because its data is intentionally stale. It also requires sufficient storage and monitoring because the member must retain and apply operations according to the configured delay.<\/span><\/p>\n

            Question 46<\/b><\/h3>\n

            Which authentication mechanism uses X.509 certificates?<\/b><\/p>\n

              \n
            1. SCRAM-SHA-256<\/span><\/li>\n
            2. LDAP binding<\/span><\/li>\n
            3. MONGODB-X509<\/span><\/li>\n
            4. Kerberos tickets<\/span><\/li>\n<\/ol>\n

              Correct Answer: 3<\/b><\/p>\n

              Explanation:<\/b><\/p>\n

              MONGODB-X509 is MongoDB’s authentication mechanism for clients and servers using X.509 certificates. It relies on TLS and certificate-based identity rather than a username and password exchange through SCRAM. The server must be configured appropriately for certificate authentication, including trusted certificate authorities and suitable certificate subject information. X.509 authentication is particularly useful in environments that already use a public-key infrastructure for identity management. Administrators should ensure certificates are properly issued, trusted, and renewed because expired or incorrectly configured certificates can prevent clients from establishing authenticated connections.<\/span><\/p>\n

              Question 47<\/b><\/h3>\n

              Which index type can restrict indexed documents using a filter expression?<\/b><\/p>\n

                \n
              1. Partial index<\/span><\/li>\n
              2. Sparse index<\/span><\/li>\n
              3. Text index<\/span><\/li>\n
              4. Hashed index<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1<\/b><\/p>\n

                Explanation:<\/b><\/p>\n

                A partial index indexes only documents that satisfy a specified partialFilterExpression. This can reduce index size and maintenance overhead when queries primarily target a subset of documents. For example, an application might index only active records rather than every document in a collection. Partial indexes are more flexible than sparse indexes because the administrator can define conditions beyond simple field existence. Queries must still satisfy the relevant indexing conditions for the index to provide useful query support. Choosing an appropriate partial filter can improve storage efficiency while preserving performance for targeted workloads.<\/span><\/p>\n

                Question 48<\/b><\/h3>\n

                Which command terminates a running MongoDB operation by its operation identifier?<\/b><\/p>\n

                  \n
                1. db.stopOperation()<\/span><\/li>\n
                2. db.killOp()<\/span><\/li>\n
                3. db.abortOp()<\/span><\/li>\n
                4. db.cancelQuery()<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 2<\/b><\/p>\n

                  Explanation:<\/b><\/p>\n

                  db.killOp() is used by administrators to terminate an active database operation identified by its operation ID. Administrators typically identify the operation through current-operation information before deciding whether intervention is necessary. This can be useful when a query, administrative task, or other operation is consuming excessive resources or is no longer needed. Killing an operation should be performed carefully because terminating database activity can affect application behavior or leave expected work incomplete. Appropriate privileges are also required. In production systems, investigating the reason for the problematic operation is preferable to repeatedly terminating similar operations.<\/span><\/p>\n

                  Question 49<\/b><\/h3>\n

                  What does the collStats command primarily provide?<\/b><\/p>\n

                    \n
                  1. Authentication policies<\/span><\/li>\n
                  2. Replica elections<\/span><\/li>\n
                  3. Collection statistics<\/span><\/li>\n
                  4. Shard credentials<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 3<\/b><\/p>\n

                    Explanation:<\/b><\/p>\n

                    The collStats command provides statistics about a specific collection. Depending on the storage engine and MongoDB version, the information can include document counts, storage sizes, index statistics, and other collection-level measurements. DBAs can use these metrics to investigate storage consumption, collection growth, and indexing characteristics. collStats is different from broader server-level monitoring commands because its focus is a particular collection. Examining collection statistics can help identify unusually large collections, excessive index overhead, or unexpected data growth that may require capacity planning or schema and indexing review.<\/span><\/p>\n

                    Question 50<\/b><\/h3>\n

                    Which MongoDB aggregation stage combines documents from another collection?<\/b><\/p>\n

                      \n
                    1. $merge<\/span><\/li>\n
                    2. $group<\/span><\/li>\n
                    3. $unwind<\/span><\/li>\n
                    4. $lookup<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 4<\/b><\/p>\n

                      Explanation:<\/b><\/p>\n

                      The $lookup aggregation stage performs a left outer join-like operation between documents in the current pipeline and documents from another collection. It can match fields between the two collections and add related documents to the pipeline output. $lookup is useful for workloads where related information is stored separately, although excessive use can create significant memory and processing requirements. Effective indexes on the fields involved in the matching operation can improve performance. DBAs should evaluate the data model and workload before relying heavily on cross-collection joins, particularly for high-volume production workloads.<\/span><\/p>\n

                      Question 51<\/b><\/h3>\n

                      Which replica set setting determines whether a member can become primary?<\/b><\/p>\n

                        \n
                      1. votes<\/span><\/li>\n
                      2. priority<\/span><\/li>\n
                      3. hidden<\/span><\/li>\n
                      4. tags<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 2<\/b><\/p>\n

                        Explanation:<\/b><\/p>\n

                        The priority setting influences a replica set member’s eligibility and preference for becoming primary during elections. Members with higher priority are generally preferred over members with lower priority when the election process selects a new primary. A priority of zero prevents a member from becoming primary. Administrators can therefore use priority values to control which members should normally serve as primary while considering factors such as hardware capacity, geographic placement, and network characteristics. Changing replica configuration requires careful planning because elections and configuration changes can temporarily affect application connectivity.<\/span><\/p>\n

                        Question 52<\/b><\/h3>\n

                        Which command reports active operations on a MongoDB server?<\/b><\/p>\n

                          \n
                        1. db.currentOp()<\/span><\/li>\n
                        2. db.indexStats()<\/span><\/li>\n
                        3. db.hostInfo()<\/span><\/li>\n
                        4. db.stats()<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1<\/b><\/p>\n

                          Explanation:<\/b><\/p>\n

                          db.currentOp() provides information about operations currently running on a MongoDB instance. Administrators can use it to investigate long-running queries, active writes, waiting operations, client connections, and other database activity. The information can help identify operations contributing to high CPU, memory, locking, or I\/O usage. It is often used during performance troubleshooting together with profiling and server metrics. Because active-operation output can contain substantial information, DBAs commonly filter or inspect the relevant fields rather than treating every listed operation as problematic. Proper authorization is required to obtain sensitive operational details.<\/span><\/p>\n

                          Question 53<\/b><\/h3>\n

                          Which feature protects MongoDB data stored on disk through encryption?<\/b><\/p>\n

                            \n
                          1. Queryable Encryption<\/span><\/li>\n
                          2. Client-side compression<\/span><\/li>\n
                          3. Encryption at rest<\/span><\/li>\n
                          4. Replica synchronization<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 3<\/b><\/p>\n

                            Explanation:<\/b><\/p>\n

                            Encryption at rest protects MongoDB data files and related stored information from being readable as plaintext if storage media or files are accessed outside the database’s normal security controls. It is different from TLS, which protects data while it travels between clients, servers, and cluster components. Encryption at rest can therefore complement network encryption rather than replace it. Depending on the deployment, key management can involve local or external key-management systems. DBAs should consider key protection, rotation procedures, operational recovery, and performance implications when implementing encryption for production database infrastructure.<\/span><\/p>\n

                            Question 54<\/b><\/h3>\n

                            What does a unique index prevent?<\/b><\/p>\n

                              \n
                            1. Unindexed documents<\/span><\/li>\n
                            2. Duplicate indexed values<\/span><\/li>\n
                            3. Missing collection metadata<\/span><\/li>\n
                            4. Repeated query plans<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 2<\/b><\/p>\n

                              Explanation:<\/b><\/p>\n

                              A unique index enforces uniqueness for the indexed key values. MongoDB rejects an insert or update when it would create a duplicate indexed value, subject to the specific behavior of the index definition and handling of missing or null values. Unique indexes are commonly used to enforce application-level identity requirements, such as unique usernames, account identifiers, or other business keys. They should be designed carefully because an incorrectly chosen uniqueness constraint can prevent legitimate records from being stored. Unique indexing therefore serves both query-performance and data-integrity purposes when applied to appropriate fields.<\/span><\/p>\n

                              Question 55<\/b><\/h3>\n

                              Which command displays statistics about indexes used by a collection?<\/b><\/p>\n

                                \n
                              1. db.indexUsage()<\/span><\/li>\n
                              2. db.getIndexes()<\/span><\/li>\n
                              3. db.indexStats()<\/span><\/li>\n
                              4. db.showIndexes()<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 3<\/b><\/p>\n

                                Explanation:<\/b><\/p>\n

                                db.collection.aggregate([{ $indexStats: {} }]) provides usage statistics for indexes on a collection. These statistics can help DBAs determine whether indexes are actually being accessed by queries. This is valuable when reviewing index overhead because every additional index can increase storage requirements and add work to insert and update operations. An index that appears unnecessary should not automatically be removed solely because its usage counter is low; workload patterns and monitoring periods must be considered. Index statistics are therefore most useful when combined with query analysis, application knowledge, and representative workload observations.<\/span><\/p>\n

                                Question 56<\/b><\/h3>\n

                                Which option can make a replica set member unavailable for client discovery while it continues replicating?<\/b><\/p>\n

                                  \n
                                1. priority: 2<\/span><\/li>\n
                                2. votes: 1<\/span><\/li>\n
                                3. hidden: true<\/span><\/li>\n
                                4. arbiterOnly: true<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 3<\/b><\/p>\n

                                  Explanation:<\/b><\/p>\n

                                  Setting a replica set member as hidden prevents normal client discovery from selecting that member for reads while allowing it to continue maintaining replicated data. Hidden members can be useful for dedicated operational tasks such as backups, reporting, or other workloads that administrators do not want mixed with normal application traffic. A hidden member is different from an arbiter because an arbiter does not maintain a copy of the data. The hidden setting is therefore particularly useful when administrators need a fully replicated database member that remains outside normal client routing.<\/span><\/p>\n

                                  Question 57<\/b><\/h3>\n

                                  Which command requests a replica set member to step down from primary?<\/b><\/p>\n

                                    \n
                                  1. rs.stepDown()<\/span><\/li>\n
                                  2. rs.leavePrimary()<\/span><\/li>\n
                                  3. rs.demote()<\/span><\/li>\n
                                  4. rs.transferPrimary()<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1<\/b><\/p>\n

                                    Explanation:<\/b><\/p>\n

                                    rs.stepDown() causes the current primary to relinquish its primary role, allowing the replica set election process to select another eligible member. This command can be useful during planned maintenance, server replacement, or controlled operational procedures. A stepdown can temporarily interrupt writes because the new primary must be elected and applications must reconnect or rediscover the new primary. Administrators should therefore perform stepdowns carefully and understand the configured priorities and member health before initiating one. Properly configured drivers generally handle replica set topology changes automatically after the election completes.<\/span><\/p>\n

                                    Question 58<\/b><\/h3>\n

                                    Which aggregation stage expands an array into separate pipeline documents?<\/b><\/p>\n

                                      \n
                                    1. $project<\/span><\/li>\n
                                    2. $match<\/span><\/li>\n
                                    3. $unwind<\/span><\/li>\n
                                    4. $sort<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 3<\/b><\/p>\n

                                      Explanation:<\/b><\/p>\n

                                      The $unwind stage deconstructs an array field so that each element can become a separate document in the aggregation pipeline. For example, a document containing several order items can be transformed into multiple pipeline documents, one for each item. This is particularly useful when individual array elements need to be filtered, grouped, sorted, or analyzed independently. $unwind can increase the number of documents flowing through subsequent stages, so DBAs should consider the resulting workload when optimizing aggregation pipelines. Proper filtering before expansion can sometimes reduce unnecessary processing.<\/span><\/p>\n

                                      Question 59<\/b><\/h3>\n

                                      Which setting helps prevent a replica set member from becoming primary while retaining voting participation?<\/b><\/p>\n

                                        \n
                                      1. hidden: true<\/span><\/li>\n
                                      2. priority: 0<\/span><\/li>\n
                                      3. secondaryDelaySecs<\/span><\/li>\n
                                      4. buildIndexes: false<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 2<\/b><\/p>\n

                                        Explanation:<\/b><\/p>\n

                                        A replica set member configured with priority: 0 cannot become primary. It can still participate in replication and, when configured appropriately, can retain its voting role. This is useful for members that should contribute to elections but should never host primary workloads, such as members in particular geographic locations or systems with operational constraints. This setting differs from hidden, which controls client discovery, and from delayed replication settings, which intentionally make a member’s data stale. Administrators should understand how priority, votes, hidden status, and delay interact when designing replica set topology.<\/span><\/p>\n

                                        Question 60<\/b><\/h3>\n

                                        Which feature allows MongoDB clients to maintain related operations across multiple commands?<\/b><\/p>\n

                                          \n
                                        1. Database profiler<\/span><\/li>\n
                                        2. Collection validator<\/span><\/li>\n
                                        3. Storage checkpoint<\/span><\/li>\n
                                        4. Client session<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 4<\/b><\/p>\n

                                          Explanation:<\/b><\/p>\n

                                          A client session provides a logical context that can span multiple MongoDB operations. Sessions are used by drivers and applications for features such as transactions, causal consistency, and retryable operations. A session gives the server additional context for associating related commands and maintaining the required operation state. Applications generally rely on the MongoDB driver to create and manage sessions rather than manually implementing the underlying protocol details. Understanding sessions is important for DBAs because session behavior affects transaction management, connection usage, timeout configuration, and the way modern applications interact with MongoDB clusters.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full MongoDB C100DBA Exam Dumps and Practice Test Dumps   Question 41 Which WiredTiger feature periodically persists dirty data to disk? Oplog rotation Query planning Journal replay Checkpoint processing Correct Answer: 4 Explanation: WiredTiger uses checkpoints to create consistent on-disk snapshots of data files. During checkpoint processing, modified or dirty pages are written to […]<\/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\/23284"}],"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=23284"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23284\/revisions"}],"predecessor-version":[{"id":23285,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23284\/revisions\/23285"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23284"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23284"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23284"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}