{"id":11847,"date":"2026-09-14T12:34:41","date_gmt":"2026-09-14T12:34:41","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=11847"},"modified":"2026-09-14T12:34:41","modified_gmt":"2026-09-14T12:34:41","slug":"microsoft-dp-800-practice-test-questions-and-exam-dumps-part-17-q321-q340","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-dp-800-practice-test-questions-and-exam-dumps-part-17-q321-q340\/","title":{"rendered":"Microsoft DP-800 Practice Test Questions and Exam Dumps Part 17: Q321\u2013Q340"},"content":{"rendered":"

View Full\u00a0Microsoft DP-800 Exam Dumps<\/a>\u00a0and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

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

Which T-SQL statement removes a previously granted or denied permission from a database principal?<\/b><\/p>\n

    \n
  1. DROP<\/span><\/li>\n
  2. REVOKE<\/span><\/li>\n
  3. GRANT<\/span><\/li>\n
  4. ALTER<\/span><\/li>\n<\/ol>\n

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

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

    The <\/span>REVOKE<\/span> statement removes a previously granted or denied permission from a database principal. It is commonly used when access should no longer be explicitly assigned to a user or role. <\/span>GRANT<\/span> provides permissions, while <\/span>DENY<\/span> explicitly prevents a permission. Administrators should understand SQL Server’s permission hierarchy because a user may still receive access through another role even after a direct permission is revoked. Regular permission reviews help maintain least-privilege security.<\/span><\/p>\n

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

    Which T-SQL statement explicitly prevents a user or role from performing a specific operation?<\/b><\/p>\n

      \n
    1. GRANT<\/span><\/li>\n
    2. REVOKE<\/span><\/li>\n
    3. DENY<\/span><\/li>\n
    4. EXECUTE<\/span><\/li>\n<\/ol>\n

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

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

      The <\/span>DENY<\/span> statement explicitly prevents a database principal from receiving a specified permission through normal permission inheritance. It is different from <\/span>REVOKE<\/span>, which removes an explicit permission assignment. Administrators should use DENY carefully because SQL Server permission inheritance and ownership can affect how permissions are evaluated. Before applying a DENY, administrators should understand the user’s membership in database roles and how the requested permission is inherited.<\/span><\/p>\n

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

      Which database role provides broad administrative permissions within a SQL Server database?<\/b><\/p>\n

        \n
      1. db_datareader<\/span><\/li>\n
      2. db_datawriter<\/span><\/li>\n
      3. db_owner<\/span><\/li>\n
      4. public<\/span><\/li>\n<\/ol>\n

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

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

        The <\/span>db_owner<\/span> fixed database role provides extensive control over a database. Members can perform most database-level administrative actions and can manage permissions and database objects. Because this role provides broad privileges, administrators should avoid assigning it to users or applications unless it is genuinely required. For normal application workloads, more limited roles such as <\/span>db_datareader<\/span>, <\/span>db_datawriter<\/span>, or custom roles are generally preferable to follow the principle of least privilege.<\/span><\/p>\n

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

        Which fixed database role allows members to read data from all user tables and views?<\/b><\/p>\n

          \n
        1. db_datareader<\/span><\/li>\n
        2. db_datawriter<\/span><\/li>\n
        3. db_owner<\/span><\/li>\n
        4. db_ddladmin<\/span><\/li>\n<\/ol>\n

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

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

          The <\/span>db_datareader<\/span> fixed database role allows members to read data from all user tables and views in the database. It is useful when a user or application needs broad read access without requiring permissions to modify data. However, assigning this role may provide more access than a specific application actually needs. Administrators should consider creating custom roles with permissions limited to the required tables, views, or procedures when stronger least-privilege controls are needed.<\/span><\/p>\n

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

          Which fixed database role allows members to insert, update, and delete data in all user tables?<\/b><\/p>\n

            \n
          1. db_datareader<\/span><\/li>\n
          2. db_datawriter<\/span><\/li>\n
          3. db_owner<\/span><\/li>\n
          4. db_securityadmin<\/span><\/li>\n<\/ol>\n

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

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

            The <\/span>db_datawriter<\/span> fixed database role allows members to insert, update, and delete data in all user tables. It does not provide the same broad administrative privileges as <\/span>db_owner<\/span>. However, it can still be excessive for applications that only need access to a small number of tables. Administrators should consider custom database roles when applications require limited write access. Granting only the necessary permissions helps reduce the potential impact of compromised credentials.<\/span><\/p>\n

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

            Which database role is generally used to allow users to execute stored procedures and functions when appropriate permissions are assigned?<\/b><\/p>\n

              \n
            1. db_executor<\/span><\/li>\n
            2. db_datareader<\/span><\/li>\n
            3. db_backupoperator<\/span><\/li>\n
            4. db_ddladmin<\/span><\/li>\n<\/ol>\n

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

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

              SQL Server does not provide a built-in fixed database role named <\/span>db_executor<\/span> by default, but administrators can create a custom database role with that name and grant it EXECUTE permissions. This pattern is useful when applications need to execute stored procedures without receiving broad direct access to tables. A custom execution role can support least privilege by exposing controlled database operations through procedures rather than granting unnecessary table-level permissions.<\/span><\/p>\n

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

              Which system catalog view contains information about database-level principals such as users and roles?<\/b><\/p>\n

                \n
              1. sys.database_principals<\/span><\/li>\n
              2. sys.tables<\/span><\/li>\n
              3. sys.columns<\/span><\/li>\n
              4. sys.indexes<\/span><\/li>\n<\/ol>\n

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

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

                sys.database_principals<\/span> contains information about database-level security principals, including database users, roles, and other principal types. Administrators can query this catalog view when investigating database security configuration. It can be combined with other catalog views to determine role memberships and permissions. Understanding database principals is important when troubleshooting authorization problems or reviewing whether users and applications have more access than required.<\/span><\/p>\n

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

                Which catalog view can be used to examine explicit database permissions assigned to principals?<\/b><\/p>\n

                  \n
                1. sys.tables<\/span><\/li>\n
                2. sys.database_permissions<\/span><\/li>\n
                3. sys.columns<\/span><\/li>\n
                4. sys.databases<\/span><\/li>\n<\/ol>\n

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

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

                  sys.database_permissions<\/span> contains information about explicit permissions assigned to database principals. Administrators can query it to investigate GRANT, DENY, and other permission states at the database level. This is useful when troubleshooting authorization problems or performing security reviews. Because permissions can also come through role membership and ownership, administrators should combine this view with information from <\/span>sys.database_principals<\/span> and role-membership metadata for a complete understanding of effective access.<\/span><\/p>\n

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

                  Which database object provides a namespace that can be used to organize tables, views, procedures, and other objects?<\/b><\/p>\n

                    \n
                  1. Schema<\/span><\/li>\n
                  2. Index<\/span><\/li>\n
                  3. Trigger<\/span><\/li>\n
                  4. Constraint<\/span><\/li>\n<\/ol>\n

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

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

                    A schema is a logical container for database objects such as tables, views, stored procedures, and functions. Schemas help organize objects and can also simplify permission management. Administrators can grant permissions on a schema rather than individually assigning permissions to every object within it. This can make security administration easier in larger databases. Schemas are separate from database users, although users can own or have permissions on schemas.<\/span><\/p>\n

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

                    Which permission is required to execute a stored procedure?<\/b><\/p>\n

                      \n
                    1. SELECT<\/span><\/li>\n
                    2. INSERT<\/span><\/li>\n
                    3. EXECUTE<\/span><\/li>\n
                    4. ALTER<\/span><\/li>\n<\/ol>\n

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

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

                      The <\/span>EXECUTE<\/span> permission allows a user or role to execute a stored procedure or other executable database object when applicable. Administrators can grant EXECUTE directly on an individual procedure or at a broader scope such as a schema. Granting EXECUTE on procedures can support least privilege because applications may perform required operations without receiving direct access to underlying tables. Administrators should review procedure permissions regularly and avoid granting unnecessary privileges.<\/span><\/p>\n

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

                      Which SQL Server feature can encrypt sensitive column values so that the database engine does not normally see the plaintext data?<\/b><\/p>\n

                        \n
                      1. Dynamic Data Masking<\/span><\/li>\n
                      2. Always Encrypted<\/span><\/li>\n
                      3. Row-Level Security<\/span><\/li>\n
                      4. Data compression<\/span><\/li>\n<\/ol>\n

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

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

                        Always Encrypted is designed to protect sensitive data by encrypting selected column values so that the database engine does not normally see the plaintext values. Encryption and decryption are handled by the client-side application or driver. This provides stronger protection for sensitive information than Dynamic Data Masking, which only changes how data is displayed to certain users. Administrators should carefully evaluate application compatibility, key management, supported operations, and performance before enabling Always Encrypted.<\/span><\/p>\n

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

                        Which security feature controls access to individual rows based on a user’s identity or role?<\/b><\/p>\n

                          \n
                        1. Transparent Data Encryption<\/span><\/li>\n
                        2. Row-Level Security<\/span><\/li>\n
                        3. Always Encrypted<\/span><\/li>\n
                        4. Database backup<\/span><\/li>\n<\/ol>\n

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

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

                          Row-Level Security (RLS) uses security predicates to control which rows a user can access or modify. It is useful when multiple users or tenants share the same tables but should only see their own data. For example, a multi-tenant application can use RLS to restrict each customer to rows belonging to that customer. Administrators should thoroughly test RLS policies because incorrect predicates can unintentionally expose data or prevent legitimate users from accessing required rows.<\/span><\/p>\n

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

                          Which Azure SQL security feature encrypts data at rest without requiring changes to application queries?<\/b><\/p>\n

                            \n
                          1. Always Encrypted<\/span><\/li>\n
                          2. Transparent Data Encryption<\/span><\/li>\n
                          3. Row-Level Security<\/span><\/li>\n
                          4. Dynamic Data Masking<\/span><\/li>\n<\/ol>\n

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

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

                            Transparent Data Encryption (TDE) encrypts database files and related data at rest while remaining transparent to applications. Applications continue sending normal queries without implementing encryption and decryption logic for the database files. TDE helps protect data if storage media or backup files are accessed without authorization. It is different from Always Encrypted, which protects selected sensitive column values from access by the database engine and requires appropriate client-side support.<\/span><\/p>\n

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

                            Which SQL Server feature can record login activity and database operations for security investigations?<\/b><\/p>\n

                              \n
                            1. SQL Server Audit<\/span><\/li>\n
                            2. Data compression<\/span><\/li>\n
                            3. Query Store<\/span><\/li>\n
                            4. Resource Governor<\/span><\/li>\n<\/ol>\n

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

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

                              SQL Server Audit provides a mechanism for recording selected server-level and database-level events. Administrators can configure audit specifications to capture activities such as authentication events, permission changes, and database operations. Audit records can support compliance requirements, security investigations, and monitoring. Administrators should carefully select the events to capture and protect the audit destination because audit data can contain sensitive information. Appropriate retention policies should also be established.<\/span><\/p>\n

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

                              Which SQL Server feature can identify login failures and other security-related events for auditing?<\/b><\/p>\n

                                \n
                              1. SQL Server Audit<\/span><\/li>\n
                              2. Index rebuild<\/span><\/li>\n
                              3. Query Store<\/span><\/li>\n
                              4. Database snapshot<\/span><\/li>\n<\/ol>\n

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

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

                                SQL Server Audit can capture security-related events, including selected authentication and database activity events, depending on the configured audit specifications. Administrators can use these records to investigate suspicious activity, review access patterns, and support compliance requirements. Audit configuration should be designed according to the organization’s security and regulatory needs. Capturing too many unnecessary events can increase storage and management requirements, so administrators should focus on events that provide meaningful security information.<\/span><\/p>\n

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

                                Which SQL Server feature helps prevent a single workload from consuming excessive CPU or memory resources on a shared instance?<\/b><\/p>\n

                                  \n
                                1. Resource Governor<\/span><\/li>\n
                                2. Query Store<\/span><\/li>\n
                                3. Extended Events<\/span><\/li>\n
                                4. SQL Server Audit<\/span><\/li>\n<\/ol>\n

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

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

                                  Resource Governor allows administrators to control resource usage for classified workloads. Administrators can create workload groups and resource pools with limits or priorities for CPU and memory. This can help protect important workloads when multiple applications share the same SQL Server instance. Resource Governor is not primarily a query optimization feature; it is a resource management feature. Administrators should monitor the results after configuration to ensure that limits do not negatively affect required workloads.<\/span><\/p>\n

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

                                  Which SQL Server feature can help identify queries that consume excessive CPU over time?<\/b><\/p>\n

                                    \n
                                  1. Query Store<\/span><\/li>\n
                                  2. Database Mail<\/span><\/li>\n
                                  3. Model database<\/span><\/li>\n
                                  4. Database snapshots<\/span><\/li>\n<\/ol>\n

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

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

                                    Query Store records query execution information over time, including runtime statistics that can help administrators identify CPU-intensive queries. Administrators can sort and analyze query performance to find workloads that consume significant resources. This historical information is useful when performance problems are intermittent or started after a change. Once an expensive query is identified, administrators can inspect its execution plan, indexes, statistics, and query design to determine the appropriate optimization strategy.<\/span><\/p>\n

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

                                    Which tool is most appropriate for capturing a detailed event when a deadlock occurs?<\/b><\/p>\n

                                      \n
                                    1. Extended Events<\/span><\/li>\n
                                    2. Azure Cost Management<\/span><\/li>\n
                                    3. Azure Advisor<\/span><\/li>\n
                                    4. BACPAC<\/span><\/li>\n<\/ol>\n

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

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

                                      Extended Events can capture deadlock events and provide information about the sessions, resources, and statements involved. This information helps administrators determine why transactions are competing for resources and which transaction SQL Server selected as the deadlock victim. Administrators can then investigate indexing, transaction order, isolation levels, and application behavior. Capturing deadlock events is generally preferable to trying to diagnose a deadlock only from a user’s error message.<\/span><\/p>\n

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

                                      Which SQL Server feature can store multiple historical versions of rows for temporal querying?<\/b><\/p>\n

                                        \n
                                      1. System-versioned temporal tables<\/span><\/li>\n
                                      2. Database snapshots<\/span><\/li>\n
                                      3. Query Store<\/span><\/li>\n
                                      4. SQL Server Audit<\/span><\/li>\n<\/ol>\n

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

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

                                        System-versioned temporal tables automatically maintain historical row versions in a history table. This allows administrators and applications to query data as it existed during previous periods. Temporal tables are useful for auditing data changes, investigating historical states, and supporting business requirements that need data history. They are not a substitute for database backups because they do not provide complete database recovery. Administrators should manage the history data appropriately as it can grow over time.<\/span><\/p>\n

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

                                        Which SQL Server feature allows administrators to compare current data with historical row versions using temporal queries?<\/b><\/p>\n

                                          \n
                                        1. System-versioned temporal tables<\/span><\/li>\n
                                        2. Dynamic Data Masking<\/span><\/li>\n
                                        3. Database Mail<\/span><\/li>\n
                                        4. Resource Governor<\/span><\/li>\n<\/ol>\n

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

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

                                          System-versioned temporal tables maintain current and historical versions of rows with associated system-time information. Administrators can use temporal queries to examine how data looked at a previous point in time. This is useful for investigating changes, auditing business records, and understanding historical states. The history table is maintained automatically by SQL Server while system versioning is enabled. Administrators should monitor history-table growth and establish appropriate retention or cleanup strategies where supported.<\/span><\/p>\n

                                           <\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full\u00a0Microsoft DP-800 Exam Dumps\u00a0and Practice Test Dumps.   Question 321 Which T-SQL statement removes a previously granted or denied permission from a database principal? DROP REVOKE GRANT ALTER Correct Answer: 2 Explanation The REVOKE statement removes a previously granted or denied permission from a database principal. It is commonly used when access should no […]<\/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\/11847"}],"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=11847"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11847\/revisions"}],"predecessor-version":[{"id":11848,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/11847\/revisions\/11848"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=11847"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=11847"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=11847"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}