Practice Exams:

Microsoft DP-900 Dumps

EXAM: Microsoft Azure Data Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

DP-900 Premium Bundle


  • Premium File 332 Questions & Answers
  • Training Course 32 Lectures
  • Study Guide 672 Pages

Microsoft DP-900 Practice Test 39

Question 380

At Silverfield Commerce searching orders by customer ID becomes slow. Which shortcut most directly threatens the intended data outcome?

  1. Permit arbitrary numeric parent IDs and trust the application never sends a typo.
  2. Deploy a full SQL Server virtual machine solely because every SQL database must have customer-managed operating system patches.
  3. Add indexes to every column without considering insert overhead or actual predicates.
  4. Use an INNER JOIN when the request explicitly includes customers with zero orders.

Answer & Explanations

Correct answer: C

A.

Permit arbitrary numeric parent IDs and trust the application never sends a typo. This concerns another issue: At Silvercrest Commerce all invoice lines must belong to an existing order. In the stated case—At Silverfield Commerce searching orders by customer ID becomes slow—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

B.

Deploy a full SQL Server virtual machine solely because every SQL database must have customer-managed operating system patches. This concerns another issue: At Harborcrest Apps a new order service needs managed T-SQL storage. In the stated case—At Silverfield Commerce searching orders by customer ID becomes slow—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

C.

Add indexes to every column without considering insert overhead or actual predicates. The scenario is: At Silverfield Commerce searching orders by customer ID becomes slow. This undermines the mechanism: An index can accelerate selective lookups but incurs storage and write-maintenance costs. Instead: Create an index on frequently filtered columns when measured query patterns justify it.

D.

Use an INNER JOIN when the request explicitly includes customers with zero orders. This concerns another issue: At Westbridge Retail retention analysts need every customer including nonbuyers. In the stated case—At Silverfield Commerce searching orders by customer ID becomes slow—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

Question 381

At Oakport Health patient lookups often filter by an indexed record identifier. Which design or Azure data approach best fits this requirement?

  1. Treat SQL NULL as unknown or missing and use IS NULL instead of equality comparison when filtering it.
  2. Use an Azure SQL Database elastic pool for several databases with varying, noncoincident resource demand.
  3. Use a SELECT query with a WHERE predicate to retrieve only qualifying orders.
  4. Create an index on frequently filtered columns when measured query patterns justify it.

Answer & Explanations

Correct answer: D

A.

Treat SQL NULL as unknown or missing and use IS NULL instead of equality comparison when filtering it. This addresses a different situation: At Willowport Health incomplete patient contact records need review. The present case is: At Oakport Health patient lookups often filter by an indexed record identifier. The relevant action here is: Create an index on frequently filtered columns when measured query patterns justify it.

B.

Use an Azure SQL Database elastic pool for several databases with varying, noncoincident resource demand. This addresses a different situation: At Cedarcrest SaaS hundreds of customer databases have different peak usage periods. The present case is: At Oakport Health patient lookups often filter by an indexed record identifier. The relevant action here is: Create an index on frequently filtered columns when measured query patterns justify it.

C.

Use a SELECT query with a WHERE predicate to retrieve only qualifying orders. This addresses a different situation: At Pineport Commerce support needs orders placed on one business day. The present case is: At Oakport Health patient lookups often filter by an indexed record identifier. The relevant action here is: Create an index on frequently filtered columns when measured query patterns justify it.

D.

Create an index on frequently filtered columns when measured query patterns justify it. This works because: An index can accelerate selective lookups but incurs storage and write-maintenance costs. The scenario is: At Oakport Health patient lookups often filter by an indexed record identifier. Verify the outcome by: Compare a representative query plan and response after adding a test index.

Question 382

At Oakport Health patient lookups often filter by an indexed record identifier. The team proposes this approach: Create an index on frequently filtered columns when measured query patterns justify it. Which technical principle explains the choice?

  1. Parameters separate query structure from values, preventing input text from changing SQL syntax.
  2. SQL data manipulation statements have different effects on persisted records and must be controlled by matching predicates.
  3. An index can accelerate selective lookups but incurs storage and write-maintenance costs.
  4. Serverless can scale compute according to activity and support auto-pause where configured and supported.

Answer & Explanations

Correct answer: C

A.

Parameters separate query structure from values, preventing input text from changing SQL syntax. That explains a separate situation: At Silverport Retail a support page searches names containing apostrophes. The current case is: At Oakport Health patient lookups often filter by an indexed record identifier. The actual mechanism is: An index can accelerate selective lookups but incurs storage and write-maintenance costs.

B.

SQL data manipulation statements have different effects on persisted records and must be controlled by matching predicates. That explains a separate situation: At Harborpoint Deliveries only one tracking record needs a status correction. The current case is: At Oakport Health patient lookups often filter by an indexed record identifier. The actual mechanism is: An index can accelerate selective lookups but incurs storage and write-maintenance costs.

C.

An index can accelerate selective lookups but incurs storage and write-maintenance costs. This principle supports the intervention: Create an index on frequently filtered columns when measured query patterns justify it. The relevant scenario is: At Oakport Health patient lookups often filter by an indexed record identifier. Verify the result by: Compare a representative query plan and response after adding a test index.

D.

Serverless can scale compute according to activity and support auto-pause where configured and supported. That explains a separate situation: At Pineport Research an internal reporting database is idle most evenings. The current case is: At Oakport Health patient lookups often filter by an indexed record identifier. The actual mechanism is: An index can accelerate selective lookups but incurs storage and write-maintenance costs.

Question 383

At Oakport Health patient lookups often filter by an indexed record identifier. After implementing this approach—Create an index on frequently filtered columns when measured query patterns justify it—which result would most directly confirm success?

  1. Generate staggered synthetic tenant loads and inspect whether pooled capacity meets service targets.
  2. Attempt to insert two fictional orders with the same key and verify the second fails.
  3. Compare a representative query plan and response after adding a test index.
  4. Update a fictional city postal reference once and verify all related customer records use the approved value.

Answer & Explanations

Correct answer: C

A.

Generate staggered synthetic tenant loads and inspect whether pooled capacity meets service targets. This tests a separate situation: At Cedarcrest SaaS hundreds of customer databases have different peak usage periods. The observed case is: At Oakport Health patient lookups often filter by an indexed record identifier. Use this acceptance check instead: Compare a representative query plan and response after adding a test index.

B.

Attempt to insert two fictional orders with the same key and verify the second fails. This tests a separate situation: At Bayfield Retail several orders can belong to one customer. The observed case is: At Oakport Health patient lookups often filter by an indexed record identifier. Use this acceptance check instead: Compare a representative query plan and response after adding a test index.

C.

Compare a representative query plan and response after adding a test index. This tests the targeted action: Create an index on frequently filtered columns when measured query patterns justify it. The reason is: An index can accelerate selective lookups but incurs storage and write-maintenance costs. The reported case is: At Oakport Health patient lookups often filter by an indexed record identifier.

D.

Update a fictional city postal reference once and verify all related customer records use the approved value. This tests a separate situation: At Harborcrest Tax a postal region's standard reference data changes annually. The observed case is: At Oakport Health patient lookups often filter by an indexed record identifier. Use this acceptance check instead: Compare a representative query plan and response after adding a test index.

Question 384

At Oakport Health patient lookups often filter by an indexed record identifier. Which shortcut most directly threatens the intended data outcome?

  1. Put COUNT(*) in a row-level WHERE clause and expect every database to accept it.
  2. Assume a continuously saturated production database will pause and deliver large idle savings.
  3. Add indexes to every column without considering insert overhead or actual predicates.
  4. Duplicate the order date on every line keyed by order ID and line number.

Answer & Explanations

Correct answer: C

A.

Put COUNT(*) in a row-level WHERE clause and expect every database to accept it. This concerns another issue: At Meadowcrest Insurance analysts need branches exceeding an incident threshold. In the stated case—At Oakport Health patient lookups often filter by an indexed record identifier—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

B.

Assume a continuously saturated production database will pause and deliver large idle savings. This concerns another issue: At Pineport Research an internal reporting database is idle most evenings. In the stated case—At Oakport Health patient lookups often filter by an indexed record identifier—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

C.

Add indexes to every column without considering insert overhead or actual predicates. The scenario is: At Oakport Health patient lookups often filter by an indexed record identifier. This undermines the mechanism: An index can accelerate selective lookups but incurs storage and write-maintenance costs. Instead: Create an index on frequently filtered columns when measured query patterns justify it.

D.

Duplicate the order date on every line keyed by order ID and line number. This concerns another issue: At Cedarbrook Manufacturing order header details repeat across line items. In the stated case—At Oakport Health patient lookups often filter by an indexed record identifier—reject: Add indexes to every column without considering insert overhead or actual predicates. The safer response is: Create an index on frequently filtered columns when measured query patterns justify it.

Question 385

At Cedarcrest Travel analysts need booking summaries without card tokens. Which design or Azure data approach best fits this requirement?

  1. Use a foreign key between order lines and their parent orders to enforce a valid relationship.
  2. Validate network access rules and Microsoft Entra authentication for Azure SQL connections.
  3. Use a SELECT query with a WHERE predicate to retrieve only qualifying orders.
  4. Use a view to expose a controlled reusable projection of sensitive transaction records.

Answer & Explanations

Correct answer: D

A.

Use a foreign key between order lines and their parent orders to enforce a valid relationship. This addresses a different situation: At Silvercrest Commerce all invoice lines must belong to an existing order. The present case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

B.

Validate network access rules and Microsoft Entra authentication for Azure SQL connections. This addresses a different situation: At Meadowbank Health only an approved application subnet should query a managed SQL database. The present case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

C.

Use a SELECT query with a WHERE predicate to retrieve only qualifying orders. This addresses a different situation: At Pineport Commerce support needs orders placed on one business day. The present case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

D.

Use a view to expose a controlled reusable projection of sensitive transaction records. This works because: A view provides a defined query interface and can omit fields that consumers should not see. The scenario is: At Cedarcrest Travel analysts need booking summaries without card tokens. Verify the outcome by: Query a test reporting view and confirm it excludes protected payment-token columns.

Question 386

At Cedarcrest Travel analysts need booking summaries without card tokens. The team proposes this approach: Use a view to expose a controlled reusable projection of sensitive transaction records. Which technical principle explains the choice?

  1. A view provides a defined query interface and can omit fields that consumers should not see.
  2. A primary key rejects duplicate or null identifiers so each order has a stable row identity.
  3. An outer join preserves rows on the designated side and represents missing matches with NULL columns.
  4. Engine family alone does not guarantee all self-managed plugins, versions or host customizations are supported by the managed offering.

Answer & Explanations

Correct answer: A

A.

A view provides a defined query interface and can omit fields that consumers should not see. This principle supports the intervention: Use a view to expose a controlled reusable projection of sensitive transaction records. The relevant scenario is: At Cedarcrest Travel analysts need booking summaries without card tokens. Verify the result by: Query a test reporting view and confirm it excludes protected payment-token columns.

B.

A primary key rejects duplicate or null identifiers so each order has a stable row identity. That explains a separate situation: At Bayfield Retail several orders can belong to one customer. The current case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

C.

An outer join preserves rows on the designated side and represents missing matches with NULL columns. That explains a separate situation: At Westbridge Retail retention analysts need every customer including nonbuyers. The current case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

D.

Engine family alone does not guarantee all self-managed plugins, versions or host customizations are supported by the managed offering. That explains a separate situation: At Oakridge Data a PostgreSQL service relies on a specialized geographic extension. The current case is: At Cedarcrest Travel analysts need booking summaries without card tokens. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

Question 387

At Cedarcrest Travel analysts need booking summaries without card tokens. After implementing this approach—Use a view to expose a controlled reusable projection of sensitive transaction records—which result would most directly confirm success?

  1. Query a test reporting view and confirm it excludes protected payment-token columns.
  2. Compare a representative query plan and response after adding a test index.
  3. Update a fictional city postal reference once and verify all related customer records use the approved value.
  4. Execute synthetic weekday and idle-period workloads and examine auto-pause and restart behavior.

Answer & Explanations

Correct answer: A

A.

Query a test reporting view and confirm it excludes protected payment-token columns. This tests the targeted action: Use a view to expose a controlled reusable projection of sensitive transaction records. The reason is: A view provides a defined query interface and can omit fields that consumers should not see. The reported case is: At Cedarcrest Travel analysts need booking summaries without card tokens.

B.

Compare a representative query plan and response after adding a test index. This tests a separate situation: At Silverfield Commerce searching orders by customer ID becomes slow. The observed case is: At Cedarcrest Travel analysts need booking summaries without card tokens. Use this acceptance check instead: Query a test reporting view and confirm it excludes protected payment-token columns.

C.

Update a fictional city postal reference once and verify all related customer records use the approved value. This tests a separate situation: At Harborcrest Tax a postal region's standard reference data changes annually. The observed case is: At Cedarcrest Travel analysts need booking summaries without card tokens. Use this acceptance check instead: Query a test reporting view and confirm it excludes protected payment-token columns.

D.

Execute synthetic weekday and idle-period workloads and examine auto-pause and restart behavior. This tests a separate situation: At Pineport Research an internal reporting database is idle most evenings. The observed case is: At Cedarcrest Travel analysts need booking summaries without card tokens. Use this acceptance check instead: Query a test reporting view and confirm it excludes protected payment-token columns.

Question 388

At Cedarcrest Travel analysts need booking summaries without card tokens. Which shortcut most directly threatens the intended data outcome?

  1. Assume newly inserted records will always appear at the bottom of an un-ordered query.
  2. Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck.
  3. Give every reporting user direct access to all underlying columns for convenience.
  4. Put all contact numbers in one semicolon-delimited customer column.

Answer & Explanations

Correct answer: C

A.

Assume newly inserted records will always appear at the bottom of an un-ordered query. This concerns another issue: At Cedarbank Logistics dispatch lists must show oldest outstanding shipments first. In the stated case—At Cedarcrest Travel analysts need booking summaries without card tokens—reject: Give every reporting user direct access to all underlying columns for convenience. The safer response is: Use a view to expose a controlled reusable projection of sensitive transaction records.

B.

Increase storage capacity to solve a CPU-bound query plan without examining the bottleneck. This concerns another issue: At Bayfield Travel application requests slow under concurrent booking loads. In the stated case—At Cedarcrest Travel analysts need booking summaries without card tokens—reject: Give every reporting user direct access to all underlying columns for convenience. The safer response is: Use a view to expose a controlled reusable projection of sensitive transaction records.

C.

Give every reporting user direct access to all underlying columns for convenience. The scenario is: At Cedarcrest Travel analysts need booking summaries without card tokens. This undermines the mechanism: A view provides a defined query interface and can omit fields that consumers should not see. Instead: Use a view to expose a controlled reusable projection of sensitive transaction records.

D.

Put all contact numbers in one semicolon-delimited customer column. This concerns another issue: At Meadowport Services customers often provide multiple contact phones. In the stated case—At Cedarcrest Travel analysts need booking summaries without card tokens—reject: Give every reporting user direct access to all underlying columns for convenience. The safer response is: Use a view to expose a controlled reusable projection of sensitive transaction records.

Question 389

At Harborview Banking external auditors require a restricted account activity projection. Which design or Azure data approach best fits this requirement?

  1. Create an index on frequently filtered columns when measured query patterns justify it.
  2. Use a view to expose a controlled reusable projection of sensitive transaction records.
  3. Use an INNER JOIN on approved keys to combine matching customer and order rows.
  4. Validate network access rules and Microsoft Entra authentication for Azure SQL connections.

Answer & Explanations

Correct answer: B

A.

Create an index on frequently filtered columns when measured query patterns justify it. This addresses a different situation: At Silverfield Commerce searching orders by customer ID becomes slow. The present case is: At Harborview Banking external auditors require a restricted account activity projection. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

B.

Use a view to expose a controlled reusable projection of sensitive transaction records. This works because: A view provides a defined query interface and can omit fields that consumers should not see. The scenario is: At Harborview Banking external auditors require a restricted account activity projection. Verify the outcome by: Query a test reporting view and confirm it excludes protected payment-token columns.

C.

Use an INNER JOIN on approved keys to combine matching customer and order rows. This addresses a different situation: At Cedarcrest Finance invoices must display the correct customer account. The present case is: At Harborview Banking external auditors require a restricted account activity projection. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

D.

Validate network access rules and Microsoft Entra authentication for Azure SQL connections. This addresses a different situation: At Meadowbank Health only an approved application subnet should query a managed SQL database. The present case is: At Harborview Banking external auditors require a restricted account activity projection. The relevant action here is: Use a view to expose a controlled reusable projection of sensitive transaction records.

Question 390

At Harborview Banking external auditors require a restricted account activity projection. The team proposes this approach: Use a view to expose a controlled reusable projection of sensitive transaction records. Which technical principle explains the choice?

  1. A view provides a defined query interface and can omit fields that consumers should not see.
  2. WHERE filters individual rows before projection into the result set.
  3. Third-normal-form design reduces repeated non-key dependencies and the anomalies they cause.
  4. Selecting a service tier should reflect the actual workload bottleneck rather than database size alone.

Answer & Explanations

Correct answer: A

A.

A view provides a defined query interface and can omit fields that consumers should not see. This principle supports the intervention: Use a view to expose a controlled reusable projection of sensitive transaction records. The relevant scenario is: At Harborview Banking external auditors require a restricted account activity projection. Verify the result by: Query a test reporting view and confirm it excludes protected payment-token columns.

B.

WHERE filters individual rows before projection into the result set. That explains a separate situation: At Pineport Commerce support needs orders placed on one business day. The current case is: At Harborview Banking external auditors require a restricted account activity projection. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

C.

Third-normal-form design reduces repeated non-key dependencies and the anomalies they cause. That explains a separate situation: At Harborcrest Tax a postal region's standard reference data changes annually. The current case is: At Harborview Banking external auditors require a restricted account activity projection. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

D.

Selecting a service tier should reflect the actual workload bottleneck rather than database size alone. That explains a separate situation: At Bayfield Travel application requests slow under concurrent booking loads. The current case is: At Harborview Banking external auditors require a restricted account activity projection. The actual mechanism is: A view provides a defined query interface and can omit fields that consumers should not see.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests