Microsoft DP-800 Questions & Answers

Combine DAB permissions with SQL RLS where applicable. The current task instead requires this action: rate-limit expensive query shapes and monitor access logs.

Prevent arbitrary tenant context spoofing and test privileged access. The current task instead requires this action: rate-limit expensive query shapes and monitor access logs.

Reset pooled connections and validate context on each request. The current task instead requires this action: rate-limit expensive query shapes and monitor access logs.

DAB can surface declared stored procedures without granting arbitrary query execution.

DAB generates endpoints from explicit configuration rather than automatically exposing every table.

Expose an authorized DAB REST endpoint with approved methods and resource paths. The relevant technical condition instead is that configure DAB entity relationships with matching source/target keys.

Model calls and retrieval calls each succeed only with required scopes. However, that result would not establish the required outcome: anonymous calls fail while authorized SQL workloads succeed.

Two test principals receive appropriately different display values. However, that result would not establish the required outcome: anonymous calls fail while authorized SQL workloads succeed.

A role-based test demonstrates restricted account values are masked. However, that result would not establish the required outcome: anonymous calls fail while authorized SQL workloads succeed.

Changing project source alone does not apply DDL to the deployed database. The actual technical constraint is that mis-targeted deployments can damage production regardless of SQL correctness.

Schema reconciliation can propose destructive changes that threaten existing records. The actual technical constraint is that mis-targeted deployments can damage production regardless of SQL correctness.

Cross-system contracts can fail even when individual SQL procedures are correct. The actual technical constraint is that mis-targeted deployments can damage production regardless of SQL correctness.

Review cascading deletes for unintended financial data loss. The current task instead requires this action: separate creation time from event time and validate clock policy.

Check memory capacity and unsupported features before migration. The current task instead requires this action: separate creation time from event time and validate clock policy.

Monitor source availability and credential rotation. The current task instead requires this action: separate creation time from event time and validate clock policy.

Reconciling generated claims with SQL source values before publishing results would not correct a model sometimes produces markdown instead of the requested JSON object for an automated workflow. Validate structured model output against a strict schema and reject invalid responses.

Data minimization reduces prompt exposure and cost without losing relevant context.

Structured JSON preserves field boundaries and escaping for downstream model prompts.

Staging resolves its own Azure SQL endpoint and local development still works. However, that result would not establish the required outcome: a staging start resolves each declared source without runtime errors.

Page requests return stable bounded records without gaps. However, that result would not establish the required outcome: a staging start resolves each declared source without runtime errors.

Partners read approved columns and cannot modify base tables. However, that result would not establish the required outcome: a staging start resolves each declared source without runtime errors.

Lexical retrieval protects exact tokens while vectors address paraphrases. The actual technical constraint is that independent retrieval branches can produce overlapping hits and uncalibrated scores.

Embedding similarity can confuse near-looking product codes that must match exactly. The actual technical constraint is that independent retrieval branches can produce overlapping hits and uncalibrated scores.

Full-text predicates require a configured index and supported column types. The actual technical constraint is that independent retrieval branches can produce overlapping hits and uncalibrated scores.

Reset pooled connections and validate context on each request. The current task instead requires this action: test every write operation and auditing requirements.

Keep a tool allowlist and capture authenticated invocations. The current task instead requires this action: test every write operation and auditing requirements.

Rehearse key recovery and avoid distributing keys in scripts. The current task instead requires this action: test every write operation and auditing requirements.

This action addresses a different case: An RLS policy uses SESSION_CONTEXT set directly from untrusted request text. For that case, session context is only safe as an authorization input when callers cannot impersonate other tenants. For this case, it does not directly correct the observed problem; the distinguishing issue is security enforcement must be tested with the exact executing principal. The specifically relevant immediate technical action is: Verify RLS behavior under every service principal and prohibit unnecessary bypass roles.

Replacing excessive privileges with minimum SELECT and no UNMASK entitlement would not correct a DBA enables RLS but bulk export uses a high privilege or bypass identity. Verify RLS behavior under every service principal and prohibit unnecessary bypass roles.

This action addresses a different case: A container app's managed identity can log in but cannot read the required database view. For that case, azure identity authentication and database authorization are distinct checks. For this case, it does not directly correct the observed problem; the distinguishing issue is security enforcement must be tested with the exact executing principal. The specifically relevant immediate technical action is: Verify RLS behavior under every service principal and prohibit unnecessary bypass roles.

Malformed output is quarantined and valid output produces typed records. However, that result would not establish the required outcome: a fixture response yields the expected text without transport headers.

The approved identity receives a 2xx response while an unauthorized one fails. However, that result would not establish the required outcome: a fixture response yields the expected text without transport headers.

A JSON parser reconstructs the intended order IDs and amounts. However, that result would not establish the required outcome: a fixture response yields the expected text without transport headers.