Microsoft DP-800 Practice Test 56
Question 550
At BrightPath Studios, a shopping app queries orders and their items in one GraphQL request. The observed constraint is: GraphQL schema lacks relationship mapping despite SQL foreign key. What operational condition would provide the earliest useful regression warning?
- Monitor GraphQL query cost and relationship failures
- Monitor privilege changes and blocked query attempts
- Monitor missing correlation and sampling errors
- Monitor token validation failures and auth configuration
Explanation
Correct Answer
A:
GraphQL schema lacks relationship mapping despite SQL foreign key. Monitor GraphQL query cost and relationship failures.
Incorrect Answers
B:
“Monitor privilege changes and blocked query attempts” concerns Role mapping permits clients to select every column; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Monitor GraphQL query cost and relationship failures.
C:
“Monitor missing correlation and sampling errors” concerns HTTP response latency is available but SQL dependency duration is missing; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Monitor GraphQL query cost and relationship failures.
D:
“Monitor token validation failures and auth configuration” concerns Anonymous API access bypasses identity checks; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Monitor GraphQL query cost and relationship failures.
Question 551
A database engineer at Lakeview Services is investigating this case: A public API over a million products returns too many records per call. The relevant finding is: Unbounded pages risk resource exhaustion. What initial check best narrows the technical cause without altering business data?
- Examine entity fields and DAB role action permissions
- Inspect DAB entity pagination and max page size
- Inspect DAB relationships and entity naming
- Inspect DAB configuration schema, source type and connection auth
Explanation
Correct Answer
B:
Unbounded pages risk resource exhaustion. Inspect DAB entity pagination and max page size.
Incorrect Answers
A:
“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: Unbounded pages risk resource exhaustion. Inspect DAB entity pagination and max page size.
C:
“Inspect DAB relationships and entity naming” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Unbounded pages risk resource exhaustion. Inspect DAB entity pagination and max page size.
D:
“Inspect DAB configuration schema, source type and connection auth” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Unbounded pages risk resource exhaustion. Inspect DAB entity pagination and max page size.
Question 552
Crownridge Travel is responsible for an Azure SQL or Microsoft SQL workload. A public API over a million products returns too many records per call. Operational evidence: Unbounded pages risk resource exhaustion. Which proposed change is the most suitable response to the observed constraint?
- Use an approved SQL change feed connected to Logic Apps
- Use SQL Change Tracking with version tokens and consistent sync snapshots
- Configure supported Azure Functions SQL trigger binding with least privilege
- Set safe pagination defaults and enforce request limits
Explanation
Correct Answer
D:
Unbounded pages risk resource exhaustion. Set safe pagination defaults and enforce request limits.
Incorrect Answers
A:
“Use an approved SQL change feed connected to Logic Apps” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is Unbounded pages risk resource exhaustion. Set safe pagination defaults and enforce request limits.
B:
“Use SQL Change Tracking with version tokens and consistent sync snapshots” concerns Full row-history logging is unnecessary; the reported problem instead is Unbounded pages risk resource exhaustion. Set safe pagination defaults and enforce request limits.
C:
“Configure supported Azure Functions SQL trigger binding with least privilege” concerns Polling entire table every minute is wasteful; the reported problem instead is Unbounded pages risk resource exhaustion. Set safe pagination defaults and enforce request limits.
Question 553
At Oakridge Advisors, a public API over a million products returns too many records per call. The observed constraint is: Unbounded pages risk resource exhaustion. What isolated pilot would provide the strongest evidence before rollout?
- Request successive pages from a synthetic large dataset
- Run mock API request invoking deliberate slow SQL
- Update a synthetic tracked row and observe function invocation
- Modify a test catalog and request changes since known version
Explanation
Correct Answer
A:
Unbounded pages risk resource exhaustion. Request successive pages from a synthetic large dataset.
Incorrect Answers
B:
“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 Unbounded pages risk resource exhaustion. Request successive pages from a synthetic large dataset.
C:
“Update a synthetic tracked row and observe function invocation” concerns Polling entire table every minute is wasteful; the reported problem instead is Unbounded pages risk resource exhaustion. Request successive pages from a synthetic large dataset.
D:
“Modify a test catalog and request changes since known version” concerns Full row-history logging is unnecessary; the reported problem instead is Unbounded pages risk resource exhaustion. Request successive pages from a synthetic large dataset.
Question 554
A database engineer at Horizon Communications is investigating this case: A public API over a million products returns too many records per call. The relevant finding is: Unbounded pages risk resource exhaustion. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Workflow receives correct state without blocking OLTP transaction
- Pages are bounded and navigation returns no unintended duplicates
- Nested items match parent order with no unintended data
- One intended event is processed with idempotency controls
Explanation
Correct Answer
B:
Unbounded pages risk resource exhaustion. Pages are bounded and navigation returns no unintended duplicates.
Incorrect Answers
A:
“Workflow receives correct state without blocking OLTP transaction” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is Unbounded pages risk resource exhaustion. Pages are bounded and navigation returns no unintended duplicates.
C:
“Nested items match parent order with no unintended data” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Unbounded pages risk resource exhaustion. Pages are bounded and navigation returns no unintended duplicates.
D:
“One intended event is processed with idempotency controls” concerns Polling entire table every minute is wasteful; the reported problem instead is Unbounded pages risk resource exhaustion. Pages are bounded and navigation returns no unintended duplicates.
Question 555
Brookfield Labs is responsible for an Azure SQL or Microsoft SQL workload. A public API over a million products returns too many records per call. Operational evidence: Unbounded pages risk resource exhaustion. What operational condition would provide the earliest useful regression warning?
- Monitor large page requests and API latency
- Monitor trigger lag and duplicate processing
- Monitor latency, failed log ingestion and alert noise
- Monitor procedure errors and API write attempts
Explanation
Correct Answer
A:
Unbounded pages risk resource exhaustion. Monitor large page requests and API latency.
Incorrect Answers
B:
“Monitor trigger lag and duplicate processing” concerns Polling entire table every minute is wasteful; the reported problem instead is Unbounded pages risk resource exhaustion. Monitor large page requests and API latency.
C:
“Monitor latency, failed log ingestion and alert noise” concerns Application logs alone cannot distinguish database waits from network errors; the reported problem instead is Unbounded pages risk resource exhaustion. Monitor large page requests and API latency.
D:
“Monitor procedure errors and API write attempts” concerns Direct table insert bypasses business constraints; the reported problem instead is Unbounded pages risk resource exhaustion. Monitor large page requests and API latency.
Question 556
At Cascade Manufacturing, an API entity includes confidential salary column. The observed constraint is: Role mapping permits clients to select every column. What initial check best narrows the technical cause without altering business data?
- Inspect entity fields and DAB role action permissions
- Inspect DAB entity pagination and max page size
- Inspect DAB relationships and entity naming
- Inspect stored procedure contract and supported DAB action mapping
Explanation
Correct Answer
A:
Role mapping permits clients to select every column. Inspect entity fields and DAB role action permissions.
Incorrect Answers
B:
“Inspect DAB entity pagination and max page size” concerns Unbounded pages risk resource exhaustion; the reported problem instead is Role mapping permits clients to select every column. Inspect entity fields and DAB role action permissions.
C:
“Inspect DAB relationships and entity naming” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Role mapping permits clients to select every column. Inspect entity fields and DAB role action permissions.
D:
“Inspect stored procedure contract and supported DAB action mapping” concerns Direct table insert bypasses business constraints; the reported problem instead is Role mapping permits clients to select every column. Inspect entity fields and DAB role action permissions.
Question 557
A database engineer at Clearwater Utilities is investigating this case: An API entity includes confidential salary column. The relevant finding is: Role mapping permits clients to select every column. Which proposed change is the most suitable response to the observed constraint?
- Use an approved SQL change feed connected to Logic Apps
- Expose only approved fields and restrict role privileges
- Expose controlled stored procedure endpoint instead of unrestricted table writes
- Create Data API builder config with approved SQL source/entity mapping
Explanation
Correct Answer
B:
Role mapping permits clients to select every column. Expose only approved fields and restrict role privileges.
Incorrect Answers
A:
“Use an approved SQL change feed connected to Logic Apps” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is Role mapping permits clients to select every column. Expose only approved fields and restrict role privileges.
C:
“Expose controlled stored procedure endpoint instead of unrestricted table writes” concerns Direct table insert bypasses business constraints; the reported problem instead is Role mapping permits clients to select every column. Expose only approved fields and restrict role privileges.
D:
“Create Data API builder config with approved SQL source/entity mapping” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Role mapping permits clients to select every column. Expose only approved fields and restrict role privileges.
Question 558
Cedarbridge Health is responsible for an Azure SQL or Microsoft SQL workload. An API entity includes confidential salary column. Operational evidence: Role mapping permits clients to select every column. What isolated pilot would provide the strongest evidence before rollout?
- Generate synthetic slow query and inspect correlated telemetry
- Query synthetic order with multiple line items through GraphQL
- Start DAB in a test container against sample SQL
- Query with consumer and admin test roles
Explanation
Correct Answer
D:
Role mapping permits clients to select every column. Query with consumer and admin test roles.
Incorrect Answers
A:
“Generate synthetic slow query and inspect correlated telemetry” concerns Application logs alone cannot distinguish database waits from network errors; the reported problem instead is Role mapping permits clients to select every column. Query with consumer and admin test roles.
B:
“Query synthetic order with multiple line items through GraphQL” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is Role mapping permits clients to select every column. Query with consumer and admin test roles.
C:
“Start DAB in a test container against sample SQL” concerns No configuration maps entities to SQL objects or runtime connections; the reported problem instead is Role mapping permits clients to select every column. Query with consumer and admin test roles.
Question 559
At Ashwood Solutions, an API entity includes confidential salary column. The observed constraint is: Role mapping permits clients to select every column. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Only valid authorized tokens can read allowed entities
- Consumer cannot retrieve salary while authorized endpoint still works
- One intended event is processed with idempotency controls
- Expected REST entity is accessible only under authorized rules
Explanation
Correct Answer
B:
Role mapping permits clients to select every column. Consumer cannot retrieve salary while authorized endpoint still works.
Incorrect Answers
A:
“Only valid authorized tokens can read allowed entities” concerns Anonymous API access bypasses identity checks; the reported problem instead is Role mapping permits clients to select every column. Consumer cannot retrieve salary while authorized endpoint still works.
C:
“One intended event is processed with idempotency controls” concerns Polling entire table every minute is wasteful; the reported problem instead is Role mapping permits clients to select every column. Consumer cannot retrieve salary while authorized endpoint still works.
D:
“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 Role mapping permits clients to select every column. Consumer cannot retrieve salary while authorized endpoint still works.
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.