Microsoft DP-800 Questions & Answers

Model size increases cost and latency without guaranteeing proportional quality gains.

Vector dimensionality is fixed by the column and must match the query vector.

IDs alone lack the natural-language signal needed for semantic retrieval.

Known nearest-neighbor fixtures appear first in the final order. However, that result would not establish the required outcome: the corrected query executes and returns expected similar records.

Known phrase and inflection tests return expected articles. However, that result would not establish the required outcome: the corrected query executes and returns expected similar records.

The quoted phrase test excludes documents without that phrase. However, that result would not establish the required outcome: the corrected query executes and returns expected similar records.

Metadata-based partition switching requires strict schema and partition alignment. The actual technical constraint is that misaligned indexes can block efficient partition maintenance.

A surrogate primary key alone does not protect a separate business identifier. The actual technical constraint is that misaligned indexes can block efficient partition maintenance.

Referential integrity prevents orphan children unless cascade or other actions are deliberately configured. The actual technical constraint is that misaligned indexes can block efficient partition maintenance.

Minimize trigger side effects and audit dependent trigger paths. The current task instead requires this action: implement transactional outbox or supported change notifications.

Restrict callers to authorized tenant and customer context. The current task instead requires this action: implement transactional outbox or supported change notifications.

Implement idempotent retry and bounded transaction duration. The current task instead requires this action: implement transactional outbox or supported change notifications.

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

Numeric reconciliation is a structured calculation, not a reason to hallucinate an answer from documents.

RAG is appropriate only if the retriever enforces contractual permissions.

Attack strings are treated as data and queries return only intended rows. However, that result would not establish the required outcome: tests resolve the intended procedure and handle null/invalid inputs.

A test UPDATE completes once with expected values and no recursion error. However, that result would not establish the required outcome: tests resolve the intended procedure and handle null/invalid inputs.

Boundary amounts return correct DECIMAL values in unit tests. However, that result would not establish the required outcome: tests resolve the intended procedure and handle null/invalid inputs.

The stored procedure enables outbound HTTP but requires correct permissions, endpoint reachability and payload formatting. The actual technical constraint is that an authorization error occurs before model inference can produce valid content.

Sending unauthorized rows to a model is a disclosure even if its final answer omits them. The actual technical constraint is that an authorization error occurs before model inference can produce valid content.

RAG can inject up-to-date source evidence at answer time rather than encoding it in weights. The actual technical constraint is that an authorization error occurs before model inference can produce valid content.

Separate key custodianship and audit key usage. The current task instead requires this action: protect client-side keys and plan query limitations and rotation.

Reset pooled connections and validate context on each request. The current task instead requires this action: protect client-side keys and plan query limitations and rotation.

Monitor service-principal grants and run negative authorization tests. The current task instead requires this action: protect client-side keys and plan query limitations and rotation.

Summarize or chunk results within supported token and request limits before model invocation. The relevant technical condition instead is that apply database RLS and data minimization before constructing the outbound payload.

RAG is appropriate only if the retriever enforces contractual permissions.

Reconciling generated claims with SQL source values before publishing results addresses a different database behavior; the relevant distinction is that apply database RLS and data minimization before constructing the outbound payload.

A forged admin header fails while valid signed identities receive correct rights. However, that result would not establish the required outcome: an anonymous request is denied and an approved role sees only permitted fields.

Approved procedures decrypt the target values and unauthorized roles cannot open keys. However, that result would not establish the required outcome: an anonymous request is denied and an approved role sees only permitted fields.

A simulated low-privilege role cannot infer restricted personal identifiers. However, that result would not establish the required outcome: an anonymous request is denied and an approved role sees only permitted fields.

SCHEMABINDING protects referenced definitions against incompatible schema changes. The actual technical constraint is that a view centralizes a query contract without storing a second copy by default.

SQL triggers run per statement and inserted can contain multiple rows. The actual technical constraint is that a view centralizes a query contract without storing a second copy by default.

Nested or recursive trigger behavior can cause cycles and unexpected work. The actual technical constraint is that a view centralizes a query contract without storing a second copy by default.