Microsoft DP-800 Practice Test 34
Question 330
Brookfield Labs is responsible for an Azure SQL or Microsoft SQL workload. An Azure Function connects to Azure SQL using a stored password. Operational evidence: Password rotation breaks the app and exposes credentials. What operational condition would provide the earliest useful regression warning?
- Monitor grants and privileged role membership
- Monitor anomalous prior token activity
- Monitor API denied requests and role drift
- Monitor token failures and assigned role drift
Explanation
Correct Answer
D:
Password rotation breaks the app and exposes credentials. Monitor token failures and assigned role drift.
Incorrect Answers
A:
“Monitor grants and privileged role membership” concerns Unnecessary DDL rights create serious modification risk; the reported problem instead is Password rotation breaks the app and exposes credentials. Monitor token failures and assigned role drift.
B:
“Monitor anomalous prior token activity” concerns Secrets may have been indexed and copied; the reported problem instead is Password rotation breaks the app and exposes credentials. Monitor token failures and assigned role drift.
C:
“Monitor API denied requests and role drift” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Password rotation breaks the app and exposes credentials. Monitor token failures and assigned role drift.
Question 331
At Cascade Manufacturing, compliance needs records of who updated privileged role memberships. The observed constraint is: Existing logs cannot identify actor and changed object. What initial check best narrows the technical cause without altering business data?
- Review audit events and target retention requirements
- Inventory affected service principals and audit logs
- Inspect retention settings and writer permissions
- Review platform TDE state and key custody requirements
Explanation
Correct Answer
A:
Existing logs cannot identify actor and changed object. Review audit events and target retention requirements.
Incorrect Answers
B:
“Inventory affected service principals and audit logs” concerns Secrets may have been indexed and copied; the reported problem instead is Existing logs cannot identify actor and changed object. Review audit events and target retention requirements.
C:
“Inspect retention settings and writer permissions” concerns Admins could alter evidence after a security incident; the reported problem instead is Existing logs cannot identify actor and changed object. Review audit events and target retention requirements.
D:
“Review platform TDE state and key custody requirements” concerns Storage backup compromise could expose plaintext pages; the reported problem instead is Existing logs cannot identify actor and changed object. Review audit events and target retention requirements.
Question 332
A database engineer at Clearwater Utilities is investigating this case: Compliance needs records of who updated privileged role memberships. The relevant finding is: Existing logs cannot identify actor and changed object. Which proposed change is the most suitable response to the observed constraint?
- Map roles to minimum allowed actions and enforce SQL permissions
- Send audit events to approved immutable or tamper-resistant storage
- Enable supported transparent data encryption and govern key backups
- Enable appropriate SQL auditing for privileged actions and send to governed storage
Explanation
Correct Answer
D:
Existing logs cannot identify actor and changed object. Enable appropriate SQL auditing for privileged actions and send to governed storage.
Incorrect Answers
A:
“Map roles to minimum allowed actions and enforce SQL permissions” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Existing logs cannot identify actor and changed object. Enable appropriate SQL auditing for privileged actions and send to governed storage.
B:
“Send audit events to approved immutable or tamper-resistant storage” concerns Admins could alter evidence after a security incident; the reported problem instead is Existing logs cannot identify actor and changed object. Enable appropriate SQL auditing for privileged actions and send to governed storage.
C:
“Enable supported transparent data encryption and govern key backups” concerns Storage backup compromise could expose plaintext pages; the reported problem instead is Existing logs cannot identify actor and changed object. Enable appropriate SQL auditing for privileged actions and send to governed storage.
Question 333
Cedarbridge Health is responsible for an Azure SQL or Microsoft SQL workload. Compliance needs records of who updated privileged role memberships. Operational evidence: Existing logs cannot identify actor and changed object. What isolated pilot would provide the strongest evidence before rollout?
- Run controlled inference probes against masked fields in a test database
- Perform a simulated GRANT and inspect collected audit events
- Attempt authorized ingest and blocked rewrite of synthetic audit record
- Switch a sandbox service to a newly issued credential
Explanation
Correct Answer
B:
Existing logs cannot identify actor and changed object. Perform a simulated GRANT and inspect collected audit events.
Incorrect Answers
A:
“Run controlled inference probes against masked fields in a test database” concerns Masking is not a substitute for authorization and can be inferred; the reported problem instead is Existing logs cannot identify actor and changed object. Perform a simulated GRANT and inspect collected audit events.
C:
“Attempt authorized ingest and blocked rewrite of synthetic audit record” concerns Admins could alter evidence after a security incident; the reported problem instead is Existing logs cannot identify actor and changed object. Perform a simulated GRANT and inspect collected audit events.
D:
“Switch a sandbox service to a newly issued credential” concerns Secrets may have been indexed and copied; the reported problem instead is Existing logs cannot identify actor and changed object. Perform a simulated GRANT and inspect collected audit events.
Question 334
At Ashwood Solutions, compliance needs records of who updated privileged role memberships. The observed constraint is: Existing logs cannot identify actor and changed object. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Old credential fails and new credential works only for scoped permissions
- Restricted principals cannot retrieve sensitive raw values through alternate paths
- Actor, action and timestamp are present and protected from tampering
- Expected fields are labeled and permissions tested
Explanation
Correct Answer
C:
Existing logs cannot identify actor and changed object. Actor, action and timestamp are present and protected from tampering.
Incorrect Answers
A:
“Old credential fails and new credential works only for scoped permissions” concerns Secrets may have been indexed and copied; the reported problem instead is Existing logs cannot identify actor and changed object. Actor, action and timestamp are present and protected from tampering.
B:
“Restricted principals cannot retrieve sensitive raw values through alternate paths” concerns Masking is not a substitute for authorization and can be inferred; the reported problem instead is Existing logs cannot identify actor and changed object. Actor, action and timestamp are present and protected from tampering.
D:
“Expected fields are labeled and permissions tested” concerns Teams cannot apply proper controls without data inventory; the reported problem instead is Existing logs cannot identify actor and changed object. Actor, action and timestamp are present and protected from tampering.
Question 335
A database engineer at Seabrook University is investigating this case: Compliance needs records of who updated privileged role memberships. The relevant finding is: Existing logs cannot identify actor and changed object. Which monitoring condition directly checks that audit records for role membership changes continue to arrive at their destination with adequate retention?
- Monitor policy changes and cross-tenant access tests
- Monitor audit pipeline gaps and retention policy
- Monitor masking policy misunderstanding and overprivileged accounts
- Monitor only server CPU utilization and ordinary query response time
Explanation
Correct Answer
B:
Existing logs cannot identify actor and changed object. Monitor audit pipeline gaps and retention policy.
Incorrect Answers
A:
“Monitor policy changes and cross-tenant access tests” concerns Application bugs could read rows belonging to another tenant; the reported problem instead is Existing logs cannot identify actor and changed object. Monitor audit pipeline gaps and retention policy.
C:
“Monitor masking policy misunderstanding and overprivileged accounts” concerns Masking is not a substitute for authorization and can be inferred; the reported problem instead is Existing logs cannot identify actor and changed object. Monitor audit pipeline gaps and retention policy.
D:
CPU and query response time describe database performance and do not establish whether role-change audit records were emitted, ingested or retained. Audit pipeline and retention checks in B directly satisfy the evidentiary requirement.
Question 336
Atlas Publishing is responsible for an Azure SQL or Microsoft SQL workload. A newly enabled RLS security policy slows a reporting workload. Operational evidence: Security predicates join an unindexed tenant mapping table. What initial check best narrows the technical cause without altering business data?
- Inventory exposed tools and execution principals
- Inspect identity support and SQL principal mapping
- Inspect retention settings and writer permissions
- Inspect actual execution plan and predicate function execution
Explanation
Correct Answer
D:
Security predicates join an unindexed tenant mapping table. Inspect actual execution plan and predicate function execution.
Incorrect Answers
A:
“Inventory exposed tools and execution principals” concerns An AI agent only needs metadata yet can invoke DELETE; the reported problem instead is Security predicates join an unindexed tenant mapping table. Inspect actual execution plan and predicate function execution.
B:
“Inspect identity support and SQL principal mapping” concerns Password rotation breaks the app and exposes credentials; the reported problem instead is Security predicates join an unindexed tenant mapping table. Inspect actual execution plan and predicate function execution.
C:
“Inspect retention settings and writer permissions” concerns Admins could alter evidence after a security incident; the reported problem instead is Security predicates join an unindexed tenant mapping table. Inspect actual execution plan and predicate function execution.
Question 337
At Mountainview Realty, a newly enabled RLS security policy slows a reporting workload. The observed constraint is: Security predicates join an unindexed tenant mapping table. Which proposed change is the most suitable response to the observed constraint?
- Optimize RLS predicate lookup indexes without weakening filtering
- Combine least-privilege controls, RLS/encryption and masking only as defense in depth
- Use a Row-Level Security predicate and security policy for tenant boundaries
- Send audit events to approved immutable or tamper-resistant storage
Explanation
Correct Answer
A:
Security predicates join an unindexed tenant mapping table. Optimize RLS predicate lookup indexes without weakening filtering.
Incorrect Answers
B:
“Combine least-privilege controls, RLS/encryption and masking only as defense in depth” concerns Masking is not a substitute for authorization and can be inferred; the reported problem instead is Security predicates join an unindexed tenant mapping table. Optimize RLS predicate lookup indexes without weakening filtering.
C:
“Use a Row-Level Security predicate and security policy for tenant boundaries” concerns Application bugs could read rows belonging to another tenant; the reported problem instead is Security predicates join an unindexed tenant mapping table. Optimize RLS predicate lookup indexes without weakening filtering.
D:
“Send audit events to approved immutable or tamper-resistant storage” concerns Admins could alter evidence after a security incident; the reported problem instead is Security predicates join an unindexed tenant mapping table. Optimize RLS predicate lookup indexes without weakening filtering.
Question 338
A database engineer at Willow Creek Finance is investigating this case: A newly enabled RLS security policy slows a reporting workload. The relevant finding is: Security predicates join an unindexed tenant mapping table. What isolated pilot would provide the strongest evidence before rollout?
- Query the same test rows through separate tenant principals
- Try authorized GET and unauthorized mutation using test tokens
- Benchmark identical queries under an authorized test role
- Attempt authorized ingest and blocked rewrite of synthetic audit record
Explanation
Correct Answer
C:
Security predicates join an unindexed tenant mapping table. Benchmark identical queries under an authorized test role.
Incorrect Answers
A:
“Query the same test rows through separate tenant principals” concerns Application bugs could read rows belonging to another tenant; the reported problem instead is Security predicates join an unindexed tenant mapping table. Benchmark identical queries under an authorized test role.
B:
“Try authorized GET and unauthorized mutation using test tokens” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Security predicates join an unindexed tenant mapping table. Benchmark identical queries under an authorized test role.
D:
“Attempt authorized ingest and blocked rewrite of synthetic audit record” concerns Admins could alter evidence after a security incident; the reported problem instead is Security predicates join an unindexed tenant mapping table. Benchmark identical queries under an authorized test role.
Question 339
Granite Ridge Technology is responsible for an Azure SQL or Microsoft SQL workload. A newly enabled RLS security policy slows a reporting workload. Operational evidence: Security predicates join an unindexed tenant mapping table. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Each session sees only authorized tenant rows even on broad SELECT
- Event is preserved and modifications are prevented or detectable
- Correct tenant isolation persists with reduced query overhead
- Authorized query works without stored SQL passwords
Explanation
Correct Answer
C:
Security predicates join an unindexed tenant mapping table. Correct tenant isolation persists with reduced query overhead.
Incorrect Answers
A:
“Each session sees only authorized tenant rows even on broad SELECT” concerns Application bugs could read rows belonging to another tenant; the reported problem instead is Security predicates join an unindexed tenant mapping table. Correct tenant isolation persists with reduced query overhead.
B:
“Event is preserved and modifications are prevented or detectable” concerns Admins could alter evidence after a security incident; the reported problem instead is Security predicates join an unindexed tenant mapping table. Correct tenant isolation persists with reduced query overhead.
D:
“Authorized query works without stored SQL passwords” concerns Password rotation breaks the app and exposes credentials; the reported problem instead is Security predicates join an unindexed tenant mapping table. Correct tenant isolation persists with reduced query overhead.
Question 340
At Pinecrest Operations, a newly enabled RLS security policy slows a reporting workload. The observed constraint is: Security predicates join an unindexed tenant mapping table. What operational condition would provide the earliest useful regression warning?
- Monitor plan regressions and security tests
- Monitor retention policy and ingestion outages
- Monitor MCP invocation logs and unauthorized action attempts
- Monitor policy changes and cross-tenant access tests
Explanation
Correct Answer
A:
Security predicates join an unindexed tenant mapping table. Monitor plan regressions and security tests.
Incorrect Answers
B:
“Monitor retention policy and ingestion outages” concerns Admins could alter evidence after a security incident; the reported problem instead is Security predicates join an unindexed tenant mapping table. Monitor plan regressions and security tests.
C:
“Monitor MCP invocation logs and unauthorized action attempts” concerns An AI agent only needs metadata yet can invoke DELETE; the reported problem instead is Security predicates join an unindexed tenant mapping table. Monitor plan regressions and security tests.
D:
“Monitor policy changes and cross-tenant access tests” concerns Application bugs could read rows belonging to another tenant; the reported problem instead is Security predicates join an unindexed tenant mapping table. Monitor plan regressions and security tests.