Microsoft DP-800 Practice Test 33
Question 320
A database engineer at Briarfield Foods is investigating this case: A multi-tenant SaaS database stores several customers in one table. The relevant finding is: Application bugs could read rows belonging to another tenant. Which operational check supplies an **early preventive warning** that tenant-filter policies have changed or cross-tenant negative tests are failing, before a real user observes leaked rows?
- Monitor policy changes and cross-tenant access tests
- Monitor plan regressions and security tests
- Monitor key access and driver encryption errors
- Monitor cross-tenant query anomalies
Explanation
Correct Answer
A:
Application bugs could read rows belonging to another tenant. Monitor policy changes and cross-tenant access tests.
Incorrect Answers
B:
“Monitor plan regressions and security tests” concerns Security predicates join an unindexed tenant mapping table; the reported problem instead is Application bugs could read rows belonging to another tenant. Monitor policy changes and cross-tenant access tests.
C:
“Monitor key access and driver encryption errors” concerns Server-side encryption alone leaves plaintext exposed to DB engine; the reported problem instead is Application bugs could read rows belonging to another tenant. Monitor policy changes and cross-tenant access tests.
D:
Unusual cross-tenant queries can help detect an active exposure, but may be observed only after an unauthorized query has already occurred. The stated early preventive criterion requires checking RLS policy changes and continuous negative access tests rather than only reactive anomalies.
Question 321
Northstar Analytics is responsible for an Azure SQL or Microsoft SQL workload. A reporting service account is a db_owner. Operational evidence: Unnecessary DDL rights create serious modification risk. What initial check best narrows the technical cause without altering business data?
- Inspect schemas, effective privileges and undesired objects
- Inspect key hierarchy and permitted decrypting roles
- Review effective database roles and required queries
- Review threat model and ability to run queries or export data
Explanation
Correct Answer
C:
Unnecessary DDL rights create serious modification risk. Review effective database roles and required queries.
Incorrect Answers
A:
“Inspect schemas, effective privileges and undesired objects” concerns Repeated per-object GRANT updates are error-prone; the reported problem instead is Unnecessary DDL rights create serious modification risk. Review effective database roles and required queries.
B:
“Inspect key hierarchy and permitted decrypting roles” concerns Data requires encryption at rest but query-time access is limited; the reported problem instead is Unnecessary DDL rights create serious modification risk. Review effective database roles and required queries.
D:
“Review threat model and ability to run queries or export data” concerns Masking is not a substitute for authorization and can be inferred; the reported problem instead is Unnecessary DDL rights create serious modification risk. Review effective database roles and required queries.
Question 322
At Maple Harbor Research, a reporting service account is a db_owner. The observed constraint is: Unnecessary DDL rights create serious modification risk. Which proposed change is the most suitable response to the observed constraint?
- Grant SELECT on approved views and remove broad owner membership
- Revoke exposed credential, rotate it and remove secret from source history/process
- Restrict MCP tools to metadata-only and remove broad write authority
- Grant appropriate schema-scope SELECT only after catalog review
Explanation
Correct Answer
A:
Unnecessary DDL rights create serious modification risk. Grant SELECT on approved views and remove broad owner membership.
Incorrect Answers
B:
“Revoke exposed credential, rotate it and remove secret from source history/process” concerns Secrets may have been indexed and copied; the reported problem instead is Unnecessary DDL rights create serious modification risk. Grant SELECT on approved views and remove broad owner membership.
C:
“Restrict MCP tools to metadata-only and remove broad write authority” concerns An AI agent only needs metadata yet can invoke DELETE; the reported problem instead is Unnecessary DDL rights create serious modification risk. Grant SELECT on approved views and remove broad owner membership.
D:
“Grant appropriate schema-scope SELECT only after catalog review” concerns Repeated per-object GRANT updates are error-prone; the reported problem instead is Unnecessary DDL rights create serious modification risk. Grant SELECT on approved views and remove broad owner membership.
Question 323
A database engineer at Juniper Commerce is investigating this case: A reporting service account is a db_owner. The relevant finding is: Unnecessary DDL rights create serious modification risk. What isolated pilot would provide the strongest evidence before rollout?
- Try authorized GET and unauthorized mutation using test tokens
- Try allowed view SELECT and prohibited table DROP as test principal
- Try harmless metadata read and blocked test DELETE
- Add a synthetic view and test effective permissions
Explanation
Correct Answer
B:
Unnecessary DDL rights create serious modification risk. Try allowed view SELECT and prohibited table DROP as test principal.
Incorrect Answers
A:
“Try authorized GET and unauthorized mutation using test tokens” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Unnecessary DDL rights create serious modification risk. Try allowed view SELECT and prohibited table DROP as test principal.
C:
“Try harmless metadata read and blocked test DELETE” concerns An AI agent only needs metadata yet can invoke DELETE; the reported problem instead is Unnecessary DDL rights create serious modification risk. Try allowed view SELECT and prohibited table DROP as test principal.
D:
“Add a synthetic view and test effective permissions” concerns Repeated per-object GRANT updates are error-prone; the reported problem instead is Unnecessary DDL rights create serious modification risk. Try allowed view SELECT and prohibited table DROP as test principal.
Question 324
Summit Logistics is responsible for an Azure SQL or Microsoft SQL workload. A reporting service account is a db_owner. Operational evidence: Unnecessary DDL rights create serious modification risk. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Only intended read methods succeed; writes are rejected
- Event is preserved and modifications are prevented or detectable
- Only documented read operations succeed
- Restricted principals cannot retrieve sensitive raw values through alternate paths
Explanation
Correct Answer
C:
Unnecessary DDL rights create serious modification risk. Only documented read operations succeed.
Incorrect Answers
A:
“Only intended read methods succeed; writes are rejected” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Unnecessary DDL rights create serious modification risk. Only documented read operations succeed.
B:
“Event is preserved and modifications are prevented or detectable” concerns Admins could alter evidence after a security incident; the reported problem instead is Unnecessary DDL rights create serious modification risk. Only documented read operations succeed.
D:
“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 Unnecessary DDL rights create serious modification risk. Only documented read operations succeed.
Question 325
At BrightPath Studios, a reporting service account is a db_owner. The observed constraint is: Unnecessary DDL rights create serious modification risk. What operational condition would provide the earliest useful regression warning?
- Monitor API denied requests and role drift
- Monitor grants and privileged role membership
- Monitor token failures and assigned role drift
- Monitor unexpected UNMASK grants and data export paths
Explanation
Correct Answer
B:
Unnecessary DDL rights create serious modification risk. Monitor grants and privileged role membership.
Incorrect Answers
A:
“Monitor API denied requests and role drift” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Unnecessary DDL rights create serious modification risk. Monitor grants and privileged role membership.
C:
“Monitor token failures and assigned role drift” concerns Password rotation breaks the app and exposes credentials; the reported problem instead is Unnecessary DDL rights create serious modification risk. Monitor grants and privileged role membership.
D:
“Monitor unexpected UNMASK grants and data export paths” concerns Regular SELECT reveals sensitive contact details; the reported problem instead is Unnecessary DDL rights create serious modification risk. Monitor grants and privileged role membership.
Question 326
A database engineer at Lakeview Services is investigating this case: An Azure Function connects to Azure SQL using a stored password. The relevant finding is: Password rotation breaks the app and exposes credentials. What initial check best narrows the technical cause without altering business data?
- Inspect identity support and SQL principal mapping
- Inspect DAB runtime role mapping, entity actions and authentication
- Inspect existing column masking rules and principal rights
- Inspect DAB role filters and SQL identity context
Explanation
Correct Answer
A:
Password rotation breaks the app and exposes credentials. Inspect identity support and SQL principal mapping.
Incorrect Answers
B:
“Inspect DAB runtime role mapping, entity actions and authentication” concerns Default or overly broad role mappings permit unintended writes; the reported problem instead is Password rotation breaks the app and exposes credentials. Inspect identity support and SQL principal mapping.
C:
“Inspect existing column masking rules and principal rights” concerns Regular SELECT reveals sensitive contact details; the reported problem instead is Password rotation breaks the app and exposes credentials. Inspect identity support and SQL principal mapping.
D:
“Inspect DAB role filters and SQL identity context” concerns Resolver inherits broad SQL user permissions; the reported problem instead is Password rotation breaks the app and exposes credentials. Inspect identity support and SQL principal mapping.
Question 327
Crownridge Travel 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. Which proposed change is the most suitable response to the observed constraint?
- Back up protected keys/certificates separately with controlled access
- Classify sensitive columns and enforce access according to data policy
- Use managed identity with Microsoft Entra authentication for SQL access
- Use managed identity or scoped credential and approved endpoint authorization
Explanation
Correct Answer
C:
Password rotation breaks the app and exposes credentials. Use managed identity with Microsoft Entra authentication for SQL access.
Incorrect Answers
A:
“Back up protected keys/certificates separately with controlled access” concerns Missing encryption certificate blocks restoration; the reported problem instead is Password rotation breaks the app and exposes credentials. Use managed identity with Microsoft Entra authentication for SQL access.
B:
“Classify sensitive columns and enforce access according to data policy” concerns Teams cannot apply proper controls without data inventory; the reported problem instead is Password rotation breaks the app and exposes credentials. Use managed identity with Microsoft Entra authentication for SQL access.
D:
“Use managed identity or scoped credential and approved endpoint authorization” concerns Static API keys in scripts are exposed in source control; the reported problem instead is Password rotation breaks the app and exposes credentials. Use managed identity with Microsoft Entra authentication for SQL access.
Question 328
At Oakridge Advisors, an Azure Function connects to Azure SQL using a stored password. The observed constraint is: Password rotation breaks the app and exposes credentials. What isolated pilot would provide the strongest evidence before rollout?
- Restore encrypted database in DR sandbox using approved key procedure
- Call a disposable database from the Function test identity
- Invoke fake model endpoint under minimally privileged test identity
- Run controlled inference probes against masked fields in a test database
Explanation
Correct Answer
B:
Password rotation breaks the app and exposes credentials. Call a disposable database from the Function test identity.
Incorrect Answers
A:
“Restore encrypted database in DR sandbox using approved key procedure” concerns Missing encryption certificate blocks restoration; the reported problem instead is Password rotation breaks the app and exposes credentials. Call a disposable database from the Function test identity.
C:
“Invoke fake model endpoint under minimally privileged test identity” concerns Static API keys in scripts are exposed in source control; the reported problem instead is Password rotation breaks the app and exposes credentials. Call a disposable database from the Function test identity.
D:
“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 Password rotation breaks the app and exposes credentials. Call a disposable database from the Function test identity.
Question 329
A database engineer at Horizon Communications is investigating this case: An Azure Function connects to Azure SQL using a stored password. The relevant finding is: Password rotation breaks the app and exposes credentials. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Encrypted data can be recovered by authorized process only
- Authorized client decrypts while untrusted SQL session sees ciphertext
- Old credential fails and new credential works only for scoped permissions
- Authorized query works without stored SQL passwords
Explanation
Correct Answer
D:
Password rotation breaks the app and exposes credentials. Authorized query works without stored SQL passwords.
Incorrect Answers
A:
“Encrypted data can be recovered by authorized process only” concerns Storage backup compromise could expose plaintext pages; the reported problem instead is Password rotation breaks the app and exposes credentials. Authorized query works without stored SQL passwords.
B:
“Authorized client decrypts while untrusted SQL session sees ciphertext” concerns Server-side encryption alone leaves plaintext exposed to DB engine; the reported problem instead is Password rotation breaks the app and exposes credentials. Authorized query works without stored SQL passwords.
C:
“Old credential fails and new credential works only for scoped permissions” concerns Secrets may have been indexed and copied; the reported problem instead is Password rotation breaks the app and exposes credentials. Authorized query works without stored SQL passwords.
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.