100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 480
A database deployer must be unable to read private production data. A test instead finds: Deployment identity can export customer records. Which underlying issue best explains this finding?
- Transparent data encryption was not enabled or backed correctly
- The migration role was granted unnecessary data-reader rights
- AI tooling reused an elevated operational account
- DELETE permission was granted directly or via inherited role
Explanation
Correct Answer
B:The migration role was granted unnecessary data-reader rights. It accounts for the specific observed failure: deployment identity can export customer records. The intended solution is separate schema-deployment permission from data select rights with the required setup.
Incorrect Answers
A:Transparent data encryption was not enabled or backed correctly. This is relevant when a stolen database file is readable offline. Here, the migration role was granted unnecessary data-reader rights.
C:AI tooling reused an elevated operational account. This concerns tool executes delete on a business table. Here, the migration role was granted unnecessary data-reader rights.
D:DELETE permission was granted directly or via inherited role. This concerns editor can remove entire rows. Here, the migration role was granted unnecessary data-reader rights.
Question 481
A project needs secure key rotation for Always Encrypted. 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
- Use Always Encrypted for client-side column encryption
- Rotate column master key and update encrypted key metadata properly
Explanation
Correct Answer
D:Rotate column master key and update encrypted key metadata properly. The implementation is use supported key rotation workflow with key vault and drivers; success can be checked by verify clients decrypt data after key rotation. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Store the secret in Azure Key Vault with workload identity. This concerns retrieving a database secret without checking it into git. Here, rotate column master key and update encrypted key metadata properly.
B:Create a dedicated database role for AI-assisted exploration. This concerns segregated permissions for ai tooling. Here, rotate column master key and update encrypted key metadata properly.
C:Use Always Encrypted for client-side column encryption. This concerns a hospital protects payment numbers even from database administrators. Here, rotate column master key and update encrypted key metadata properly.
Question 482
A project needs secure key rotation for Always Encrypted. The team selects: Rotate column master key and update encrypted key metadata properly. Which implementation action puts this design into practice?
- Configure authenticated role mappings and field restrictions
- Manage symmetric keys, certificates and ENCRYPTBYKEY in approved code
- Use supported key rotation workflow with Key Vault and drivers
- Configure database TDE with supported protector and key management
Explanation
Correct Answer
C:Use supported key rotation workflow with Key Vault and drivers. This is the concrete setup for rotate column master key and update encrypted key metadata properly, and verify clients decrypt data after key rotation supplies a direct confirmation.
Incorrect Answers
A:Configure authenticated role mappings and field restrictions. This concerns secure graphql field access for different roles. Instead, use supported key rotation workflow with Key Vault and drivers.
B:Manage symmetric keys, certificates and ENCRYPTBYKEY in approved code. This concerns developers need to encrypt one application field using SQL keys. Instead, use supported key rotation workflow with Key Vault and drivers.
D:Configure database TDE with supported protector and key management. This concerns encryption of database files and backups at rest. Instead, use supported key rotation workflow with Key Vault and drivers.
Question 483
A project needs secure key rotation for Always Encrypted. After implementing the design, which check most directly validates the expected behavior?
- Attempt direct export via privileged user without decrypt key
- Open key and decrypt only as authorized principal
- Verify clients decrypt data after key rotation
- Read secret from approved runtime while repo contains no plaintext
Explanation
Correct Answer
C:Verify clients decrypt data after key rotation. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that keys were rotated without re-encrypting or updating dependent keys.
Incorrect Answers
A:Attempt direct export via privileged user without decrypt key. This concerns distinguishing encrypted values from masked display values. Instead, verify clients decrypt data after key rotation.
B:Open key and decrypt only as authorized principal. This concerns developers need to encrypt one application field using SQL keys. Instead, verify clients decrypt data after key rotation.
D:Read secret from approved runtime while repo contains no plaintext. This concerns retrieving a database secret without checking it into git. Instead, verify clients decrypt data after key rotation.
Question 484
A project needs secure key rotation for Always Encrypted. A test instead finds: Old encryption metadata breaks all clients. Which underlying issue best explains this finding?
- Keys were rotated without re-encrypting or updating dependent keys
- Role permissions were configured only at UI tier
- Identity-based authentication was not configured end to end
- Required symmetric key was not opened in that session
Explanation
Correct Answer
A:Keys were rotated without re-encrypting or updating dependent keys. It accounts for the specific observed failure: old encryption metadata breaks all clients. The intended solution is rotate column master key and update encrypted key metadata properly with the required setup.
Incorrect Answers
B:Role permissions were configured only at UI tier. This concerns a low-privilege token selects a private graphql field. Here, keys were rotated without re-encrypting or updating dependent keys.
C:Identity-based authentication was not configured end to end. This concerns connection falls back to embedded SQL credentials. Here, keys were rotated without re-encrypting or updating dependent keys.
D:Required symmetric key was not opened in that session. This concerns decryptbykey returns null unexpectedly. Here, keys were rotated without re-encrypting or updating dependent keys.
Question 485
An application uses a SQL credential in a deployment pipeline. Which TWO listed actions form the most appropriate database design and its concrete implementation? (Choose TWO.)
- Reference protected secret variables at runtime only
- Use SQL column-level encryption functions where appropriate
- Grant SELECT on the reporting schema and restrict others
- Store the pipeline credential as Base64 text in the source repository
- Store credentials in pipeline secret management
Explanation
Correct Answers
A:This is the concrete configuration of the specified design: reference protected secret variables at runtime only. The choice makes the implementation testable in the given workload.
E:Store credentials in pipeline secret management. The implementation is reference protected secret variables at runtime only; success can be checked by review logs and artifacts for accidental secret disclosure. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Use SQL column-level encryption functions where appropriate. This concerns developers need to encrypt one application field using SQL keys. Here, reference protected secret variables at runtime only.
C:Grant SELECT on the reporting schema and restrict others. This concerns reading only a specific schema. Here, reference protected secret variables at runtime only.
D:Base64 encoding is reversible, not secret storage; committing credentials in repository files exposes them to anyone with source access.
Question 486
An application uses a SQL credential in a deployment pipeline. The team selects: Store credentials in pipeline secret management. 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
- Create inline TVF predicate and SECURITY POLICY
- Reference protected secret variables at runtime only
Explanation
Correct Answer
D:Reference protected secret variables at runtime only. This is the concrete setup for store credentials in pipeline secret management, and review logs and artifacts for accidental secret disclosure supplies a direct confirmation.
Incorrect Answers
A:Create Entra principal and assign managed identity to workload. This concerns authenticating without storing a SQL password. Here, reference protected secret variables at runtime only.
B:Grant managed identity a limited vault data-plane role. This concerns retrieving a database secret without checking it into git. Here, reference protected secret variables at runtime only.
C:Create inline TVF predicate and SECURITY POLICY. This concerns show each tenant only its own rows. Here, reference protected secret variables at runtime only.
Question 487
An application uses a SQL credential in a deployment pipeline. After implementing the design, which check most directly validates the expected behavior?
- Query as admin without keys and confirm ciphertext stays opaque
- Review logs and artifacts for accidental secret disclosure
- Read secret from approved runtime while repo contains no plaintext
- Acquire token and connect while no SQL password is stored
Explanation
Correct Answer
B:Review logs and artifacts for accidental secret disclosure. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that the pipeline echoes or expands unmasked secret values.
Incorrect Answers
A:Query as admin without keys and confirm ciphertext stays opaque. This concerns a hospital protects payment numbers even from database administrators. Instead, review logs and artifacts for accidental secret disclosure.
C:Read secret from approved runtime while repo contains no plaintext. This concerns retrieving a database secret without checking it into git. Instead, review logs and artifacts for accidental secret disclosure.
D:Acquire token and connect while no SQL password is stored. This concerns authenticating without storing a SQL password. Instead, review logs and artifacts for accidental secret disclosure.
Question 488
An application uses a SQL credential in a deployment pipeline. A test instead finds: Build log prints connection password. Which underlying issue best explains this finding?
- Masking was mistaken for cryptographic confidentiality
- Secret was embedded rather than fetched securely
- The pipeline echoes or expands unmasked secret values
- The application built SQL by concatenating user input
Explanation
Correct Answer
C:The pipeline echoes or expands unmasked secret values. It accounts for the specific observed failure: build log prints connection password. The intended solution is store credentials in pipeline secret management with the required setup.
Incorrect Answers
A:Masking was mistaken for cryptographic confidentiality. This concerns privileged users retrieve underlying unmasked secret. Here, the pipeline echoes or expands unmasked secret values.
B:Secret was embedded rather than fetched securely. This concerns secret appears in deployment scripts. Here, the pipeline echoes or expands unmasked secret values.
D:The application built SQL by concatenating user input. This concerns input with a quote executes appended SQL. Here, the pipeline echoes or expands unmasked secret values.
Question 489
A security team requires segregated permissions for AI tooling. Which database design or engineering approach most directly meets this requirement?
- Use managed identity and scoped endpoint permissions
- Create a dedicated database role for AI-assisted exploration
- Use encryption for secrecy instead of relying on Dynamic Data Masking
- Audit effective permissions and role memberships
Explanation
Correct Answer
B:Create a dedicated database role for AI-assisted exploration. The implementation is grant view definition or select only where approved; success can be checked by run ai tool as its role and test blocked operations. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use managed identity and scoped endpoint permissions. This is relevant when a production ai model endpoint is called from SQL. Instead, create a dedicated database role for AI-assisted exploration.
C:Use encryption for secrecy instead of relying on Dynamic Data Masking. This concerns distinguishing encrypted values from masked display values. Instead, create a dedicated database role for AI-assisted exploration.
D:Audit effective permissions and role memberships. This concerns preventing accidental broad grants from roles. Instead, create a dedicated database role for AI-assisted exploration.
Question 490
A security team requires segregated permissions for AI tooling. The team selects: Create a dedicated database role for AI-assisted exploration. Which implementation action puts this design into practice?
- Assign workload identity to endpoint access role
- GRANT VIEW DEFINITION or SELECT only where approved
- Apply appropriate protected-column encryption to sensitive data
- Use GRANT UPDATE and explicit minimum SELECT permissions
Explanation
Correct Answer
B:GRANT VIEW DEFINITION or SELECT only where approved. This is the concrete setup for create a dedicated database role for ai-assisted exploration, and run ai tool as its role and test blocked operations supplies a direct confirmation.
Incorrect Answers
A:Assign workload identity to endpoint access role. This is relevant when a production ai model endpoint is called from SQL. The relevant SQL or system operation is GRANT VIEW DEFINITION or SELECT only where approved.
C:Apply appropriate protected-column encryption to sensitive data. This concerns distinguishing encrypted values from masked display values. The relevant SQL or system operation is GRANT VIEW DEFINITION or SELECT only where approved.
D:Use GRANT UPDATE and explicit minimum SELECT permissions. This concerns updating but not delete orders. The relevant SQL or system operation is GRANT VIEW DEFINITION or SELECT only where approved.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests