100% Latest & Updated Microsoft DP-800 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
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.
Question 421
Security officers need a durable record of database schema changes. Which database design or engineering approach most directly meets this requirement?
- Capture SELECT access with supported SQL auditing
- Require authenticated Data API builder endpoint access
- Enable appropriate SQL auditing for schema events
- Grant SELECT on the reporting schema and restrict others
Explanation
Correct Answer
C:Enable appropriate SQL auditing for schema events. The implementation is configure audit destination and action groups; success can be checked by execute a test alter and confirm audit record arrival. 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, enable appropriate SQL auditing for schema events.
B:Require authenticated Data API builder endpoint access. This concerns an external service calls a database-backed rest API. Instead, enable appropriate SQL auditing for schema events.
D:Grant SELECT on the reporting schema and restrict others. This concerns reading only a specific schema. Instead, enable appropriate SQL auditing for schema events.
Question 422
Security officers need a durable record of database schema changes. The team selects: Enable appropriate SQL auditing for schema events. Which implementation action puts this design into practice?
- Configure audit destination and action groups
- Create minimal integration role and GRANT EXECUTE
- Send SQL audit output to protected storage with retention controls
- Configure audit policy for sensitive object action
Explanation
Correct Answer
A:Configure audit destination and action groups. This is the concrete setup for enable appropriate sql auditing for schema events, and execute a test alter and confirm audit record arrival supplies a direct confirmation.
Incorrect Answers
B:Create minimal integration role and GRANT EXECUTE. This concerns access one stored procedure. Instead, configure audit destination and action groups.
C:Send SQL audit output to protected storage with retention controls. This concerns trustworthy records of security changes. Instead, configure audit destination and action groups.
D:Configure audit policy for sensitive object action. This concerns recording which identity retrieved salary information. Instead, configure audit destination and action groups.
Question 423
Security officers need a durable record of database schema changes. After implementing the design, which check most directly validates the expected behavior?
- Query as masked and privileged principals
- Issue scoped query and verify principal and timestamp in logs
- Test audit events and storage deletion restrictions
- Execute a test ALTER and confirm audit record arrival
Explanation
Correct Answer
D:Execute a test ALTER and confirm audit record arrival. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that audit action or destination was not configured.
Incorrect Answers
A:Query as masked and privileged principals. This concerns obscure salaries on standard queries. Instead, execute a test ALTER and confirm audit record arrival.
B:Issue scoped query and verify principal and timestamp in logs. This concerns recording which identity retrieved salary information. Instead, execute a test ALTER and confirm audit record arrival.
C:Test audit events and storage deletion restrictions. This concerns trustworthy records of security changes. Instead, execute a test ALTER and confirm audit record arrival.
Question 424
Security officers need a durable record of database schema changes. A test instead finds: Change incident has no attributable database audit event. Which underlying issue best explains this finding?
- Wrong audit actions were selected
- Audit action or destination was not configured
- Audit logs lack protected independent retention
- Principal inherits broad db_datareader or equivalent access
Explanation
Correct Answer
B:Audit action or destination was not configured. It accounts for the specific observed failure: change incident has no attributable database audit event. The intended solution is enable appropriate sql auditing for schema events with the required setup.
Incorrect Answers
A:Wrong audit actions were selected. This concerns auditing only records schema modifications but not sensitive reads. Instead, audit action or destination was not configured.
C:Audit logs lack protected independent retention. This concerns an operator can erase all historical audit evidence. Instead, audit action or destination was not configured.
D:Principal inherits broad db_datareader or equivalent access. This concerns analyst reads payroll tables outside approved schema. Instead, audit action or destination was not configured.
Question 425
An external service calls a database-backed REST API. Which database design or engineering approach most directly meets this requirement?
- Use Always Encrypted with secure enclaves where supported
- Use a private endpoint and disable unwanted public access
- Enable transparent data encryption
- Require authenticated Data API builder endpoint access
Explanation
Correct Answer
D:Require authenticated Data API builder endpoint access. The implementation is configure dab auth provider and action permissions; success can be checked by test unauthorized calls receive access denial. The method addresses the stated data and workload constraint.
Incorrect Answers
A:Use Always Encrypted with secure enclaves where supported. This concerns executing server-side calculations over protected columns. Instead, require authenticated Data API builder endpoint access.
B:Use a private endpoint and disable unwanted public access. This concerns internal-only database access from azure workloads. Instead, require authenticated Data API builder endpoint access.
C:Enable transparent data encryption. This concerns encryption of database files and backups at rest. Instead, require authenticated Data API builder endpoint access.
Question 426
An external service calls a database-backed REST API. The team selects: Require authenticated Data API builder endpoint access. Which implementation action puts this design into practice?
- Configure audit destination and action groups
- Use GRANT UPDATE and explicit minimum SELECT permissions
- Configure database TDE with supported protector and key management
- Configure DAB auth provider and action permissions
Explanation
Correct Answer
D:Configure DAB auth provider and action permissions. This is the concrete setup for require authenticated data api builder endpoint access, and test unauthorized calls receive access denial supplies a direct confirmation.
Incorrect Answers
A:Configure audit destination and action groups. This concerns security officers need a durable record of database schema changes. Instead, configure DAB auth provider and action permissions.
B:Use GRANT UPDATE and explicit minimum SELECT permissions. This concerns updating but not delete orders. Instead, configure DAB auth provider and action permissions.
C:Configure database TDE with supported protector and key management. This concerns encryption of database files and backups at rest. Instead, configure DAB auth provider and action permissions.
Question 427
An external service calls a database-backed REST API. After implementing the design, which check most directly validates the expected behavior?
- Test unauthorized calls receive access denial
- Attempt unauthorized metadata discovery and confirm denial
- Resolve database hostname to approved private IP and connect
- Test schema deployment and reject raw sensitive data query
Explanation
Correct Answer
A:Test unauthorized calls receive access denial. This verifies the requirement in the case rather than merely confirming that a job ran; an opposing result can reveal that rest endpoint authorization defaults were too permissive.
Incorrect Answers
B:Attempt unauthorized metadata discovery and confirm denial. This concerns a team exposes SQL metadata through an mcp endpoint. Instead, test unauthorized calls receive access denial.
C:Resolve database hostname to approved private IP and connect. This concerns internal-only database access from azure workloads. Instead, test unauthorized calls receive access denial.
D:Test schema deployment and reject raw sensitive data query. This concerns being unable to read private production data. Instead, test unauthorized calls receive access denial.
Question 428
An external service calls a database-backed REST API. A test instead finds: Anonymous callers can query restricted entities. Which underlying issue best explains this finding?
- REST endpoint authorization defaults were too permissive
- DELETE permission was granted directly or via inherited role
- Transparent data encryption was not enabled or backed correctly
- Endpoint authentication was not migrated to managed identity
Explanation
Correct Answer
A:REST endpoint authorization defaults were too permissive. It accounts for the specific observed failure: anonymous callers can query restricted entities. The intended solution is require authenticated data api builder endpoint access with the required setup.
Incorrect Answers
B:DELETE permission was granted directly or via inherited role. This concerns editor can remove entire rows. The relevant SQL or system operation is REST endpoint authorization defaults were too permissive.
C:Transparent data encryption was not enabled or backed correctly. This is relevant when a stolen database file is readable offline. The relevant SQL or system operation is REST endpoint authorization defaults were too permissive.
D:Endpoint authentication was not migrated to managed identity. This concerns SQL service sends a hard-coded endpoint key in clear configuration. The relevant SQL or system operation is REST endpoint authorization defaults were too permissive.
Question 429
A developer needs secure GraphQL field access for different roles. Which database design or engineering approach most directly meets this requirement?
- Apply DAB entity and role permissions to GraphQL
- Rotate column master key and update encrypted key metadata properly
- Use managed identity and scoped endpoint permissions
- Audit effective permissions and role memberships
Explanation
Correct Answer
A:Apply DAB entity and role permissions to GraphQL. The implementation is configure authenticated role mappings and field restrictions; success can be checked by run role-specific queries for visible and hidden fields. The method addresses the stated data and workload constraint.
Incorrect Answers
B:Rotate column master key and update encrypted key metadata properly. This concerns secure key rotation for always encrypted. Instead, apply DAB entity and role permissions to GraphQL.
C:Use managed identity and scoped endpoint permissions. This is relevant when a production ai model endpoint is called from SQL. Instead, apply DAB entity and role permissions to GraphQL.
D:Audit effective permissions and role memberships. This concerns preventing accidental broad grants from roles. Instead, apply DAB entity and role permissions to GraphQL.
Question 430
A developer needs secure GraphQL field access for different roles. The team selects: Apply DAB entity and role permissions to GraphQL. Which implementation action puts this design into practice?
- Configure authenticated role mappings and field restrictions
- Configure private DNS and network access policies
- Create database principal for function identity and GRANT EXECUTE
- Use supported key rotation workflow with Key Vault and drivers
Explanation
Correct Answer
A:Configure authenticated role mappings and field restrictions. This is the concrete setup for apply dab entity and role permissions to graphql, and run role-specific queries for visible and hidden fields supplies a direct confirmation.
Incorrect Answers
B:Configure private DNS and network access policies. This concerns internal-only database access from azure workloads. Instead, configure authenticated role mappings and field restrictions.
C:Create database principal for function identity and GRANT EXECUTE. This concerns permission to call a database. Instead, configure authenticated role mappings and field restrictions.
D:Use supported key rotation workflow with Key Vault and drivers. This concerns secure key rotation for always encrypted. Instead, configure authenticated role mappings and field restrictions.
Developing AI-Enabled Database Solutions (DP-800) Practice Tests