100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 411
An application must authenticate without storing a SQL password. After implementing the design, which check most directly validates the expected behavior?
- Acquire token and connect while no SQL password is stored
- Test injection-like strings and inspect query behavior
- Check negotiated TLS and reject a forged certificate
- Review logs and artifacts for accidental secret disclosure
Explanation
Correct Answer
A:Acquire token and connect while no SQL password is stored. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that identity-based authentication was not configured end to end.
Incorrect Answers
B:Test injection-like strings and inspect query behavior. This concerns protecting sensitive data from SQL injection. Here, acquire token and connect while no SQL password is stored.
C:Check negotiated TLS and reject a forged certificate. This concerns protecting connections in transit. Here, acquire token and connect while no SQL password is stored.
D:Review logs and artifacts for accidental secret disclosure. This is relevant when an application uses a SQL credential in a deployment pipeline. Here, acquire token and connect while no SQL password is stored.
Question 412
An application must authenticate without storing a SQL password. A test instead finds: Connection falls back to embedded SQL credentials. Which underlying issue best explains this finding?
- The application built SQL by concatenating user input
- Endpoint authentication was not migrated to managed identity
- MCP server credential can access unapproved database objects
- Identity-based authentication was not configured end to end
Explanation
Correct Answer
D:Identity-based authentication was not configured end to end. It accounts for the specific observed failure: connection falls back to embedded sql credentials. The intended solution is use microsoft entra authentication with managed identity where supported with the required setup.
Incorrect Answers
A:The application built SQL by concatenating user input. This concerns input with a quote executes appended SQL. Here, identity-based authentication was not configured end to end.
B:Endpoint authentication was not migrated to managed identity. This concerns SQL service sends a hard-coded endpoint key in clear configuration. Here, identity-based authentication was not configured end to end.
C:MCP server credential can access unapproved database objects. This concerns agent lists protected schemas despite low privilege. Here, identity-based authentication was not configured end to end.
Question 413
An Azure Function already uses a managed identity and now needs least-privilege EXECUTE on a particular database procedure. Which TWO actions establish the database permission? (Choose TWO.)
- Use SQL data classification metadata
- Assign the Function an Azure resource Reader role but create no SQL database principal
- Enable Microsoft Entra authentication without granting the Function identity any database permissions
- Create database principal for function identity and GRANT EXECUTE
- Authorize its managed identity with least privileges
Explanation
Correct Answers
D:This is the concrete configuration of the specified design: create database principal for function identity and grant execute. The choice makes the implementation testable in the given workload.
E:Authorize its managed identity with least privileges. The implementation is create database principal for function identity and grant execute; success can be checked by confirm function executes only approved stored procedures. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use SQL data classification metadata. This concerns searchable sensitivity tags on columns. Instead, create database principal for function identity and GRANT EXECUTE.
B:Azure resource Reader alone does not create a database user or grant SQL EXECUTE rights on the stored procedure.
C:Entra authentication establishes identity but the database still requires a suitable principal and explicitly scoped EXECUTE rights.
Question 414
An Azure Function needs permission to call a database. The team selects: Authorize its managed identity with least privileges. Which implementation action puts this design into practice?
- Create minimal integration role and GRANT EXECUTE
- Define a MASKED WITH function and restrict UNMASK permission
- Create database principal for function identity and GRANT EXECUTE
- Configure DAB auth provider and action permissions
Explanation
Correct Answer
C:Create database principal for function identity and GRANT EXECUTE. This is the concrete setup for authorize its managed identity with least privileges, and confirm function executes only approved stored procedures supplies a direct confirmation.
Incorrect Answers
A:Create minimal integration role and GRANT EXECUTE. This concerns access one stored procedure. Instead, create database principal for function identity and GRANT EXECUTE.
B:Define a MASKED WITH function and restrict UNMASK permission. This concerns obscure salaries on standard queries. Instead, create database principal for function identity and GRANT EXECUTE.
D:Configure DAB auth provider and action permissions. This concerns an external service calls a database-backed rest API. Instead, create database principal for function identity and GRANT EXECUTE.
Question 415
An Azure Function needs permission to call a database. After implementing the design, which check most directly validates the expected behavior?
- Confirm function executes only approved stored procedures
- Resolve database hostname to approved private IP and connect
- Read secret from approved runtime while repo contains no plaintext
- Verify clients decrypt data after key rotation
Explanation
Correct Answer
A:Confirm function executes only approved stored procedures. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that database lacks mapped principal or appropriate grant.
Incorrect Answers
B:Resolve database hostname to approved private IP and connect. This concerns internal-only database access from azure workloads. Instead, confirm function executes only approved stored procedures.
C:Read secret from approved runtime while repo contains no plaintext. This concerns retrieving a database secret without checking it into git. Instead, confirm function executes only approved stored procedures.
D:Verify clients decrypt data after key rotation. This concerns secure key rotation for always encrypted. Instead, confirm function executes only approved stored procedures.
Question 416
An Azure Function needs permission to call a database. A test instead finds: Function cannot authenticate despite a valid Azure identity. Which underlying issue best explains this finding?
- DELETE permission was granted directly or via inherited role
- Audit logs lack protected independent retention
- Private DNS zone linkage or endpoint configuration is missing
- Database lacks mapped principal or appropriate grant
Explanation
Correct Answer
D:Database lacks mapped principal or appropriate grant. It accounts for the specific observed failure: function cannot authenticate despite a valid azure identity. The intended solution is authorize its managed identity with least privileges with the required setup.
Incorrect Answers
A:DELETE permission was granted directly or via inherited role. This concerns editor can remove entire rows. Here, database lacks mapped principal or appropriate grant.
B:Audit logs lack protected independent retention. This concerns an operator can erase all historical audit evidence. Here, database lacks mapped principal or appropriate grant.
C:Private DNS zone linkage or endpoint configuration is missing. This concerns private workload resolves a public endpoint unexpectedly. Here, database lacks mapped principal or appropriate grant.
Question 417
An application must retrieve a database secret without checking it into Git. Which database design or engineering approach most directly meets this requirement?
- Store the secret in Azure Key Vault with workload identity
- Create a dedicated database role for AI-assisted exploration
- Store credentials in pipeline secret management
- Rotate column master key and update encrypted key metadata properly
Explanation
Correct Answer
A:Store the secret in Azure Key Vault with workload identity. The implementation is grant managed identity a limited vault data-plane role; success can be checked by read secret from approved runtime while repo contains no plaintext. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Create a dedicated database role for AI-assisted exploration. This concerns segregated permissions for ai tooling. Instead, store the secret in Azure Key Vault with workload identity.
C:Store credentials in pipeline secret management. This is relevant when an application uses a SQL credential in a deployment pipeline. Instead, store the secret in Azure Key Vault with workload identity.
D:Rotate column master key and update encrypted key metadata properly. This concerns secure key rotation for always encrypted. Instead, store the secret in Azure Key Vault with workload identity.
Question 418
An application must retrieve a database secret without checking it into Git. The team selects: Store the secret in Azure Key Vault with workload identity. Which implementation action puts this design into practice?
- Create Entra principal and assign managed identity to workload
- Create database principal for function identity and GRANT EXECUTE
- Grant managed identity a limited vault data-plane role
- Bind MCP server to least-privilege SQL identity and secure transport
Explanation
Correct Answer
C:Grant managed identity a limited vault data-plane role. This is the concrete setup for store the secret in azure key vault with workload identity, and read secret from approved runtime while repo contains no plaintext supplies a direct confirmation.
Incorrect Answers
A:Create Entra principal and assign managed identity to workload. This concerns authenticating without storing a SQL password. Instead, grant managed identity a limited vault data-plane role.
B:Create database principal for function identity and GRANT EXECUTE. This concerns permission to call a database. Instead, grant managed identity a limited vault data-plane role.
D:Bind MCP server to least-privilege SQL identity and secure transport. This concerns a team exposes SQL metadata through an mcp endpoint. Instead, grant managed identity a limited vault data-plane role.
Question 419
An application must retrieve a database secret without checking it into Git. After implementing the design, which check most directly validates the expected behavior?
- Test injection-like strings and inspect query behavior
- Test an approved enclave computation without plaintext exposure
- Read secret from approved runtime while repo contains no plaintext
- Review logs and artifacts for accidental secret disclosure
Explanation
Correct Answer
C:Read secret from approved runtime while repo contains no plaintext. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that secret was embedded rather than fetched securely.
Incorrect Answers
A:Test injection-like strings and inspect query behavior. This concerns protecting sensitive data from SQL injection. Instead, read secret from approved runtime while repo contains no plaintext.
B:Test an approved enclave computation without plaintext exposure. This concerns executing server-side calculations over protected columns. Instead, read secret from approved runtime while repo contains no plaintext.
D:Review logs and artifacts for accidental secret disclosure. This is relevant when an application uses a SQL credential in a deployment pipeline. Instead, read secret from approved runtime while repo contains no plaintext.
Question 420
An application must retrieve a database secret without checking it into Git. A test instead finds: Secret appears in deployment scripts. Which underlying issue best explains this finding?
- Database lacks mapped principal or appropriate grant
- Role permissions were configured only at UI tier
- Secret was embedded rather than fetched securely
- The pipeline echoes or expands unmasked secret values
Explanation
Correct Answer
C:Secret was embedded rather than fetched securely. It accounts for the specific observed failure: secret appears in deployment scripts. The intended solution is store the secret in azure key vault with workload identity with the required setup.
Incorrect Answers
A:Database lacks mapped principal or appropriate grant. This concerns function cannot authenticate despite a valid azure identity. Here, secret was embedded rather than fetched securely.
B:Role permissions were configured only at UI tier. This concerns a low-privilege token selects a private graphql field. Here, secret was embedded rather than fetched securely.
D:The pipeline echoes or expands unmasked secret values. This concerns building log prints connection password. Here, secret was embedded rather than fetched securely.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests