100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 460
A vendor integration must access one stored procedure. A test instead finds: Vendor account can browse the full schema. Which underlying issue best explains this finding?
- Principal inherits broad db_datareader or equivalent access
- Over-broad role membership was used instead of object grant
- AI tooling reused an elevated operational account
- Permission arrives from a different role or ownership chain
Explanation
Correct Answer
B:Over-broad role membership was used instead of object grant. It accounts for the specific observed failure: vendor account can browse the full schema. The intended solution is grant execute on the procedure, not broad table access with the required setup.
Incorrect Answers
A:Principal inherits broad db_datareader or equivalent access. This concerns analyst reads payroll tables outside approved schema. Here, over-broad role membership was used instead of object grant.
C:AI tooling reused an elevated operational account. This concerns tool executes delete on a business table. Here, over-broad role membership was used instead of object grant.
D:Permission arrives from a different role or ownership chain. This concerns unexpected access persists after revoking direct grant. Here, over-broad role membership was used instead of object grant.
Question 461
A tenant admin wants to prevent accidental broad grants from roles. Which TWO listed actions form the most appropriate database design and its concrete implementation? (Choose TWO.)
- Apply DAB entity and role permissions to GraphQL
- Use Row-Level Security with session-based tenant predicate
- Audit effective permissions and role memberships
- Grant UPDATE but not DELETE to a scoped role
- Use fn_my_permissions or supported catalog views under principal
Explanation
Correct Answers
C:Audit effective permissions and role memberships. The implementation is use fn_my_permissions or supported catalog views under principal; success can be checked by test effective access on representative securables. The method addresses the stated data and workload constraint.
E:This is the concrete configuration of the specified design: use fn_my_permissions or supported catalog views under principal. The choice makes the implementation testable in the given workload.
Incorrect Answers
A:Apply DAB entity and role permissions to GraphQL. This concerns secure graphql field access for different roles. Instead, audit effective permissions and role memberships.
B:Use Row-Level Security with session-based tenant predicate. This concerns show each tenant only its own rows. Instead, audit effective permissions and role memberships.
D:Grant UPDATE but not DELETE to a scoped role. This concerns updating but not delete orders. Instead, audit effective permissions and role memberships.
Question 462
A tenant admin wants to prevent accidental broad grants from roles. The team selects: Audit effective permissions and role memberships. Which implementation action puts this design into practice?
- Create inline TVF predicate and SECURITY POLICY
- Use supported key rotation workflow with Key Vault and drivers
- GRANT VIEW DEFINITION or SELECT only where approved
- Use fn_my_permissions or supported catalog views under principal
Explanation
Correct Answer
D:Use fn_my_permissions or supported catalog views under principal. This is the concrete setup for audit effective permissions and role memberships, and test effective access on representative securables supplies a direct confirmation.
Incorrect Answers
A:Create inline TVF predicate and SECURITY POLICY. This concerns show each tenant only its own rows. Instead, use fn_my_permissions or supported catalog views under principal.
B:Use supported key rotation workflow with Key Vault and drivers. This concerns secure key rotation for always encrypted. Instead, use fn_my_permissions or supported catalog views under principal.
C:GRANT VIEW DEFINITION or SELECT only where approved. This concerns segregated permissions for ai tooling. Instead, use fn_my_permissions or supported catalog views under principal.
Question 463
A tenant admin wants to prevent accidental broad grants from roles. After implementing the design, which check most directly validates the expected behavior?
- Execute a test ALTER and confirm audit record arrival
- Query with two tenant identities and compare visibility
- Test effective access on representative securables
- Resolve database hostname to approved private IP and connect
Explanation
Correct Answer
C:Test effective access on representative securables. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that permission arrives from a different role or ownership chain.
Incorrect Answers
A:Execute a test ALTER and confirm audit record arrival. This concerns security officers need a durable record of database schema changes. Instead, test effective access on representative securables.
B:Query with two tenant identities and compare visibility. This concerns show each tenant only its own rows. Instead, test effective access on representative securables.
D:Resolve database hostname to approved private IP and connect. This concerns internal-only database access from azure workloads. Instead, test effective access on representative securables.
Question 464
A tenant admin wants to prevent accidental broad grants from roles. A test instead finds: Unexpected access persists after revoking direct grant. Which underlying issue best explains this finding?
- Permission arrives from a different role or ownership chain
- Wrong audit actions were selected
- Role permissions were configured only at UI tier
- Over-broad role membership was used instead of object grant
Explanation
Correct Answer
A:Permission arrives from a different role or ownership chain. It accounts for the specific observed failure: unexpected access persists after revoking direct grant. The intended solution is audit effective permissions and role memberships with the required setup.
Incorrect Answers
B:Wrong audit actions were selected. This concerns auditing only records schema modifications but not sensitive reads. Here, permission arrives from a different role or ownership chain.
C:Role permissions were configured only at UI tier. This concerns a low-privilege token selects a private graphql field. Here, permission arrives from a different role or ownership chain.
D:Over-broad role membership was used instead of object grant. This concerns vendor account can browse the full schema. Here, permission arrives from a different role or ownership chain.
Question 465
A user needs to protect sensitive data from SQL injection. Which database design or engineering approach most directly meets this requirement?
- Use Dynamic Data Masking to reduce casual exposure
- Separate schema-deployment permission from data SELECT rights
- Parameterize statements and restrict SQL principal rights
- Use SQL data classification metadata
Explanation
Correct Answer
C:Parameterize statements and restrict SQL principal rights. The implementation is bind typed sql parameters instead of string concatenation; success can be checked by test injection-like strings and inspect query behavior. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use Dynamic Data Masking to reduce casual exposure. This concerns obscure salaries on standard queries. Here, parameterize statements and restrict SQL principal rights.
B:Separate schema-deployment permission from data SELECT rights. This concerns being unable to read private production data. Here, parameterize statements and restrict SQL principal rights.
D:Use SQL data classification metadata. This concerns searchable sensitivity tags on columns. Here, parameterize statements and restrict SQL principal rights.
Question 466
A user needs to protect sensitive data from SQL injection. The team selects: Parameterize statements and restrict SQL principal rights. Which implementation action puts this design into practice?
- Use fn_my_permissions or supported catalog views under principal
- Apply appropriate protected-column encryption to sensitive data
- Bind typed SQL parameters instead of string concatenation
- Bind MCP server to least-privilege SQL identity and secure transport
Explanation
Correct Answer
C:Bind typed SQL parameters instead of string concatenation. This is the concrete setup for parameterize statements and restrict sql principal rights, and test injection-like strings and inspect query behavior supplies a direct confirmation.
Incorrect Answers
A:Use fn_my_permissions or supported catalog views under principal. This concerns preventing accidental broad grants from roles. Here, bind typed SQL parameters instead of string concatenation.
B:Apply appropriate protected-column encryption to sensitive data. This concerns distinguishing encrypted values from masked display values. Here, bind typed SQL parameters instead of string concatenation.
D:Bind MCP server to least-privilege SQL identity and secure transport. This concerns a team exposes SQL metadata through an mcp endpoint. Here, bind typed SQL parameters instead of string concatenation.
Question 467
A user needs to protect sensitive data from SQL injection. After implementing the design, which check most directly validates the expected behavior?
- Test UPDATE permitted and DELETE denied under role
- Test injection-like strings and inspect query behavior
- Test schema deployment and reject raw sensitive data query
- Inspect classified metadata and reporting output
Explanation
Correct Answer
B:Test injection-like strings and inspect query behavior. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that the application built sql by concatenating user input.
Incorrect Answers
A:Test UPDATE permitted and DELETE denied under role. This concerns updating but not delete orders. Instead, test injection-like strings and inspect query behavior.
C:Test schema deployment and reject raw sensitive data query. This concerns being unable to read private production data. Instead, test injection-like strings and inspect query behavior.
D:Inspect classified metadata and reporting output. This concerns searchable sensitivity tags on columns. Instead, test injection-like strings and inspect query behavior.
Question 468
A user needs to protect sensitive data from SQL injection. A test instead finds: Input with a quote executes appended SQL. Which underlying issue best explains this finding?
- Identity-based authentication was not configured end to end
- The application built SQL by concatenating user input
- Trust validation was disabled or server certificate was not verified
- Principal inherits broad db_datareader or equivalent access
Explanation
Correct Answer
B:The application built SQL by concatenating user input. It accounts for the specific observed failure: input with a quote executes appended sql. The intended solution is parameterize statements and restrict sql principal rights with the required setup.
Incorrect Answers
A:Identity-based authentication was not configured end to end. This concerns connection falls back to embedded SQL credentials. Here, the application built SQL by concatenating user input.
C:Trust validation was disabled or server certificate was not verified. This concerns clients accept a man-in-the-middle certificate silently. Here, the application built SQL by concatenating user input.
D:Principal inherits broad db_datareader or equivalent access. This concerns analyst reads payroll tables outside approved schema. Here, the application built SQL by concatenating user input.
Question 469
A compliance team needs searchable sensitivity tags on columns. Which database design or engineering approach most directly meets this requirement?
- Use SQL data classification metadata
- Require scoped authentication and permissioned tools
- Use Always Encrypted with secure enclaves where supported
- Use Row-Level Security with session-based tenant predicate
Explanation
Correct Answer
A:Use SQL data classification metadata. The implementation is apply sensitivity labels/information types to sensitive columns; success can be checked by inspect classified metadata and reporting output. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Require scoped authentication and permissioned tools. This concerns a team exposes SQL metadata through an mcp endpoint. Instead, use SQL data classification metadata.
C:Use Always Encrypted with secure enclaves where supported. This concerns executing server-side calculations over protected columns. Instead, use SQL data classification metadata.
D:Use Row-Level Security with session-based tenant predicate. This concerns show each tenant only its own rows. Instead, use SQL data classification metadata.
Question 470
A compliance team needs searchable sensitivity tags on columns. The team selects: Use SQL data classification metadata. Which implementation action puts this design into practice?
- Apply sensitivity labels/information types to sensitive columns
- Configure enclave attestation and enclave-enabled encryption keys
- Use GRANT UPDATE and explicit minimum SELECT permissions
- Apply appropriate protected-column encryption to sensitive data
Explanation
Correct Answer
A:Apply sensitivity labels/information types to sensitive columns. This is the concrete setup for use sql data classification metadata, and inspect classified metadata and reporting output supplies a direct confirmation.
Incorrect Answers
B:Configure enclave attestation and enclave-enabled encryption keys. This concerns executing server-side calculations over protected columns. Instead, apply sensitivity labels/information types to sensitive columns.
C:Use GRANT UPDATE and explicit minimum SELECT permissions. This concerns updating but not delete orders. Instead, apply sensitivity labels/information types to sensitive columns.
D:Apply appropriate protected-column encryption to sensitive data. This concerns distinguishing encrypted values from masked display values. Instead, apply sensitivity labels/information types to sensitive columns.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests