100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 400
An analytics app must show each tenant only its own rows. A test instead finds: Tenant A can SELECT rows belonging to tenant B. Which underlying issue best explains this finding?
- RLS predicate is missing or session context is untrusted
- MCP server credential can access unapproved database objects
- Secure enclave support or attestation configuration is absent
- Required symmetric key was not opened in that session
Explanation
Correct Answer
A:RLS predicate is missing or session context is untrusted. It accounts for the specific observed failure: tenant a can select rows belonging to tenant b. The intended solution is use row-level security with session-based tenant predicate with the required setup.
Incorrect Answers
B:MCP server credential can access unapproved database objects. This concerns agent lists protected schemas despite low privilege. The relevant SQL or system operation is RLS predicate is missing or session context is untrusted.
C:Secure enclave support or attestation configuration is absent. This concerns protected comparison fails despite proper client drivers. The relevant SQL or system operation is RLS predicate is missing or session context is untrusted.
D:Required symmetric key was not opened in that session. This concerns decryptbykey returns null unexpectedly. The relevant SQL or system operation is RLS predicate is missing or session context is untrusted.
Question 401
A database editor should update but not delete orders. Which database design or engineering approach most directly meets this requirement?
- Use a private endpoint and disable unwanted public access
- Rotate column master key and update encrypted key metadata properly
- Grant UPDATE but not DELETE to a scoped role
- Create a dedicated database role for AI-assisted exploration
Explanation
Correct Answer
C:Grant UPDATE but not DELETE to a scoped role. The implementation is use grant update and explicit minimum select permissions; success can be checked by test update permitted and delete denied under role. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use a private endpoint and disable unwanted public access. This concerns internal-only database access from azure workloads. Instead, grant UPDATE but not DELETE to a scoped role.
B:Rotate column master key and update encrypted key metadata properly. This concerns secure key rotation for always encrypted. Instead, grant UPDATE but not DELETE to a scoped role.
D:Create a dedicated database role for AI-assisted exploration. This concerns segregated permissions for ai tooling. Instead, grant UPDATE but not DELETE to a scoped role.
Question 402
A database editor should update but not delete orders. The team selects: Grant UPDATE but not DELETE to a scoped role. Which implementation action puts this design into practice?
- Bind typed SQL parameters instead of string concatenation
- Use GRANT UPDATE and explicit minimum SELECT permissions
- GRANT VIEW DEFINITION or SELECT only where approved
- Create a report reader role with scoped GRANT SELECT
Explanation
Correct Answer
B:Use GRANT UPDATE and explicit minimum SELECT permissions. This is the concrete setup for grant update but not delete to a scoped role, and test update permitted and delete denied under role supplies a direct confirmation.
Incorrect Answers
A:Bind typed SQL parameters instead of string concatenation. This concerns protecting sensitive data from SQL injection. Instead, use GRANT UPDATE and explicit minimum SELECT permissions.
C:GRANT VIEW DEFINITION or SELECT only where approved. This concerns segregated permissions for ai tooling. Instead, use GRANT UPDATE and explicit minimum SELECT permissions.
D:Create a report reader role with scoped GRANT SELECT. This concerns reading only a specific schema. Instead, use GRANT UPDATE and explicit minimum SELECT permissions.
Question 403
A database editor should update but not delete orders. After implementing the design, which check most directly validates the expected behavior?
- Test UPDATE permitted and DELETE denied under role
- Run AI tool as its role and test blocked operations
- Resolve database hostname to approved private IP and connect
- Issue scoped query and verify principal and timestamp in logs
Explanation
Correct Answer
A:Test UPDATE permitted and DELETE denied under role. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that delete permission was granted directly or via inherited role.
Incorrect Answers
B:Run AI tool as its role and test blocked operations. This concerns segregated permissions for ai tooling. Instead, test UPDATE permitted and DELETE denied under role.
C:Resolve database hostname to approved private IP and connect. This concerns internal-only database access from azure workloads. Instead, test UPDATE permitted and DELETE denied under role.
D:Issue scoped query and verify principal and timestamp in logs. This concerns recording which identity retrieved salary information. Instead, test UPDATE permitted and DELETE denied under role.
Question 404
A database editor should update but not delete orders. A test instead finds: Editor can remove entire rows. Which underlying issue best explains this finding?
- DELETE permission was granted directly or via inherited role
- Trust validation was disabled or server certificate was not verified
- The migration role was granted unnecessary data-reader rights
- Database lacks mapped principal or appropriate grant
Explanation
Correct Answer
A:DELETE permission was granted directly or via inherited role. It accounts for the specific observed failure: editor can remove entire rows. The intended solution is grant update but not delete to a scoped role with the required setup.
Incorrect Answers
B:Trust validation was disabled or server certificate was not verified. This concerns clients accept a man-in-the-middle certificate silently. The relevant SQL or system operation is DELETE permission was granted directly or via inherited role.
C:The migration role was granted unnecessary data-reader rights. This concerns deployment identity can export customer records. The relevant SQL or system operation is DELETE permission was granted directly or via inherited role.
D:Database lacks mapped principal or appropriate grant. This concerns function cannot authenticate despite a valid azure identity. The relevant SQL or system operation is DELETE permission was granted directly or via inherited role.
Question 405
A reporting analyst should read only a specific schema. Which database design or engineering approach most directly meets this requirement?
- Enable appropriate SQL auditing for schema events
- Separate schema-deployment permission from data SELECT rights
- Authorize its managed identity with least privileges
- Grant SELECT on the reporting schema and restrict others
Explanation
Correct Answer
D:Grant SELECT on the reporting schema and restrict others. The implementation is create a report reader role with scoped grant select; success can be checked by run tests under analyst role against report and private objects. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Enable appropriate SQL auditing for schema events. This concerns security officers need a durable record of database schema changes. Instead, grant SELECT on the reporting schema and restrict others.
B:Separate schema-deployment permission from data SELECT rights. This concerns being unable to read private production data. Instead, grant SELECT on the reporting schema and restrict others.
C:Authorize its managed identity with least privileges. This concerns permission to call a database. Instead, grant SELECT on the reporting schema and restrict others.
Question 406
A reporting analyst should read only a specific schema. The team selects: Grant SELECT on the reporting schema and restrict others. Which implementation action puts this design into practice?
- Create minimal integration role and GRANT EXECUTE
- Create a report reader role with scoped GRANT SELECT
- Use dedicated migration identity with scoped DDL capabilities
- Define a MASKED WITH function and restrict UNMASK permission
Explanation
Correct Answer
B:Create a report reader role with scoped GRANT SELECT. This is the concrete setup for grant select on the reporting schema and restrict others, and run tests under analyst role against report and private objects supplies a direct confirmation.
Incorrect Answers
A:Create minimal integration role and GRANT EXECUTE. This concerns access one stored procedure. Instead, create a report reader role with scoped GRANT SELECT.
C:Use dedicated migration identity with scoped DDL capabilities. This concerns being unable to read private production data. Instead, create a report reader role with scoped GRANT SELECT.
D:Define a MASKED WITH function and restrict UNMASK permission. This concerns obscure salaries on standard queries. Instead, create a report reader role with scoped GRANT SELECT.
Question 407
A reporting analyst should read only a specific schema. After implementing the design, which check most directly validates the expected behavior?
- Run tests under analyst role against report and private objects
- Query as admin without keys and confirm ciphertext stays opaque
- Run role-specific queries for visible and hidden fields
- Test schema deployment and reject raw sensitive data query
Explanation
Correct Answer
A:Run tests under analyst role against report and private objects. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that principal inherits broad db_datareader or equivalent access.
Incorrect Answers
B:Query as admin without keys and confirm ciphertext stays opaque. This concerns a hospital protects payment numbers even from database administrators. Instead, run tests under analyst role against report and private objects.
C:Run role-specific queries for visible and hidden fields. This concerns secure graphql field access for different roles. Instead, run tests under analyst role against report and private objects.
D:Test schema deployment and reject raw sensitive data query. This concerns being unable to read private production data. Instead, run tests under analyst role against report and private objects.
Question 408
A reporting analyst should read only a specific schema. A test instead finds: Analyst reads payroll tables outside approved schema. Which underlying issue best explains this finding?
- Audit action or destination was not configured
- Principal inherits broad db_datareader or equivalent access
- Over-broad role membership was used instead of object grant
- Database lacks mapped principal or appropriate grant
Explanation
Correct Answer
B:Principal inherits broad db_datareader or equivalent access. It accounts for the specific observed failure: analyst reads payroll tables outside approved schema. The intended solution is grant select on the reporting schema and restrict others with the required setup.
Incorrect Answers
A:Audit action or destination was not configured. This concerns change incident has no attributable database audit event. Here, principal inherits broad db_datareader or equivalent access.
C:Over-broad role membership was used instead of object grant. This concerns vendor account can browse the full schema. Here, principal inherits broad db_datareader or equivalent access.
D:Database lacks mapped principal or appropriate grant. This concerns function cannot authenticate despite a valid azure identity. Here, principal inherits broad db_datareader or equivalent access.
Question 409
An application must authenticate without storing a SQL password. Which database design or engineering approach most directly meets this requirement?
- Capture SELECT access with supported SQL auditing
- Use managed identity and scoped endpoint permissions
- Use Microsoft Entra authentication with managed identity where supported
- Authorize its managed identity with least privileges
Explanation
Correct Answer
C:Use Microsoft Entra authentication with managed identity where supported. The implementation is create entra principal and assign managed identity to workload; success can be checked by acquire token and connect while no sql password is stored. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Capture SELECT access with supported SQL auditing. This concerns recording which identity retrieved salary information. Instead, use Microsoft Entra authentication with managed identity where supported.
B:Use managed identity and scoped endpoint permissions. This is relevant when a production ai model endpoint is called from SQL. Instead, use Microsoft Entra authentication with managed identity where supported.
D:Authorize its managed identity with least privileges. This concerns permission to call a database. Instead, use Microsoft Entra authentication with managed identity where supported.
Question 410
An application must authenticate without storing a SQL password. The team selects: Use Microsoft Entra authentication with managed identity where supported. Which implementation action puts this design into practice?
- Create Entra principal and assign managed identity to workload
- Grant managed identity a limited vault data-plane role
- Bind MCP server to least-privilege SQL identity and secure transport
- Assign workload identity to endpoint access role
Explanation
Correct Answer
A:Create Entra principal and assign managed identity to workload. This is the concrete setup for use microsoft entra authentication with managed identity where supported, and acquire token and connect while no sql password is stored supplies a direct confirmation.
Incorrect Answers
B:Grant managed identity a limited vault data-plane role. This concerns retrieving a database secret without checking it into git. Instead, create Entra principal and assign managed identity to workload.
C:Bind MCP server to least-privilege SQL identity and secure transport. This concerns a team exposes SQL metadata through an mcp endpoint. Instead, create Entra principal and assign managed identity to workload.
D:Assign workload identity to endpoint access role. This is relevant when a production ai model endpoint is called from SQL. Instead, create Entra principal and assign managed identity to workload.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests