Microsoft DP-800 Practice Test 55
Question 540
Pinecrest Operations is responsible for an Azure SQL or Microsoft SQL workload. A DBA hotfixes production procedure during an outage. Operational evidence: Git schema is now older than deployed state. What operational condition would provide the earliest useful regression warning?
- Monitor repeat untracked emergency DDL
- Monitor deployment authorization and emergency bypass use
- Monitor unauthorized DDL outside pipeline
- Monitor deployment health and rollback triggers
Explanation
Correct Answer
A:
Git schema is now older than deployed state. Monitor repeat untracked emergency DDL.
Incorrect Answers
B:
“Monitor deployment authorization and emergency bypass use” concerns No manual signoff for a high-risk migration; the reported problem instead is Git schema is now older than deployed state. Monitor repeat untracked emergency DDL.
C:
“Monitor unauthorized DDL outside pipeline” concerns Future deployment would overwrite or conflict with unknown change; the reported problem instead is Git schema is now older than deployed state. Monitor repeat untracked emergency DDL.
D:
“Monitor deployment health and rollback triggers” concerns Schema build alone does not cover runtime permissions; the reported problem instead is Git schema is now older than deployed state. Monitor repeat untracked emergency DDL.
Question 541
At Marigold Banking, a team publishes SQL data over an internal REST API. The observed constraint is: No configuration maps entities to SQL objects or runtime connections. What initial check best narrows the technical cause without altering business data?
- Inspect DAB configuration schema, source type and connection auth
- Inspect DAB entity pagination and max page size
- Inspect entity fields and DAB role action permissions
- Inspect DAB relationships and entity naming
Explanation
Correct Answer
A:
No configuration maps entities to SQL objects or runtime connections. Inspect DAB configuration schema, source type and connection auth.
Incorrect Answers
B:
“Inspect DAB entity pagination and max page size” concerns Unbounded pages risk resource exhaustion; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Inspect DAB configuration schema, source type and connection auth.
C:
“Inspect entity fields and DAB role action permissions” concerns Role mapping permits clients to select every column; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Inspect DAB configuration schema, source type and connection auth.
D:
“Inspect DAB relationships and entity naming” concerns GraphQL schema lacks relationship mapping despite SQL foreign key; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Inspect DAB configuration schema, source type and connection auth.
Question 542
A database engineer at Riverbend Retail is investigating this case: A team publishes SQL data over an internal REST API. The relevant finding is: No configuration maps entities to SQL objects or runtime connections. Which proposed change is the most suitable response to the observed constraint?
- Route relevant SQL metrics/logs into approved Log Analytics workspace
- Use an approved SQL change feed connected to Logic Apps
- Configure supported JWT authentication and scoped API roles
- Create Data API builder config with approved SQL source/entity mapping
Explanation
Correct Answer
D:
No configuration maps entities to SQL objects or runtime connections. Create Data API builder config with approved SQL source/entity mapping.
Incorrect Answers
A:
“Route relevant SQL metrics/logs into approved Log Analytics workspace” concerns Application logs alone cannot distinguish database waits from network errors; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Create Data API builder config with approved SQL source/entity mapping.
B:
“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 No configuration maps entities to SQL objects or runtime connections. Create Data API builder config with approved SQL source/entity mapping.
C:
“Configure supported JWT authentication and scoped API roles” concerns Anonymous API access bypasses identity checks; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Create Data API builder config with approved SQL source/entity mapping.
Question 543
Prairie Logistics is responsible for an Azure SQL or Microsoft SQL workload. A team publishes SQL data over an internal REST API. Operational evidence: No configuration maps entities to SQL objects or runtime connections. What isolated pilot would provide the strongest evidence before rollout?
- Start DAB in a test container against sample SQL
- Run mock API request invoking deliberate slow SQL
- Update sample status and follow test approval workflow
- Query with consumer and admin test roles
Explanation
Correct Answer
A:
No configuration maps entities to SQL objects or runtime connections. Start DAB in a test container against sample SQL.
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 No configuration maps entities to SQL objects or runtime connections. Start DAB in a test container against sample SQL.
C:
“Update sample status and follow test approval workflow” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Start DAB in a test container against sample SQL.
D:
“Query with consumer and admin test roles” concerns Role mapping permits clients to select every column; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Start DAB in a test container against sample SQL.
Question 544
At Silverpine Labs, a team publishes SQL data over an internal REST API. The observed constraint is: No configuration maps entities to SQL objects or runtime connections. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Expected REST entity is accessible only under authorized rules
- Business rules enforced and unauthorized clients denied
- Consumer cannot retrieve salary while authorized endpoint still works
- Only valid authorized tokens can read allowed entities
Explanation
Correct Answer
A:
No configuration maps entities to SQL objects or runtime connections. Expected REST entity is accessible only under authorized rules.
Incorrect Answers
B:
“Business rules enforced and unauthorized clients denied” concerns Direct table insert bypasses business constraints; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Expected REST entity is accessible only under authorized rules.
C:
“Consumer cannot retrieve salary while authorized endpoint still works” concerns Role mapping permits clients to select every column; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Expected REST entity is accessible only under authorized rules.
D:
“Only valid authorized tokens can read allowed entities” concerns Anonymous API access bypasses identity checks; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Expected REST entity is accessible only under authorized rules.
Question 545
A database engineer at Briarfield Foods is investigating this case: A team publishes SQL data over an internal REST API. The relevant finding is: No configuration maps entities to SQL objects or runtime connections. What operational condition would provide the earliest useful regression warning?
- Monitor config validation and service startup errors
- Monitor missing correlation and sampling errors
- Monitor token validation failures and auth configuration
- Monitor procedure errors and API write attempts
Explanation
Correct Answer
A:
No configuration maps entities to SQL objects or runtime connections. Monitor config validation and service startup errors.
Incorrect Answers
B:
“Monitor missing correlation and sampling errors” concerns HTTP response latency is available but SQL dependency duration is missing; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Monitor config validation and service startup errors.
C:
“Monitor token validation failures and auth configuration” concerns Anonymous API access bypasses identity checks; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Monitor config validation and service startup errors.
D:
“Monitor procedure errors and API write attempts” concerns Direct table insert bypasses business constraints; the reported problem instead is No configuration maps entities to SQL objects or runtime connections. Monitor config validation and service startup errors.
Question 546
Northstar Analytics is responsible for an Azure SQL or Microsoft SQL workload. A shopping app queries orders and their items in one GraphQL request. Operational evidence: GraphQL schema lacks relationship mapping despite SQL foreign key. What initial check best narrows the technical cause without altering business data?
- Review entity fields and DAB role action permissions
- Inspect DAB relationships and entity naming
- Inspect DAB configuration schema, source type and connection auth
- Inspect DAB entity pagination and max page size
Explanation
Correct Answer
B:
GraphQL schema lacks relationship mapping despite SQL foreign key. Inspect DAB relationships and entity naming.
Incorrect Answers
A:
“Review 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: GraphQL schema lacks relationship mapping despite SQL foreign key. Inspect DAB relationships and entity naming.
C:
“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 GraphQL schema lacks relationship mapping despite SQL foreign key. Inspect DAB relationships and entity naming.
D:
“Inspect DAB entity pagination and max page size” concerns Unbounded pages risk resource exhaustion; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Inspect DAB relationships and entity naming.
Question 547
At Maple Harbor Research, 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. Which proposed change is the most suitable response to the observed constraint?
- Configure supported Azure Functions SQL trigger binding with least privilege
- Configure supported one-to-many GraphQL relationship between entities
- Configure supported JWT authentication and scoped API roles
- Instrument supported SQL dependencies and correlation identifiers
Explanation
Correct Answer
B:
GraphQL schema lacks relationship mapping despite SQL foreign key. Configure supported one-to-many GraphQL relationship between entities.
Incorrect Answers
A:
“Configure supported Azure Functions SQL trigger binding with least privilege” concerns Polling entire table every minute is wasteful; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Configure supported one-to-many GraphQL relationship between entities.
C:
“Configure supported JWT authentication and scoped API roles” concerns Anonymous API access bypasses identity checks; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Configure supported one-to-many GraphQL relationship between entities.
D:
“Instrument supported SQL dependencies and correlation identifiers” 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. Configure supported one-to-many GraphQL relationship between entities.
Question 548
A database engineer at Juniper Commerce is investigating this case: A shopping app queries orders and their items in one GraphQL request. The relevant finding is: GraphQL schema lacks relationship mapping despite SQL foreign key. 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
- Query with consumer and admin test roles
- Request successive pages from a synthetic large dataset
Explanation
Correct Answer
B:
GraphQL schema lacks relationship mapping despite SQL foreign key. Query synthetic order with multiple line items through GraphQL.
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 GraphQL schema lacks relationship mapping despite SQL foreign key. Query synthetic order with multiple line items through GraphQL.
C:
“Query with consumer and admin test roles” concerns Role mapping permits clients to select every column; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Query synthetic order with multiple line items through GraphQL.
D:
“Request successive pages from a synthetic large dataset” concerns Unbounded pages risk resource exhaustion; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Query synthetic order with multiple line items through GraphQL.
Question 549
Summit Logistics is responsible for an Azure SQL or Microsoft SQL workload. A shopping app queries orders and their items in one GraphQL request. Operational evidence: GraphQL schema lacks relationship mapping despite SQL foreign key. Which acceptance result most directly demonstrates the requirement has been satisfied?
- Pages are bounded and navigation returns no unintended duplicates
- Downstream receives committed changes in intended order
- Nested items match parent order with no unintended data
- Workflow receives correct state without blocking OLTP transaction
Explanation
Correct Answer
C:
GraphQL schema lacks relationship mapping despite SQL foreign key. Nested items match parent order with no unintended data.
Incorrect Answers
A:
“Pages are bounded and navigation returns no unintended duplicates” concerns Unbounded pages risk resource exhaustion; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Nested items match parent order with no unintended data.
B:
“Downstream receives committed changes in intended order” concerns Nightly full refresh misses interim state; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Nested items match parent order with no unintended data.
D:
“Workflow receives correct state without blocking OLTP transaction” concerns One-off SQL triggers cannot safely call external systems; the reported problem instead is GraphQL schema lacks relationship mapping despite SQL foreign key. Nested items match parent order with no unintended data.
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.