{"id":23290,"date":"2026-09-28T04:48:30","date_gmt":"2026-09-28T04:48:30","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23290"},"modified":"2026-09-28T04:48:30","modified_gmt":"2026-09-28T04:48:30","slug":"mongodb-c100dba-practice-test-questions-and-exam-dumps-part6-q101-120","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/mongodb-c100dba-practice-test-questions-and-exam-dumps-part6-q101-120\/","title":{"rendered":"MongoDB C100DBA Practice Test Questions and Exam Dumps Part6 Q101-120"},"content":{"rendered":"

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

 <\/p>\n

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

Which MongoDB command displays the current replication configuration?<\/b><\/p>\n

    \n
  1. rs.status()<\/span><\/li>\n
  2. rs.info()<\/span><\/li>\n
  3. rs.members()<\/span><\/li>\n
  4. rs.conf()<\/span><\/li>\n<\/ol>\n

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

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

    rs.conf() returns the replica set configuration document used by MongoDB. It contains settings for members, including host information, voting configuration, priorities, hidden status, and other member properties. DBAs use this command when reviewing topology or preparing controlled replica-set configuration changes. It differs from rs.status(), which focuses on the current operational condition of members rather than the configured topology. Reviewing the configuration is especially important before maintenance because incorrect priorities, votes, or member settings can affect elections and availability. Administrators should preserve an understanding of the existing configuration before making changes.<\/span><\/p>\n

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

    Which MongoDB feature provides ordered operations within a client context?<\/b><\/p>\n

      \n
    1. Client sessions<\/span><\/li>\n
    2. Storage checkpoints<\/span><\/li>\n
    3. Collection views<\/span><\/li>\n
    4. Query indexes<\/span><\/li>\n<\/ol>\n

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

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

      Client sessions provide MongoDB with a logical context for associating related operations. Sessions are used by drivers for capabilities such as transactions, causal consistency, and retryable operations. They allow MongoDB to maintain operation-related state across multiple commands issued by an application. Session management is generally handled through the MongoDB driver rather than through custom application-level identifiers. DBAs should understand session behavior when troubleshooting transaction workloads, connection utilization, and timeout-related problems. Sessions are not the same as network connections because one logical session can participate in application workflows independently of the physical connection management performed by the driver.<\/span><\/p>\n

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

      Which MongoDB index rule places equality fields before sort fields?<\/b><\/p>\n

        \n
      1. CAP principle<\/span><\/li>\n
      2. BASE model<\/span><\/li>\n
      3. ESR rule<\/span><\/li>\n
      4. CRUD model<\/span><\/li>\n<\/ol>\n

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

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

        The ESR, or Equality-Sort-Range, guideline helps administrators design effective compound indexes. Fields used for equality predicates are generally placed before fields used for sorting, followed by fields used for range conditions when the workload fits the guideline. This ordering can improve the ability of an index to support filtering and sorting efficiently. ESR is a design guideline rather than an absolute rule for every query. DBAs should validate index choices using actual query plans, data distribution, and workload behavior. Compound-index design should also consider which fields are frequently queried together and the operational cost of maintaining each index.<\/span><\/p>\n

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

        Which setting identifies the database directory used by a MongoDB server?<\/b><\/p>\n

          \n
        1. storagePath<\/span><\/li>\n
        2. dbPath<\/span><\/li>\n
        3. dataDirectory<\/span><\/li>\n
        4. databasePath<\/span><\/li>\n<\/ol>\n

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

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

          The dbPath configuration option specifies the directory where MongoDB stores its database files. It is one of the fundamental storage settings for a self-managed deployment. The directory must provide suitable capacity, permissions, and performance characteristics for the expected workload. DBAs should monitor free space and storage latency because problems at the filesystem level can directly affect database availability and performance. Changing dbPath requires an appropriate migration or startup procedure rather than simply editing the configuration while the server is running. Backup and recovery planning should also account for the selected storage location.<\/span><\/p>\n

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

          Which MongoDB object presents aggregation results without storing a separate result collection?<\/b><\/p>\n

            \n
          1. View<\/span><\/li>\n
          2. Snapshot<\/span><\/li>\n
          3. Replica<\/span><\/li>\n
          4. Index<\/span><\/li>\n<\/ol>\n

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

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

            A MongoDB view is a read-only database object defined by an aggregation pipeline. The view does not maintain a separate stored copy of the underlying result documents. When clients query the view, MongoDB processes its underlying pipeline against the source collections. Views can provide reusable transformations and controlled representations of data without duplicating the dataset. Because the pipeline executes when the view is queried, performance depends on the underlying collections, indexes, and aggregation stages. DBAs should evaluate workload frequency and pipeline complexity before using views for heavily accessed analytical or application-facing operations.<\/span><\/p>\n

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

            Which replica set property allows a member to receive no election votes?<\/b><\/p>\n

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

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

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

              The votes: 0 setting makes a replica set member non-voting. Such a member can still replicate data and serve specialized purposes, but it does not participate in replica-set election voting. Non-voting members can be useful when a deployment requires additional data-bearing members without increasing the number of voting members. This configuration must be planned carefully because voting-member distribution affects election behavior and fault tolerance. A non-voting member is distinct from a priority-zero member: priority controls eligibility to become primary, while votes determine participation in elections. These settings can be configured independently according to topology requirements.<\/span><\/p>\n

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

              Which command can manually force a replica set configuration refresh after changes?<\/b><\/p>\n

                \n
              1. rs.reload()<\/span><\/li>\n
              2. rs.refresh()<\/span><\/li>\n
              3. rs.syncConfig()<\/span><\/li>\n
              4. rs.updateConfig()<\/span><\/li>\n<\/ol>\n

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

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

                rs.reload() reloads the replica set configuration from the configuration source when supported by the MongoDB environment. It is useful in administrative situations where a member needs to refresh its understanding of the replica set configuration. Configuration management should normally follow MongoDB’s supported replica-set reconfiguration procedures rather than relying on ad hoc changes to configuration files. DBAs should distinguish between configuration refresh operations and commands that actually modify the replica set configuration. Before performing configuration changes, administrators should verify member health, connectivity, and the intended topology to minimize unexpected election or availability effects.<\/span><\/p>\n

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

                Which query result property indicates documents examined during execution?<\/b><\/p>\n

                  \n
                1. nReturned<\/span><\/li>\n
                2. executionTime<\/span><\/li>\n
                3. totalDocsExamined<\/span><\/li>\n
                4. documentsRead<\/span><\/li>\n<\/ol>\n

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

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

                  totalDocsExamined is an execution statistic available in explain output that indicates how many documents MongoDB examined while executing a query plan. Comparing this value with nReturned can help DBAs identify queries that examine substantially more documents than they return. A large examination-to-result ratio may indicate inefficient filtering, missing indexes, or a query plan that does not align well with the workload. This metric should be interpreted alongside totalKeysExamined, execution time, and the selected plan. Explain statistics provide valuable diagnostic evidence when investigating query performance.<\/span><\/p>\n

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

                  Which sharding method distributes documents according to hashed shard-key values?<\/b><\/p>\n

                    \n
                  1. Zone sharding<\/span><\/li>\n
                  2. Hashed sharding<\/span><\/li>\n
                  3. Range partitioning<\/span><\/li>\n
                  4. Manual chunk placement<\/span><\/li>\n<\/ol>\n

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

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

                    Hashed sharding applies a hashing function to shard-key values before distributing documents across shards. This approach can provide relatively even distribution when the original key has poor cardinality or is otherwise prone to creating uneven ranges. However, hashed shard keys are generally less suitable for workloads that depend heavily on range queries over the original field. Choosing a shard key requires balancing distribution, query targeting, cardinality, and workload access patterns. DBAs should evaluate actual application queries before selecting hashed sharding because a well-distributed key can still produce inefficient query routing.<\/span><\/p>\n

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

                    Which MongoDB process routes client requests in a sharded deployment?<\/b><\/p>\n

                      \n
                    1. mongod<\/span><\/li>\n
                    2. configsvr<\/span><\/li>\n
                    3. mongos<\/span><\/li>\n
                    4. replicator<\/span><\/li>\n<\/ol>\n

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

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

                      mongos is the query router used by clients to interact with a sharded MongoDB cluster. It receives client requests, consults cluster metadata, and routes operations to the appropriate shards. Applications normally connect to mongos rather than directly selecting individual shards for sharded workloads. Multiple mongos processes can be deployed to provide routing capacity and availability. DBAs should monitor router connectivity, resource utilization, and compatibility with the cluster topology. Properly designed applications use supported MongoDB drivers and connection strings so that routing and topology changes can be handled without hard-coding individual shard destinations.<\/span><\/p>\n

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

                      Which command reports replication information including the oplog window?<\/b><\/p>\n

                        \n
                      1. rs.status()<\/span><\/li>\n
                      2. rs.conf()<\/span><\/li>\n
                      3. rs.printReplicationInfo()<\/span><\/li>\n
                      4. rs.stepDown()<\/span><\/li>\n<\/ol>\n

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

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

                        rs.printReplicationInfo() reports information about the replica set’s oplog, including timestamps that help administrators understand the available replication window. The oplog window is important because a secondary that remains disconnected longer than the available window may no longer be able to catch up using normal replication. In such circumstances, an initial synchronization may be required. DBAs should monitor oplog size and write volume together because high write workloads can consume the available window quickly. Understanding this relationship is important when planning maintenance, disaster recovery, and expected secondary downtime.<\/span><\/p>\n

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

                        Which MongoDB setting controls the verbosity of server log messages?<\/b><\/p>\n

                          \n
                        1. logLevel<\/span><\/li>\n
                        2. logVerbosity<\/span><\/li>\n
                        3. messageLevel<\/span><\/li>\n
                        4. diagnosticLevel<\/span><\/li>\n<\/ol>\n

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

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

                          MongoDB’s log verbosity settings control how much diagnostic information is written to the server log. Increasing verbosity can provide additional details during troubleshooting, but excessive logging may generate substantial output and storage consumption. DBAs should generally use elevated verbosity selectively and return to normal levels after investigating an issue. Log information can be particularly valuable for diagnosing connectivity, replication, storage, and operational problems. Administrators should also ensure that log files are retained and rotated appropriately so that increased diagnostic output does not unexpectedly consume available disk space.<\/span><\/p>\n

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

                          Which index type is designed specifically for text-search queries?<\/b><\/p>\n

                            \n
                          1. Text index<\/span><\/li>\n
                          2. Vector index<\/span><\/li>\n
                          3. Range index<\/span><\/li>\n
                          4. Session index<\/span><\/li>\n<\/ol>\n

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

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

                            A MongoDB text index supports text-search queries against string content. It indexes words from selected fields and enables the $text query operator to search for matching terms. Text indexes are useful for basic text-search requirements, although applications with advanced search needs may require specialized search technologies. DBAs should consider index size, language configuration, tokenization behavior, and write overhead before adding text indexes to large collections. The indexed fields should reflect the application’s actual search requirements. Text indexing should also be evaluated against alternative search capabilities when sophisticated relevance or search features are needed.<\/span><\/p>\n

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

                            Which command displays detailed information about a running operation?<\/b><\/p>\n

                              \n
                            1. db.operationInfo()<\/span><\/li>\n
                            2. db.currentOp()<\/span><\/li>\n
                            3. db.activeTask()<\/span><\/li>\n
                            4. db.runningQueries()<\/span><\/li>\n<\/ol>\n

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

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

                              db.currentOp() provides information about operations currently executing on the MongoDB server. The output can include operation identifiers, namespaces, client information, runtime details, locks, and other diagnostic fields depending on the operation and MongoDB version. DBAs commonly use this command when investigating long-running operations or unexpected resource consumption. After identifying an operation, administrators can determine whether it should continue, be optimized, or be terminated using appropriate administrative controls. Current-operation data should be interpreted in context because a long-running operation is not automatically a problematic operation.<\/span><\/p>\n

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

                              Which sharding feature assigns data ranges to preferred geographic or logical locations?<\/b><\/p>\n

                                \n
                              1. Hashed distribution<\/span><\/li>\n
                              2. Zone sharding<\/span><\/li>\n
                              3. Random placement<\/span><\/li>\n
                              4. Oplog routing<\/span><\/li>\n<\/ol>\n

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

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

                                Zone sharding allows administrators to associate ranges of shard-key values with designated zones and assign shards to those zones. This can help control where particular data ranges are stored based on geographic, regulatory, hardware, or workload requirements. Zone configuration works with shard-key ranges and requires careful planning to avoid creating uneven distribution or operational bottlenecks. DBAs should monitor chunk placement and balancing behavior after introducing zones. Zone sharding is different from hashed distribution because it provides an explicit placement mechanism rather than simply attempting to spread hashed keys across available shards.<\/span><\/p>\n

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

                                Which command is commonly used to inspect replication state of all replica members?<\/b><\/p>\n

                                  \n
                                1. rs.status()<\/span><\/li>\n
                                2. rs.members()<\/span><\/li>\n
                                3. rs.health()<\/span><\/li>\n
                                4. rs.replicaInfo()<\/span><\/li>\n<\/ol>\n

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

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

                                  rs.status() provides a detailed view of the current state of replica set members. Administrators can use it to identify the primary, examine secondary health, review synchronization progress, and investigate state transitions. The command is particularly useful during replication troubleshooting because it combines several operational indicators in one response. DBAs should review fields such as member state, health, optime information, and sync source when diagnosing lag or connectivity issues. Replica-set status should be interpreted alongside server logs and system monitoring to determine the underlying cause of a replication problem.<\/span><\/p>\n

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

                                  Which aggregation stage removes selected fields from documents?<\/b><\/p>\n

                                    \n
                                  1. $unset<\/span><\/li>\n
                                  2. $removeFields<\/span><\/li>\n
                                  3. $dropFields<\/span><\/li>\n
                                  4. $exclude<\/span><\/li>\n<\/ol>\n

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

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

                                    The $unset aggregation stage removes specified fields from documents flowing through a pipeline. It can be useful when preparing output for clients, simplifying documents before later processing, or excluding sensitive or unnecessary fields from results. $unset operates as part of the aggregation pipeline and does not permanently modify the source collection. Administrators should distinguish pipeline transformations from update operations because aggregation output normally represents transformed results rather than direct changes to stored documents. Careful field selection can also reduce the amount of information passed to downstream application components.<\/span><\/p>\n

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

                                    Which command shows the server’s current connection and operation counters?<\/b><\/p>\n

                                      \n
                                    1. db.metrics()<\/span><\/li>\n
                                    2. db.statusCounters()<\/span><\/li>\n
                                    3. db.serverStatus()<\/span><\/li>\n
                                    4. db.runtimeCounters()<\/span><\/li>\n<\/ol>\n

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

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

                                      db.serverStatus() provides server-level metrics, including connection information and operation counters. These measurements can help DBAs identify changes in workload intensity, connection growth, and database activity. For example, operation counters can be compared over time to understand whether read or write activity has increased significantly. Connection metrics can also reveal unusual client behavior or capacity concerns. Because serverStatus() produces a large response, monitoring systems commonly extract specific fields and track them over time. Trend analysis is more useful than interpreting a single instantaneous metric without workload context.<\/span><\/p>\n

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

                                      Which sharded-cluster component stores persistent cluster metadata?<\/b><\/p>\n

                                        \n
                                      1. mongos<\/span><\/li>\n
                                      2. Config servers<\/span><\/li>\n
                                      3. Query clients<\/span><\/li>\n
                                      4. Shard routers<\/span><\/li>\n<\/ol>\n

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

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

                                        Config servers store persistent metadata required for managing a sharded MongoDB cluster. This metadata includes information about sharded collections, chunk placement, database ownership, and other cluster configuration details. In modern MongoDB deployments, config servers are normally deployed as a replica set to provide redundancy. mongos processes client requests and uses this metadata for routing, but it does not replace the config-server replica set as the persistent metadata store. Maintaining healthy config servers is therefore critical to the operational stability of a sharded environment.<\/span><\/p>\n

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

                                        Which command can temporarily prevent a replica set member from becoming primary?<\/b><\/p>\n

                                          \n
                                        1. rs.freeze()<\/span><\/li>\n
                                        2. rs.pauseElection()<\/span><\/li>\n
                                        3. rs.preventPrimary()<\/span><\/li>\n
                                        4. rs.holdElection()<\/span><\/li>\n<\/ol>\n

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

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

                                          rs.freeze() can temporarily prevent a replica set member from becoming primary for a specified period. It is useful during controlled maintenance or topology management when an administrator wants to keep a particular member from winning an election. The command should be used carefully because replica-set elections are part of MongoDB’s high-availability mechanism. Administrators should understand the current primary, member health, priorities, and voting configuration before applying election-related controls. After the freeze period ends, normal election eligibility can resume according to the replica set’s configured rules.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full MongoDB C100DBA Exam Dumps and Practice Test Dumps   Question 101 Which MongoDB command displays the current replication configuration? rs.status() rs.info() rs.members() rs.conf() Correct Answer: 4 Explanation: rs.conf() returns the replica set configuration document used by MongoDB. It contains settings for members, including host information, voting configuration, priorities, hidden status, and other member […]<\/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\/23290"}],"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=23290"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23290\/revisions"}],"predecessor-version":[{"id":23291,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23290\/revisions\/23291"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}