Microsoft DP-800 Questions & Answers

Track model quality drift and escalation thresholds. The current task instead requires this action: reject unexpected fields and never trust generated totals without validation.

Keep source citations and access metadata attached. The current task instead requires this action: reject unexpected fields and never trust generated totals without validation.

Evaluate per-language drift and fallback routing. The current task instead requires this action: reject unexpected fields and never trust generated totals without validation.

Order an exact VECTOR_DISTANCE result ascending for nearest neighbors. The relevant technical condition instead is that generate query embeddings with the same approved model and dimension as the column.

Using RRF to reward documents ranking highly across multiple candidate lists would not correct a similarity API submits a query vector of different dimension than stored vectors. Generate query embeddings with the same approved model and dimension as the column.

Combine lexical and vector candidate retrieval in a hybrid ranking workflow. The relevant technical condition instead is that generate query embeddings with the same approved model and dimension as the column.

A tested switch moves the intended range without orphaning rows. However, that result would not establish the required outcome: a maintenance rehearsal successfully switches a partition with required constraints.

Reconciled payment totals match control calculations to the cent. However, that result would not establish the required outcome: a maintenance rehearsal successfully switches a partition with required constraints.

High-ID inserts and all dependent joins work in migration tests. However, that result would not establish the required outcome: a maintenance rehearsal successfully switches a partition with required constraints.

Nested or recursive trigger behavior can cause cycles and unexpected work. The actual technical constraint is that synchronous trigger work participates in the calling transaction and can increase latency.

SCHEMABINDING protects referenced definitions against incompatible schema changes. The actual technical constraint is that synchronous trigger work participates in the calling transaction and can increase latency.

Per-row scalar function calls may create expensive repeated execution on some workloads. The actual technical constraint is that synchronous trigger work participates in the calling transaction and can increase latency.

Version and validate provider schemas. The relevant technical condition instead is that log safe diagnostics and maintain circuit-breaker policy.

Restrict execute permission and log outbound destination. The current task instead requires this action: log safe diagnostics and maintain circuit-breaker policy.

Monitor truncation and fall back to SQL aggregates for precise counts.

Using parameterized stored procedures with scoped execution rights addresses a different database behavior; the relevant distinction is that use schema-qualified procedure references and explicit input/output parameter contracts.

SQL triggers run per statement and inserted can contain multiple rows.

Synchronous trigger work participates in the calling transaction and can increase latency.

A staging request returns the expected status and schema-valid response. However, that result would not establish the required outcome: the approved identity receives a 2xx response while an unauthorized one fails.

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

Representative requests fit allowed size and retain necessary evidence. However, that result would not establish the required outcome: the approved identity receives a 2xx response while an unauthorized one fails.

Server-side encryption can decrypt inside SQL with authorized key access, unlike client-controlled Always Encrypted. The actual technical constraint is that always Encrypted protects configured column values from the SQL engine during normal processing.

Auditing collection adds actor, operation and time evidence but does not itself block changes concerns a different mechanism; the relevant technical point is that always Encrypted protects configured column values from the SQL engine during normal processing.

Tamper-resistant off-host retention is stronger evidence than only local logs. The actual technical constraint is that always Encrypted protects configured column values from the SQL engine during normal processing.

Monitor truncation and fall back to SQL aggregates for precise counts.

Use managed identity/secure credentials and enforce timeouts. The current task instead requires this action: audit outbound data scope and access context.

Restrict execute permission and log outbound destination. The current task instead requires this action: audit outbound data scope and access context.

Validating provider-issued identity tokens and map claims to authorized application roles addresses a different database behavior; the relevant distinction is that configure authentication and per-entity role/operation permissions rather than public wildcard actions.

An open endpoint may expose inputs, outputs or costly compute to unauthorized callers.

DDM changes what unauthorized queries display; it is not data encryption.

A migration test catches incompatible column modification before production. However, that result would not establish the required outcome: both tools return the same verified sales metric from the view.

Tests resolve the intended procedure and handle null/invalid inputs. However, that result would not establish the required outcome: both tools return the same verified sales metric from the view.

A measured rewrite returns identical values with lower CPU. However, that result would not establish the required outcome: both tools return the same verified sales metric from the view.