Microsoft DP-800 Questions & Answers

External model quotas and transient errors require controlled retry behavior.

The binding can detect changes and invoke processing without polling arbitrary full tables.

A database model definition binds SQL AI operations to a specific external provider configuration.

Integration tests pass separately for the selected REST and GraphQL operations. However, that result would not establish the required outcome: gET/PATCH tests enforce intended roles and return expected status codes.

After a stock change, clients see updated counts within the defined freshness SLA. However, that result would not establish the required outcome: gET/PATCH tests enforce intended roles and return expected status codes.

An authorized request runs the report and rejects unauthorized procedure calls. However, that result would not establish the required outcome: gET/PATCH tests enforce intended roles and return expected status codes.

A poor cardinality estimate can induce unsuitable joins and memory grants. The actual technical constraint is that platform-native query insight tools expose historical workload statistics for managed instances.

Database-level settings can affect many workloads and engine versions differently. The actual technical constraint is that platform-native query insight tools expose historical workload statistics for managed instances.

Opposite lock acquisition sequences can form a cyclic wait. The actual technical constraint is that platform-native query insight tools expose historical workload statistics for managed instances.

Review grants and test bypass paths. The current task instead requires this action: audit schema role memberships after every release.

Monitor service-principal grants and run negative authorization tests. The current task instead requires this action: audit schema role memberships after every release.

Tracking principal creation across environments addresses a different database behavior; the relevant distinction is that audit schema role memberships after every release.

Summarize or chunk results within supported token and request limits before model invocation. The relevant technical condition instead is that implement bounded retry/backoff with idempotency and dead-letter handling.

HTTP response metadata and generated text are different parts of the payload.

Arbitrary external REST calls risk server-side request forgery and data exfiltration.

A staging upgrade preserves rows and enforces the new constraint. However, that result would not establish the required outcome: after publish, the target contains the intended index and tested workload improves.

Automated tests reject negative amounts and accept valid boundary values. However, that result would not establish the required outcome: after publish, the target contains the intended index and tested workload improves.

The merged procedure passes both teams' regression tests. However, that result would not establish the required outcome: after publish, the target contains the intended index and tested workload improves.

Different model endpoints can have different data governance and retention arrangements. The actual technical constraint is that tool scope governs what the model can invoke beyond ordinary chat text.

Code generation is separate from authorized database deployment. The actual technical constraint is that tool scope governs what the model can invoke beyond ordinary chat text.

Generated code can violate least privilege even if it appears syntactically correct. The actual technical constraint is that tool scope governs what the model can invoke beyond ordinary chat text.

Keep principal grants least-privilege and monitored. The current task instead requires this action: manage server allowlists and revoke unused tokens.

Review grants and server capabilities after updates. The current task instead requires this action: manage server allowlists and revoke unused tokens.

Require approved pull requests and deployment identities. The current task instead requires this action: manage server allowlists and revoke unused tokens.

Using a recursive CTE with an anchor member and a terminating recursive member would not correct a developer assumes a CTE named in one statement remains available to the next statement. Repeat the expression or persist intermediate results in a temporary table when necessary.

OPENJSON expands array elements into tabular rows for joins and validation.

A regex predicate evaluates pattern matching rather than fixed substring equality.

A role-based test demonstrates restricted account values are masked. However, that result would not establish the required outcome: a simulated low-privilege role cannot infer restricted personal identifiers.

The identity creates an approved test object but cannot alter production schemas. However, that result would not establish the required outcome: a simulated low-privilege role cannot infer restricted personal identifiers.

A privileged SQL-only session cannot read plaintext while an approved client decrypts. However, that result would not establish the required outcome: a simulated low-privilege role cannot infer restricted personal identifiers.

Data minimization reduces prompt exposure and cost without losing relevant context. The actual technical constraint is that JSON encoding preserves numeric representation better than locale-dependent concatenation.

Context-window constraints and cost require bounded prompt construction. The actual technical constraint is that JSON encoding preserves numeric representation better than locale-dependent concatenation.

Rate limiting is often transient and should not erase durable database work. The actual technical constraint is that JSON encoding preserves numeric representation better than locale-dependent concatenation.