Microsoft DP-800 Questions & Answers

Referential integrity prevents orphan children unless cascade or other actions are deliberately configured.

Temporal history captures prior row versions when system versioning is enabled.

Partitioning is most helpful when queries constrain the partition key.

A restricted test query retrieves only authorized external records with acceptable latency. However, that result would not establish the required outcome: a point-in-time query returns the former invoice values after an update.

A test payload creates the expected number of items with correct types. However, that result would not establish the required outcome: a point-in-time query returns the former invoice values after an update.

Orphan inserts fail and approved delete scenarios behave as specified. However, that result would not establish the required outcome: a point-in-time query returns the former invoice values after an update.

Nested or recursive trigger behavior can cause cycles and unexpected work. The actual technical constraint is that a DELETE trigger exposes removed rows via deleted, not inserted.

A scalar function produces one value for each call but may affect query optimization. The actual technical constraint is that a DELETE trigger exposes removed rows via deleted, not inserted.

T-SQL UDFs have restrictions on side effects and cannot be arbitrary transactional commands. The actual technical constraint is that a DELETE trigger exposes removed rows via deleted, not inserted.

Use monitored retention and independent security custody. The current task instead requires this action: retain logs immutably where required and limit audit administrators.

Scope endpoint permissions and monitor request consumption. The current task instead requires this action: retain logs immutably where required and limit audit administrators.

Prevent arbitrary tenant context spoofing and test privileged access. The current task instead requires this action: retain logs immutably where required and limit audit administrators.

Temporal history captures prior row versions when system versioning is enabled.

Evaluate supported JSON index or indexed computed-column path for that SQL platform and version. The relevant technical condition instead is that evaluate memory-optimized tables where the specific SQL engine and workload support them.

A missing selective access path forces large table or clustered-index scans.

A security review finds no production secrets in prompt logs or history. However, that result would not establish the required outcome: the final query respects RLS while returning the caller's permitted rows.

Generated examples show placeholders and approved secret references. However, that result would not establish the required outcome: the final query respects RLS while returning the caller's permitted rows.

An approved SQL workspace exposes supported Copilot features for a licensed tester. However, that result would not establish the required outcome: the final query respects RLS while returning the caller's permitted rows.

CI log readers and artifact retention can expose credentials. The actual technical constraint is that shared overly privileged credentials increase blast radius across systems.

Existing data can prevent otherwise valid stricter schema changes. The actual technical constraint is that shared overly privileged credentials increase blast radius across systems.

Path ownership helps route high-impact DDL for accountable review. The actual technical constraint is that shared overly privileged credentials increase blast radius across systems.

Reviewing grants after schema migrations addresses a different database behavior; the relevant distinction is that avoid broad database role grants to fix one dynamic query.

Separate key custodianship and audit key usage. The current task instead requires this action: avoid broad database role grants to fix one dynamic query.

Document leakage tradeoffs before enabling secure enclaves. The current task instead requires this action: avoid broad database role grants to fix one dynamic query.

Normalizing vector length separates direction from magnitude for suitable similarity metrics.

Enforcing authorization in every retrieval branch before fusion and presentation would not correct a developer receives a VECTOR value but needs to inspect its number of dimensions in SQL. Use supported VECTORPROPERTY to obtain relevant vector metadata.

Independent retrieval branches can produce overlapping hits and uncalibrated scores.

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

Health checks succeed and authorized REST queries work after rollout. However, that result would not establish the required outcome: staging resolves its own Azure SQL endpoint and local development still works.

Container-based smoke tests connect securely to the intended Azure SQL database. However, that result would not establish the required outcome: staging resolves its own Azure SQL endpoint and local development still works.

Randomized encryption does not support general plaintext pattern matching inside the engine. The actual technical constraint is that column key hierarchy and client metadata must agree for encrypted column access.

DDM changes what unauthorized queries display; it is not data encryption. The actual technical constraint is that column key hierarchy and client metadata must agree for encrypted column access.

Dynamic masking is evaluated at query output rather than permanently altering storage. The actual technical constraint is that column key hierarchy and client metadata must agree for encrypted column access.