Microsoft DP-800 Practice Test 17 - Prepaway
Practice Exams:

Pass Microsoft DP-800 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

DP-800 Premium ETE File


  • Premium File 101 Questions & Answers. Last Update: Nov 06, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Microsoft DP-800 Practice Test 17

Question 160

A help-desk knowledge table is updated frequently but its embeddings are only generated during an initial import, leaving search results stale. What would be a valid post-database-change verification?

  1. The FAQ write commits promptly and a background worker creates a matching authorized vector.
  2. Database transactions remain available during a model outage and embeddings catch up after recovery.
  3. A test query retrieves authorized matching image and text records with validated accuracy.
  4. A changed row's embedding is refreshed within the accepted time window and old results no longer dominate.

Explanation

Correct Answer

D:

A changed row's embedding is refreshed within the accepted time window and old results no longer dominate.

Incorrect Answers

A:

The FAQ write commits promptly and a background worker creates a matching authorized vector. A changed row's embedding is refreshed within the accepted time window and old results no longer dominate.

B:

Database transactions remain available during a model outage and embeddings catch up after recovery. A changed row's embedding is refreshed within the accepted time window and old results no longer dominate.

C:

A test query retrieves authorized matching image and text records with validated accuracy. A changed row's embedding is refreshed within the accepted time window and old results no longer dominate.

Question 161

A telemetry ingestion service sees hot-row latch contention in a small transient state table during bursty writes. Which TWO options together specify a corrective step and a meaningful test?

  1. Define a composite uniqueness constraint across the tenant identifier and invoice code.
  2. A load test shows lower contention without unacceptable loss of required durable records.
  3. Each tenant has unique invoice codes while other tenants can reuse the same code safely.
  4. Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features.
  5. Check native JSON indexing support or use a supported indexed computed-property strategy where appropriate.

Explanation

Correct Answers

B:

A load test shows lower contention without unacceptable loss of required durable records. Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features.

D:

Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features.

Incorrect Answers

A:

Define a composite uniqueness constraint across the tenant identifier and invoice code. Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features. A load test shows lower contention without unacceptable loss of required durable records.

C:

Each tenant has unique invoice codes while other tenants can reuse the same code safely. Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features. A load test shows lower contention without unacceptable loss of required durable records.

E:

Check native JSON indexing support or use a supported indexed computed-property strategy where appropriate. Evaluate an appropriate memory-optimized table design and durability choice under the platform's supported features.

Question 162

A team switches to SDK-style SQL Database Projects but assumes copying .sql files without a project definition creates a validated deployable model. What should the database developer do FIRST within approved procedures?

  1. Require appropriate protected branches, successful CI, environment approvals, and traceable release gates.
  2. Configure the supported SDK-style project, dependencies, and build validation in CI.
  3. Rotate the exposed credential and move secrets to an approved secret store with restricted pipeline identity.
  4. Version reference data in a reviewed idempotent deployment process with migration tests.

Explanation

Correct Answer

B:

Configure the supported SDK-style project, dependencies, and build validation in CI. A database project compiles and validates schema dependencies, not merely stores scripts.

Incorrect Answers

A:

Require appropriate protected branches, successful CI, environment approvals, and traceable release gates. A database project compiles and validates schema dependencies, not merely stores scripts. Configure the supported SDK-style project, dependencies, and build validation in CI.

C:

Rotate the exposed credential and move secrets to an approved secret store with restricted pipeline identity. A database project compiles and validates schema dependencies, not merely stores scripts. Configure the supported SDK-style project, dependencies, and build validation in CI.

D:

Version reference data in a reviewed idempotent deployment process with migration tests. A database project compiles and validates schema dependencies, not merely stores scripts. Configure the supported SDK-style project, dependencies, and build validation in CI.

Question 163

A GitHub Copilot chat connects to a SQL MCP server configured with a broad administrator identity and developers plan to run generated queries against production. Which clue best distinguishes this issue from similar incidents?

  1. MCP tool metadata shows privileges that include schema changes and unrelated sensitive tables.
  2. The query explanation shows proposed changes but the database still contains the original stored procedure.
  3. A dry-run prompt selects the production connection for an intended test schema query.
  4. AI-generated changes repeatedly use direct destructive alterations instead of the required deployment-project workflow.

Explanation

Correct Answer

A:

MCP tool metadata shows privileges that include schema changes and unrelated sensitive tables. Giving an assistant tools extends its action surface and must not imply unrestricted administrative authority.

Incorrect Answers

B:

The query explanation shows proposed changes but the database still contains the original stored procedure. Giving an assistant tools extends its action surface and must not imply unrestricted administrative authority. MCP tool metadata shows privileges that include schema changes and unrelated sensitive tables.

C:

A dry-run prompt selects the production connection for an intended test schema query. Giving an assistant tools extends its action surface and must not imply unrestricted administrative authority. MCP tool metadata shows privileges that include schema changes and unrelated sensitive tables.

D:

AI-generated changes repeatedly use direct destructive alterations instead of the required deployment-project workflow. Giving an assistant tools extends its action surface and must not imply unrestricted administrative authority. MCP tool metadata shows privileges that include schema changes and unrelated sensitive tables.

Question 164

A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Select TWO: the best action and the outcome that confirms it worked.

  1. Review partition alignment and required uniqueness keys for all indexes involved in maintenance.
  2. Define a composite uniqueness constraint across the tenant identifier and invoice code.
  3. Each tenant has unique invoice codes while other tenants can reuse the same code safely.
  4. After a tested maintenance change analytic scan cost improves and freshness commitments hold.
  5. Evaluate a columnstore index and validate load patterns and query performance before choosing the final storage design.

Explanation

Correct Answers

B:

Define a composite uniqueness constraint across the tenant identifier and invoice code. A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant.

C:

Each tenant has unique invoice codes while other tenants can reuse the same code safely. A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Define a composite uniqueness constraint across the tenant identifier and invoice code.

Incorrect Answers

A:

Review partition alignment and required uniqueness keys for all indexes involved in maintenance. A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Define a composite uniqueness constraint across the tenant identifier and invoice code.

D:

After a tested maintenance change analytic scan cost improves and freshness commitments hold. A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Define a composite uniqueness constraint across the tenant identifier and invoice code.

E:

Evaluate a columnstore index and validate load patterns and query performance before choosing the final storage design. A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Define a composite uniqueness constraint across the tenant identifier and invoice code.

Question 165

A procedure filters customers by region, usually returns ten rows but occasionally one region contains half the table; a cached plan performs poorly for the outlier. Which concept should guide the database developer in this situation?

  1. Triggers execute within database write workflows and need safeguards against recursion and broad unintended effects.
  2. Database setup scripts should be repeatable across CI and recovery environments.
  3. Procedure performance can vary with parameter cardinality even when SQL text is unchanged.
  4. INSTEAD OF triggers can customize view-write behavior but require clear business mapping and test coverage.

Explanation

Correct Answer

C:

Procedure performance can vary with parameter cardinality even when SQL text is unchanged.

Incorrect Answers

A:

Triggers execute within database write workflows and need safeguards against recursion and broad unintended effects. Procedure performance can vary with parameter cardinality even when SQL text is unchanged.

B:

Database setup scripts should be repeatable across CI and recovery environments. Procedure performance can vary with parameter cardinality even when SQL text is unchanged.

D:

INSTEAD OF triggers can customize view-write behavior but require clear business mapping and test coverage. Procedure performance can vary with parameter cardinality even when SQL text is unchanged.

Question 166

A regulated app writes SQL audit logs to short-lived storage and a retention job removes investigation evidence before the mandated period. Choose TWO statements: a suitable intervention and evidence of its success.

  1. Constrain GraphQL schema exposure and field/row authorization to approved data paths.
  2. Configure protected audit export and retention consistent with organizational policy.
  3. Bind the session context to trusted authenticated identity and prevent untrusted tenant switching.
  4. Test audit events remain retrievable and immutable for the required retention period.
  5. Unauthorized context switching is rejected and each user remains restricted to their approved tenant.

Explanation

Correct Answers

B:

Configure protected audit export and retention consistent with organizational policy. Test audit events remain retrievable and immutable for the required retention period.

D:

Test audit events remain retrievable and immutable for the required retention period.

Incorrect Answers

A:

Constrain GraphQL schema exposure and field/row authorization to approved data paths. Test audit events remain retrievable and immutable for the required retention period. Configure protected audit export and retention consistent with organizational policy.

C:

Bind the session context to trusted authenticated identity and prevent untrusted tenant switching. Test audit events remain retrievable and immutable for the required retention period. Configure protected audit export and retention consistent with organizational policy.

E:

Unauthorized context switching is rejected and each user remains restricted to their approved tenant. Test audit events remain retrievable and immutable for the required retention period. Configure protected audit export and retention consistent with organizational policy.

Question 167

A multitenant billing application assumes invoice codes are globally unique but the actual rule requires uniqueness only within each tenant. Which clue best distinguishes this issue from similar incidents?

  1. Columnstore DMV measurements show poor compression and substantial deleted-row percentages after the update surge.
  2. A test shows the old index rejects valid same-code invoices in different tenants but permits duplicate codes within one tenant under some paths.
  3. A direct SQL write bypasses the front-end validator and saves invalid guest counts.
  4. The current database permits changes with no dependable tamper-evidence verification route.

Explanation

Correct Answer

B:

A test shows the old index rejects valid same-code invoices in different tenants but permits duplicate codes within one tenant under some paths. Uniqueness keys must encode the business scope of identity rather than an arbitrary column.

Incorrect Answers

A:

Columnstore DMV measurements show poor compression and substantial deleted-row percentages after the update surge. Uniqueness keys must encode the business scope of identity rather than an arbitrary column. A test shows the old index rejects valid same-code invoices in different tenants but permits duplicate codes within one tenant under some paths.

C:

A direct SQL write bypasses the front-end validator and saves invalid guest counts. Uniqueness keys must encode the business scope of identity rather than an arbitrary column. A test shows the old index rejects valid same-code invoices in different tenants but permits duplicate codes within one tenant under some paths.

D:

The current database permits changes with no dependable tamper-evidence verification route. Uniqueness keys must encode the business scope of identity rather than an arbitrary column. A test shows the old index rejects valid same-code invoices in different tenants but permits duplicate codes within one tenant under some paths.

Question 168

A deployment script hardcodes a development database endpoint and CI unexpectedly connects to test during a production release. Choose TWO: one correct response and one verification of success.

  1. A dry run validates the intended server/database identity and production release targets only that environment.
  2. CI produces a valid model and catches an intentional missing-object reference.
  3. Parameterize supported deployment settings and enforce environment-scoped identity and target confirmation.
  4. Configure the supported SDK-style project, dependencies, and build validation in CI.
  5. Version reference data in a reviewed idempotent deployment process with migration tests.

Explanation

Correct Answers

A:

A dry run validates the intended server/database identity and production release targets only that environment. The corresponding check is whether parameterize supported deployment settings and enforce environment-scoped identity and target confirmation.

C:

Parameterize supported deployment settings and enforce environment-scoped identity and target confirmation. A dry run validates the intended server/database identity and production release targets only that environment.

Incorrect Answers

B:

CI produces a valid model and catches an intentional missing-object reference. A dry run validates the intended server/database identity and production release targets only that environment.

D:

Configure the supported SDK-style project, dependencies, and build validation in CI. A dry run validates the intended server/database identity and production release targets only that environment.

E:

Version reference data in a reviewed idempotent deployment process with migration tests. A dry run validates the intended server/database identity and production release targets only that environment.

Question 169

A company wants a low-code approval alert when a SQL business record changes, but its first design sends every table modification externally. What is the MOST appropriate initial remediation?

  1. Configure the supported DAB GraphQL relationship mapping and test nested authorization across entities.
  2. Use supported Change Tracking with a version watermark and controlled rehydration of current rows.
  3. Use a suitable Logic Apps or event-triggered integration with narrow filters and approved recipients.
  4. Version the DAB configuration and use environment-specific secret injection and validation during deployment.

Explanation

Correct Answer

C:

Use a suitable Logic Apps or event-triggered integration with narrow filters and approved recipients. Low-code automation must still enforce event selection, recipient controls, and auditability.

Incorrect Answers

A:

Configure the supported DAB GraphQL relationship mapping and test nested authorization across entities. Low-code automation must still enforce event selection, recipient controls, and auditability. Use a suitable Logic Apps or event-triggered integration with narrow filters and approved recipients.

B:

Use supported Change Tracking with a version watermark and controlled rehydration of current rows. Low-code automation must still enforce event selection, recipient controls, and auditability. Use a suitable Logic Apps or event-triggered integration with narrow filters and approved recipients.

D:

Version the DAB configuration and use environment-specific secret injection and validation during deployment. Low-code automation must still enforce event selection, recipient controls, and auditability. Use a suitable Logic Apps or event-triggered integration with narrow filters and approved recipients.

Question 170

A database project compiles locally but CI fails because a referenced shared database model exists only on one developer's machine. What distinction makes the recommended approach appropriate?

  1. Schema evolution should account for clients with independent deployment cycles.
  2. Database project source code must include secure authorization decisions, not just schema shapes.
  3. A project needs explicit versioned dependencies to support repeatable builds.
  4. Deployment configuration and identity should jointly prevent cross-environment mistakes.

Explanation

Correct Answer

C:

A project needs explicit versioned dependencies to support repeatable builds.

Incorrect Answers

A:

Schema evolution should account for clients with independent deployment cycles. A project needs explicit versioned dependencies to support repeatable builds.

B:

Database project source code must include secure authorization decisions, not just schema shapes. A project needs explicit versioned dependencies to support repeatable builds.

D:

Deployment configuration and identity should jointly prevent cross-environment mistakes. A project needs explicit versioned dependencies to support repeatable builds.

Developing AI-Enabled Database Solutions (DP-800) Practice Tests