{"id":23302,"date":"2026-09-28T04:51:14","date_gmt":"2026-09-28T04:51:14","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=23302"},"modified":"2026-09-28T04:51:14","modified_gmt":"2026-09-28T04:51:14","slug":"mongodb-c100dba-practice-test-questions-and-exam-dumps-part12-q221-240","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/mongodb-c100dba-practice-test-questions-and-exam-dumps-part12-q221-240\/","title":{"rendered":"MongoDB C100DBA Practice Test Questions and Exam Dumps Part12 Q221-240"},"content":{"rendered":"

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

 <\/p>\n

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

Which MongoDB role provides permission to monitor cluster activity?<\/b><\/p>\n

    \n
  1. readCluster<\/span><\/li>\n
  2. clusterReader<\/span><\/li>\n
  3. clusterMonitor<\/span><\/li>\n
  4. monitorAnyDatabase<\/span><\/li>\n<\/ol>\n

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

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

    The clusterMonitor built-in role provides privileges intended for monitoring MongoDB deployments. It is commonly associated with monitoring tools and administrative accounts that need to inspect server and cluster metrics without requiring unrestricted administrative permissions. Using a monitoring-specific role supports the principle of least privilege because monitoring users do not necessarily need the ability to modify databases or configuration. DBAs should evaluate the exact privileges required by their monitoring solution and avoid assigning broad roles such as root when narrower permissions are sufficient.<\/span><\/p>\n

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

    Which MongoDB role permits database backup-related operations?<\/b><\/p>\n

      \n
    1. backup<\/span><\/li>\n
    2. databaseBackup<\/span><\/li>\n
    3. backupOperator<\/span><\/li>\n
    4. clusterBackup<\/span><\/li>\n<\/ol>\n

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

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

      The backup built-in role provides privileges intended for performing MongoDB backup operations. It is designed to give backup processes the permissions required for supported backup workflows without automatically granting unrestricted administrative authority. DBAs should assign backup privileges only to dedicated backup accounts or services that require them. The exact permissions needed can also depend on the backup method being used. Administrators should regularly review backup credentials and protect them carefully because backup access can expose substantial amounts of database information.<\/span><\/p>\n

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

      Which MongoDB role provides restore-related privileges?<\/b><\/p>\n

        \n
      1. restoreOperator<\/span><\/li>\n
      2. databaseRestore<\/span><\/li>\n
      3. restore<\/span><\/li>\n
      4. clusterRestore<\/span><\/li>\n<\/ol>\n

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

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

        The restore built-in role provides privileges needed for supported MongoDB restoration activities. Restore operations can modify or replace significant amounts of database data, so the associated credentials should be carefully controlled. DBAs should separate backup and restore responsibilities where organizational security requirements call for it and should test restoration procedures regularly. A restore account should not automatically be used for routine application access. Administrators should also verify that the selected restoration process is compatible with the MongoDB deployment version and backup format being used.<\/span><\/p>\n

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

        Which MongoDB role grants read access across all databases?<\/b><\/p>\n

          \n
        1. globalReader<\/span><\/li>\n
        2. readAnyDatabase<\/span><\/li>\n
        3. readAllDatabases<\/span><\/li>\n
        4. databaseReader<\/span><\/li>\n<\/ol>\n

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

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

          The readAnyDatabase built-in role provides read privileges across databases in the MongoDB deployment. It can be useful for centralized reporting, auditing, or operational tools that need to inspect information from multiple databases. Because it provides broad visibility, it should not be assigned when an account only needs access to a limited set of databases. DBAs should consider creating narrower custom roles when cross-database access is required for only selected resources. Regular access reviews can help ensure that broad read permissions remain justified.<\/span><\/p>\n

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

          Which MongoDB role provides read and write access across databases?<\/b><\/p>\n

            \n
          1. writeAnyDatabase<\/span><\/li>\n
          2. readWriteAll<\/span><\/li>\n
          3. readWriteAnyDatabase<\/span><\/li>\n
          4. globalReadWrite<\/span><\/li>\n<\/ol>\n

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

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

            The readWriteAnyDatabase built-in role provides read and write privileges across databases. This is broader than assigning read and write access to a single application database. Such a role may be useful for certain administrative or integration scenarios, but it should be assigned carefully because it permits modifications across many databases. DBAs should prefer database-specific roles when an account does not require global write access. Broad write privileges can increase the impact of application defects, accidental commands, or compromised credentials.<\/span><\/p>\n

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

            Which MongoDB command changes a user’s password?<\/b><\/p>\n

              \n
            1. db.changePassword()<\/span><\/li>\n
            2. db.updatePassword()<\/span><\/li>\n
            3. db.setUserPassword()<\/span><\/li>\n
            4. db.modifyPassword()<\/span><\/li>\n<\/ol>\n

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

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

              db.changePassword() changes the password associated with the currently authenticated MongoDB user. It is useful for routine credential rotation when password-based authentication is being used. Password changes should be coordinated with applications, automation, and secret-management systems that depend on the affected credentials. DBAs should avoid placing passwords directly in scripts or configuration files where possible. Strong credential management and regular rotation policies can reduce exposure from compromised credentials. Authentication configuration should also be reviewed whenever users or applications transition to another authentication mechanism.<\/span><\/p>\n

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

              Which MongoDB command removes a database user?<\/b><\/p>\n

                \n
              1. db.removeUser()<\/span><\/li>\n
              2. db.deleteUser()<\/span><\/li>\n
              3. db.dropUserAccount()<\/span><\/li>\n
              4. db.eraseUser()<\/span><\/li>\n<\/ol>\n

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

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

                db.deleteUser() removes a specified user from the database where the command is executed. User deletion is appropriate when an account is no longer required or when access needs to be permanently removed. DBAs should first verify whether applications, automation, or operational procedures still depend on the account. Removing a user is different from simply revoking roles because the account itself is deleted. Administrators should also review related credentials and external identity mappings to ensure that removing the MongoDB user achieves the intended access-control result.<\/span><\/p>\n

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

                Which MongoDB command returns information about all users in a database?<\/b><\/p>\n

                  \n
                1. db.getUsers()<\/span><\/li>\n
                2. db.listUsers()<\/span><\/li>\n
                3. db.showUsers()<\/span><\/li>\n
                4. db.usersInfo()<\/span><\/li>\n<\/ol>\n

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

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

                  db.getUsers() returns information about users associated with the current database, subject to the privileges of the executing account. It is useful for administrative reviews and automation that needs to inspect user configuration. DBAs can use the information to verify role assignments and identify accounts that may require changes. User-management commands should be executed with appropriately privileged administrative credentials. When auditing authorization, administrators should consider both direct user roles and inherited privileges because effective access may be broader than a simple list of directly assigned roles suggests.<\/span><\/p>\n

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

                  Which MongoDB command invalidates cached authorization information?<\/b><\/p>\n

                    \n
                  1. db.clearRolesCache()<\/span><\/li>\n
                  2. invalidateUserCache<\/span><\/li>\n
                  3. db.refreshAuthorization()<\/span><\/li>\n
                  4. clearUserPrivileges<\/span><\/li>\n<\/ol>\n

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

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

                    The invalidateUserCache command invalidates cached user and authorization information maintained by MongoDB. It can be useful when administrators need authorization-related cached data to be refreshed after changes to users or roles. Cache invalidation should normally be performed only when required by the administrative situation because MongoDB manages authorization information automatically. DBAs should first verify the underlying user or role configuration before assuming that cached information is the cause of an access problem. Properly planned authorization changes and supported administrative procedures reduce the need for manual cache operations.<\/span><\/p>\n

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

                    Which MongoDB command retrieves the current authentication configuration?<\/b><\/p>\n

                      \n
                    1. authConfiguration<\/span><\/li>\n
                    2. getAuthentication<\/span><\/li>\n
                    3. getCmdLineOpts<\/span><\/li>\n
                    4. showAuthSettings<\/span><\/li>\n<\/ol>\n

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

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

                      getCmdLineOpts returns command-line and configuration-file options recognized by the MongoDB server. It can help administrators inspect configuration settings related to authentication, networking, storage, and other server behavior. This makes it useful when troubleshooting configuration differences between environments. DBAs should distinguish configuration inspection from runtime status monitoring because the command focuses on server startup options rather than providing a complete view of current workload metrics. Configuration information should also be protected appropriately because it can reveal operational details about the deployment.<\/span><\/p>\n

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

                      Which command returns MongoDB server build information?<\/b><\/p>\n

                        \n
                      1. buildInfo<\/span><\/li>\n
                      2. serverVersion<\/span><\/li>\n
                      3. getBuild<\/span><\/li>\n
                      4. versionInfo<\/span><\/li>\n<\/ol>\n

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

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

                        The buildInfo command returns information about the MongoDB server build, including version and build-related details. Administrators can use it when verifying software versions, troubleshooting compatibility, or documenting deployment environments. Build information can be especially important before upgrades because MongoDB features and configuration behavior can depend on the server version. DBAs should collect version information from all relevant deployment components when investigating compatibility issues rather than assuming every component runs the same release. Accurate build identification also helps support and maintenance activities.<\/span><\/p>\n

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

                        Which MongoDB command checks whether the server is responding?<\/b><\/p>\n

                          \n
                        1. healthCheck<\/span><\/li>\n
                        2. serverPing<\/span><\/li>\n
                        3. ping<\/span><\/li>\n
                        4. checkServer<\/span><\/li>\n<\/ol>\n

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

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

                          The ping command provides a simple way to verify that a MongoDB server can respond to a command request. It is useful for connectivity checks, health monitoring, and basic troubleshooting. A successful ping confirms that the server responded, but it does not by itself prove that an application query will succeed or that every replica-set component is healthy. DBAs should combine basic connectivity checks with appropriate topology, replication, and resource monitoring when diagnosing production issues. Health checks should reflect the actual availability requirements of the application.<\/span><\/p>\n

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

                          Which MongoDB command identifies the client’s remote network address?<\/b><\/p>\n

                            \n
                          1. clientAddress<\/span><\/li>\n
                          2. whatsmyuri<\/span><\/li>\n
                          3. remoteClient<\/span><\/li>\n
                          4. connectionOrigin<\/span><\/li>\n<\/ol>\n

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

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

                            The whatsmyuri command can return information identifying the client’s network address as seen by the MongoDB server. This can assist administrators when troubleshooting connection routing, access-control behavior, or unexpected client origins. Network addresses may be especially useful in environments containing application servers, proxies, containers, or multiple network interfaces. DBAs should remember that network identity alone does not establish whether a client is authorized. Authentication, authorization, and network controls should be evaluated together when investigating connection security.<\/span><\/p>\n

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

                            Which MongoDB command retrieves information about a server’s runtime logs?<\/b><\/p>\n

                              \n
                            1. showLogs<\/span><\/li>\n
                            2. getLog<\/span><\/li>\n
                            3. readLogs<\/span><\/li>\n
                            4. serverLogs<\/span><\/li>\n<\/ol>\n

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

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

                              The getLog command retrieves available MongoDB server log information through supported administrative interfaces. It can be useful for troubleshooting events such as connection problems, configuration issues, and server warnings. DBAs should recognize that database logs can contain operationally sensitive information, so access should be restricted to appropriately privileged administrators. For comprehensive production log management, organizations may also use centralized logging systems. Reviewing logs together with metrics, topology information, and application behavior provides a more complete basis for diagnosing database incidents.<\/span><\/p>\n

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

                              Which MongoDB command changes the verbosity level for server logging?<\/b><\/p>\n

                                \n
                              1. setParameter<\/span><\/li>\n
                              2. setLogLevel<\/span><\/li>\n
                              3. changeVerbosity<\/span><\/li>\n
                              4. configureLogging<\/span><\/li>\n<\/ol>\n

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

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

                                The setParameter command can modify supported MongoDB server parameters, including logging-related settings such as log verbosity. Increasing verbosity can provide additional diagnostic information during troubleshooting, while excessive verbosity can generate substantial log volume. DBAs should therefore use higher logging levels selectively and return settings to appropriate operational values after troubleshooting. Parameter changes should be made carefully because some parameters affect server behavior immediately, while others may have deployment-specific requirements. Administrators should confirm the supported parameter and valid range for their MongoDB version.<\/span><\/p>\n

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

                                Which MongoDB command can rotate the server log file?<\/b><\/p>\n

                                  \n
                                1. rotateLog<\/span><\/li>\n
                                2. logRotate<\/span><\/li>\n
                                3. switchLog<\/span><\/li>\n
                                4. newLogFile<\/span><\/li>\n<\/ol>\n

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

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

                                  The logRotate command requests rotation of the MongoDB server log. Log rotation helps prevent a single log file from growing indefinitely and supports operational log-retention practices. The exact behavior can depend on how MongoDB logging is configured, including whether logs are written to a file or handled through another logging mechanism. DBAs should coordinate log rotation with operating-system and centralized logging policies. Retention and archival procedures should also ensure that important diagnostic information remains available while preventing uncontrolled disk consumption.<\/span><\/p>\n

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

                                  Which MongoDB command obtains the current default read and write concern settings?<\/b><\/p>\n

                                    \n
                                  1. getDefaultRWConcern<\/span><\/li>\n
                                  2. showDefaultConcern<\/span><\/li>\n
                                  3. readWriteDefaults<\/span><\/li>\n
                                  4. getRWDefaults<\/span><\/li>\n<\/ol>\n

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

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

                                    getDefaultRWConcern returns information about the deployment’s configured default read and write concern settings. These defaults can influence client operations when an explicit read or write concern is not supplied. DBAs can use the command to verify configuration during deployment reviews, troubleshooting, or consistency investigations. Administrators should distinguish deployment-wide defaults from concerns explicitly specified by individual applications or operations. Understanding the effective read and write concern is important when evaluating durability, consistency, and acknowledgment behavior across different workloads.<\/span><\/p>\n

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

                                    Which MongoDB command configures default read and write concerns?<\/b><\/p>\n

                                      \n
                                    1. setRWDefaults<\/span><\/li>\n
                                    2. configureDefaultConcern<\/span><\/li>\n
                                    3. setDefaultRWConcern<\/span><\/li>\n
                                    4. applyDefaultConsistency<\/span><\/li>\n<\/ol>\n

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

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

                                      setDefaultRWConcern configures default read and write concern behavior for a MongoDB deployment. Default settings can establish baseline consistency and acknowledgment behavior for clients that do not explicitly specify their own concerns. DBAs should carefully evaluate the operational effects before changing these settings because they can influence many workloads simultaneously. Applications with explicit concerns may behave differently from those relying on defaults. Administrators should document changes, test them against representative workloads, and verify the resulting configuration using the corresponding inspection command.<\/span><\/p>\n

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

                                      Which MongoDB command retrieves cluster-wide parameter values?<\/b><\/p>\n

                                        \n
                                      1. getClusterParameter<\/span><\/li>\n
                                      2. showClusterSettings<\/span><\/li>\n
                                      3. clusterParameters<\/span><\/li>\n
                                      4. readClusterParameter<\/span><\/li>\n<\/ol>\n

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

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

                                        getClusterParameter retrieves configured cluster parameter values. Cluster parameters provide a mechanism for controlling supported deployment-wide settings across MongoDB environments. DBAs can use the command to inspect configuration when troubleshooting behavior that depends on cluster-level settings. Administrators should consult the documentation for their specific MongoDB release because supported parameters and operational behavior can vary by version. Cluster-wide changes should be carefully planned because their effects can extend across multiple servers and workloads rather than remaining limited to a single database or client connection.<\/span><\/p>\n

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

                                        Which MongoDB command changes supported cluster-wide parameter values?<\/b><\/p>\n

                                          \n
                                        1. configureClusterParameter<\/span><\/li>\n
                                        2. setClusterParameter<\/span><\/li>\n
                                        3. updateClusterSetting<\/span><\/li>\n
                                        4. modifyClusterParameter<\/span><\/li>\n<\/ol>\n

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

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

                                          setClusterParameter changes supported cluster-wide parameter values in MongoDB deployments where the relevant parameter is available. Because these settings can affect multiple components or workloads, administrators should validate the intended value and operational impact before making changes. DBAs should also record configuration modifications so that future troubleshooting can distinguish expected behavior from accidental changes. The command should only be used for supported parameters and compatible MongoDB versions. After a change, administrators can use the corresponding retrieval command to verify the resulting cluster parameter configuration.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full MongoDB C100DBA Exam Dumps and Practice Test Dumps   Question 221 Which MongoDB role provides permission to monitor cluster activity? readCluster clusterReader clusterMonitor monitorAnyDatabase Correct Answer: 3 Explanation: The clusterMonitor built-in role provides privileges intended for monitoring MongoDB deployments. It is commonly associated with monitoring tools and administrative accounts that need to inspect […]<\/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\/23302"}],"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=23302"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23302\/revisions"}],"predecessor-version":[{"id":23303,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/23302\/revisions\/23303"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=23302"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=23302"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=23302"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}