Microsoft DP-800 Practice Test 57
Question 560
A database engineer at Seabrook University is investigating this case: An API entity includes confidential salary column. The relevant finding is: Role mapping permits clients to select every column. What operational condition would provide the earliest useful regression warning?
- Monitor privilege changes and blocked query attempts
- Monitor trigger lag and duplicate processing
- Monitor procedure errors and API write attempts
- Monitor GraphQL query cost and relationship failures
Explanation
Correct Answer
A:
Role mapping permits clients to select every column. Monitor privilege changes and blocked query attempts.
Incorrect Answers
B:
“Monitor trigger lag and duplicate processing” concerns Polling entire table every minute is wasteful; the reported problem instead is Role mapping permits clients to select every column. Monitor privilege changes and blocked query attempts.
C:
“Monitor procedure errors and API write attempts” concerns Direct table insert bypasses business constraints; the reported problem instead is Role mapping permits clients to select every column. Monitor privilege changes and blocked query attempts.
D:
“Monitor GraphQL query cost and relationship failures” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Role mapping permits clients to select every column. Monitor privilege changes and blocked query attempts.
Question 561
Atlas Publishing is responsible for an Azure SQL or Microsoft SQL workload. An API must invoke validated order creation logic. Operational evidence: Direct table insert bypasses business constraints. What initial check best narrows the technical cause without altering business data?
- Inspect DAB relationships and entity naming
- Inspect entity fields and DAB role action permissions
- Inspect stored procedure contract and supported DAB action mapping
- Inspect authentication provider and role mapping
Explanation
Correct Answer
C:
Direct table insert bypasses business constraints. Inspect stored procedure contract and supported DAB action mapping.
Incorrect Answers
A:
“Inspect DAB relationships and entity naming” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Direct table insert bypasses business constraints. Inspect stored procedure contract and supported DAB action mapping.
B:
“Inspect entity fields and DAB role action permissions” concerns Role mapping permits clients to select every column; the reported problem instead is Direct table insert bypasses business constraints. Inspect stored procedure contract and supported DAB action mapping.
D:
“Inspect authentication provider and role mapping” concerns Anonymous API access bypasses identity checks; the reported problem instead is Direct table insert bypasses business constraints. Inspect stored procedure contract and supported DAB action mapping.
Question 562
At Mountainview Realty, an API must invoke validated order creation logic. The observed constraint is: Direct table insert bypasses business constraints. Which proposed change is the most suitable response to the observed constraint?
- Expose controlled stored procedure endpoint instead of unrestricted table writes
- Configure supported JWT authentication and scoped API roles
- Expose only approved fields and restrict role privileges
- Configure supported Azure Functions SQL trigger binding with least privilege
Explanation
Correct Answer
A:
Direct table insert bypasses business constraints. Expose controlled stored procedure endpoint instead of unrestricted table writes.
Incorrect Answers
B:
“Configure supported JWT authentication and scoped API roles” concerns Anonymous API access bypasses identity checks; the reported problem instead is Direct table insert bypasses business constraints. Expose controlled stored procedure endpoint instead of unrestricted table writes.
C:
“Expose only approved fields and restrict role privileges” concerns Role mapping permits clients to select every column; the reported problem instead is Direct table insert bypasses business constraints. Expose controlled stored procedure endpoint instead of unrestricted table writes.
D:
“Configure supported Azure Functions SQL trigger binding with least privilege” concerns Polling entire table every minute is wasteful; the reported problem instead is Direct table insert bypasses business constraints. Expose controlled stored procedure endpoint instead of unrestricted table writes.
Question 563
A database engineer at Willow Creek Finance is investigating this case: An API must invoke validated order creation logic. The relevant finding is: Direct table insert bypasses business constraints. What isolated pilot would provide the strongest evidence before rollout?
- Update a synthetic tracked row and observe function invocation
- Call procedure through REST in a sandbox with valid and invalid payloads
- Update sample status and follow test approval workflow
- Try valid, expired and missing tokens against mock endpoint
Explanation
Correct Answer
B:
Direct table insert bypasses business constraints. Call procedure through REST in a sandbox with valid and invalid payloads.
Incorrect Answers
A:
“Update a synthetic tracked row and observe function invocation” concerns Polling entire table every minute is wasteful; the reported problem instead is Direct table insert bypasses business constraints. Call procedure through REST in a sandbox with valid and invalid payloads.
C:
“Update sample status and follow test approval workflow” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is Direct table insert bypasses business constraints. Call procedure through REST in a sandbox with valid and invalid payloads.
D:
“Try valid, expired and missing tokens against mock endpoint” concerns Anonymous API access bypasses identity checks; the reported problem instead is Direct table insert bypasses business constraints. Call procedure through REST in a sandbox with valid and invalid payloads.
Question 564
Granite Ridge Technology is responsible for an Azure SQL or Microsoft SQL workload. An API must invoke validated order creation logic. Operational evidence: Direct table insert bypasses business constraints. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Only valid authorized tokens can read allowed entities
- One intended event is processed with idempotency controls
- Expected REST entity is accessible only under authorized rules
- Business rules enforced and unauthorized clients denied
Explanation
Correct Answer
D:
Direct table insert bypasses business constraints. Business rules enforced and unauthorized clients denied.
Incorrect Answers
A:
“Only valid authorized tokens can read allowed entities” concerns Anonymous API access bypasses identity checks; the reported problem instead is Direct table insert bypasses business constraints. Business rules enforced and unauthorized clients denied.
B:
“One intended event is processed with idempotency controls” concerns Polling entire table every minute is wasteful; the reported problem instead is Direct table insert bypasses business constraints. Business rules enforced and unauthorized clients denied.
C:
“Expected REST entity is accessible only under authorized rules” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Direct table insert bypasses business constraints. Business rules enforced and unauthorized clients denied.
Question 565
At Pinecrest Operations, an API must invoke validated order creation logic. The observed constraint is: Direct table insert bypasses business constraints. What operational condition would provide the earliest useful regression warning?
- Monitor missing correlation and sampling errors
- Monitor procedure errors and API write attempts
- Monitor large page requests and API latency
- Monitor privilege changes and blocked query attempts
Explanation
Correct Answer
B:
Direct table insert bypasses business constraints. Monitor procedure errors and API write attempts.
Incorrect Answers
A:
“Monitor missing correlation and sampling errors” concerns HTTP response latency is available but SQL dependency duration is missing; the reported problem instead is Direct table insert bypasses business constraints. Monitor procedure errors and API write attempts.
C:
“Monitor large page requests and API latency” concerns Unbounded pages risk resource exhaustion; the reported problem instead is Direct table insert bypasses business constraints. Monitor procedure errors and API write attempts.
D:
“Monitor privilege changes and blocked query attempts” concerns Role mapping permits clients to select every column; the reported problem instead is Direct table insert bypasses business constraints. Monitor procedure errors and API write attempts.
Question 566
A database engineer at Marigold Banking is investigating this case: A B2B app exposes SQL data to signed-in users. The relevant finding is: Anonymous API access bypasses identity checks. What initial check best narrows the technical cause without altering business data?
- Inspect authentication provider and role mapping
- Examine entity fields and DAB role action permissions
- Inspect DAB relationships and entity naming
- Inspect stored procedure contract and supported DAB action mapping
Explanation
Correct Answer
A:
Anonymous API access bypasses identity checks. Inspect authentication provider and role mapping.
Incorrect Answers
B:
“Examine entity fields and DAB role action permissions” addresses the dab field-level permissions situation—role mapping permits clients to select every column. The observed failure is: Anonymous API access bypasses identity checks. Inspect authentication provider and role mapping.
C:
“Inspect DAB relationships and entity naming” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Anonymous API access bypasses identity checks. Inspect authentication provider and role mapping.
D:
“Inspect stored procedure contract and supported DAB action mapping” concerns Direct table insert bypasses business constraints; the reported problem instead is Anonymous API access bypasses identity checks. Inspect authentication provider and role mapping.
Question 567
Riverbend Retail is responsible for an Azure SQL or Microsoft SQL workload. A B2B app exposes SQL data to signed-in users. Operational evidence: Anonymous API access bypasses identity checks. Which proposed change is the most suitable response to the observed constraint?
- Configure supported JWT authentication and scoped API roles
- Configure supported Azure Functions SQL trigger binding with least privilege
- Configure supported one-to-many GraphQL relationship between entities
- Enable supported CDC with scoped capture instances
Explanation
Correct Answer
A:
Anonymous API access bypasses identity checks. Configure supported JWT authentication and scoped API roles.
Incorrect Answers
B:
“Configure supported Azure Functions SQL trigger binding with least privilege” concerns Polling entire table every minute is wasteful; the reported problem instead is Anonymous API access bypasses identity checks. Configure supported JWT authentication and scoped API roles.
C:
“Configure supported one-to-many GraphQL relationship between entities” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Anonymous API access bypasses identity checks. Configure supported JWT authentication and scoped API roles.
D:
“Enable supported CDC with scoped capture instances” concerns Nightly full refresh misses interim state; the reported problem instead is Anonymous API access bypasses identity checks. Configure supported JWT authentication and scoped API roles.
Question 568
At Prairie Logistics, a B2B app exposes SQL data to signed-in users. The observed constraint is: Anonymous API access bypasses identity checks. What isolated pilot would provide the strongest evidence before rollout?
- Update sample status and follow test approval workflow
- Call procedure through REST in a sandbox with valid and invalid payloads
- Run mock API request invoking deliberate slow SQL
- Try valid, expired and missing tokens against mock endpoint
Explanation
Correct Answer
D:
Anonymous API access bypasses identity checks. Try valid, expired and missing tokens against mock endpoint.
Incorrect Answers
A:
“Update sample status and follow test approval workflow” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is Anonymous API access bypasses identity checks. Try valid, expired and missing tokens against mock endpoint.
B:
“Call procedure through REST in a sandbox with valid and invalid payloads” concerns Direct table insert bypasses business constraints; the reported problem instead is Anonymous API access bypasses identity checks. Try valid, expired and missing tokens against mock endpoint.
C:
“Run mock API request invoking deliberate slow SQL” concerns HTTP response latency is available but SQL dependency duration is missing; the reported problem instead is Anonymous API access bypasses identity checks. Try valid, expired and missing tokens against mock endpoint.
Question 569
A database engineer at Silverpine Labs is investigating this case: A B2B app exposes SQL data to signed-in users. The relevant finding is: Anonymous API access bypasses identity checks. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Only valid authorized tokens can read allowed entities
- The consumer cannot retrieve salary while authorized endpoint still works
- Expected REST entity is accessible only under authorized rules
- Business rules enforced and unauthorized clients denied
Explanation
Correct Answer
A:
Anonymous API access bypasses identity checks. Only valid authorized tokens can read allowed entities.
Incorrect Answers
B:
“The consumer cannot retrieve salary while authorized endpoint still works” addresses the dab field-level permissions situation—role mapping permits clients to select every column. The observed failure is: Anonymous API access bypasses identity checks. Only valid authorized tokens can read allowed entities.
C:
“Expected REST entity is accessible only under authorized rules” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Anonymous API access bypasses identity checks. Only valid authorized tokens can read allowed entities.
D:
“Business rules enforced and unauthorized clients denied” concerns Direct table insert bypasses business constraints; the reported problem instead is Anonymous API access bypasses identity checks. Only valid authorized tokens can read allowed entities.
Question 570
Briarfield Foods is responsible for an Azure SQL or Microsoft SQL workload. A B2B app exposes SQL data to signed-in users. Operational evidence: Anonymous API access bypasses identity checks. What operational condition would provide the earliest useful regression warning?
- Monitor token validation failures and auth configuration
- Monitor GraphQL query cost and relationship failures
- Monitor procedure errors and API write attempts
- Monitor config validation and service startup errors
Explanation
Correct Answer
A:
Monitor bearer-token validation failures and changes to issuer, audience, signature-key, and expiry checks for the SQL-facing API. Approved users should obtain authorized results, while invalid or unauthenticated tokens fail closed; a successful HTTP response without identity validation would recreate the reported exposure.
Incorrect Answers
B:
“Monitor GraphQL query cost and relationship failures” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Anonymous API access bypasses identity checks. Monitor bearer-token validation failures and changes to issuer, audience, signature-key, and expiry checks for the SQL-facing API. Approved users should obtain authorized results, while invalid or unauthenticated tokens fail closed; a successful HTTP response without identity validation would recreate the reported exposure.
C:
“Monitor procedure errors and API write attempts” concerns Direct table insert bypasses business constraints; the reported problem instead is Anonymous API access bypasses identity checks. Monitor bearer-token validation failures and changes to issuer, audience, signature-key, and expiry checks for the SQL-facing API. Approved users should obtain authorized results, while invalid or unauthenticated tokens fail closed; a successful HTTP response without identity validation would recreate the reported exposure.
D:
“Monitor config validation and service startup errors” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Anonymous API access bypasses identity checks. Monitor bearer-token validation failures and changes to issuer, audience, signature-key, and expiry checks for the SQL-facing API. Approved users should obtain authorized results, while invalid or unauthenticated tokens fail closed; a successful HTTP response without identity validation would recreate the reported exposure.