Pass Microsoft Azure Data DP-900 Exam in First Attempt Easily
Real Microsoft Azure Data DP-900 Exam Questions, Accurate & Verified Answers As Experienced in the Actual Test!

Verified by experts
3 products

You save $69.98

DP-900 Premium Bundle

  • Premium File 332 Questions & Answers
  • Last Update: Nov 14, 2026
  • Training Course 32 Lectures
  • Study Guide 672 Pages
$79.99 $149.97

Purchase Individually

  • Premium File

    332 Questions & Answers
    Last Update: Nov 14, 2026

    $76.99
    $69.99
  • Training Course

    32 Lectures

    $43.99
    $39.99
  • Study Guide

    672 Pages

    $43.99
    $39.99

Microsoft Azure Data Fundamentals DP-900 Practice Test 15

Question 140

A report needs total ordered value by product category instead of one row per sales item. If the team ignores the targeted approach (Use GROUP BY category with SUM of the order amount.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. Omitting WHERE from an UPDATE can change every row in the table.
  2. A plain ORDER BY merely sorts detail rows and does not aggregate totals.
  3. Repeating master data across transaction rows creates update anomalies.
  4. Adding an index indiscriminately can increase write maintenance and storage overhead.

Explanation

Correct Answer

B:

A plain ORDER BY merely sorts detail rows and does not aggregate totals. This risk follows from the exact scenario: A report needs total ordered value by product category instead of one row per sales item. The reason is gROUP BY forms groups for aggregate functions such as SUM. The direct mitigation is: Use GROUP BY category with SUM of the order amount.

Incorrect Answers

A:

Omitting WHERE from an UPDATE can change every row in the table. This is a real potential problem in a different scenario: An inventory correction must change Quantity for only item 402 without affecting any other item. The present case instead concerns A report needs total ordered value by product category instead of one row per sales item. With the targeted action omitted, the direct exposure is A plain ORDER BY merely sorts detail rows and does not aggregate totals.

C:

Repeating master data across transaction rows creates update anomalies. This is a real potential problem in a different scenario: A customer address is copied into every order and updates leave conflicting addresses in past rows. The present case instead concerns A report needs total ordered value by product category instead of one row per sales item. With the targeted action omitted, the direct exposure is A plain ORDER BY merely sorts detail rows and does not aggregate totals.

D:

Adding an index indiscriminately can increase write maintenance and storage overhead. This is a real potential problem in a different scenario: Queries frequently filter a very large Orders table by OrderDate and scan too many unrelated rows. The present case instead concerns A report needs total ordered value by product category instead of one row per sales item. With the targeted action omitted, the direct exposure is A plain ORDER BY merely sorts detail rows and does not aggregate totals.

Question 141

A support application must add one new record to an existing Orders table. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Store telephone values atomically in related rows rather than a comma-separated list.
  2. Use UPDATE with a WHERE predicate selecting ItemId 402.
  3. Use GROUP BY category with SUM of the order amount.
  4. Use INSERT INTO with the required column values.

Explanation

Correct Answer

D:

Use INSERT INTO with the required column values. This directly addresses the case: A support application must add one new record to an existing Orders table. The deciding technical reason is that iNSERT adds rows to a table while CREATE defines database objects. Verify the solution by checking: The new row appears once without replacing existing orders.

Incorrect Answers

A:

Store telephone values atomically in related rows rather than a comma-separated list. This is a legitimate approach for a different problem: A table stores three phone numbers in one comma-separated field but support staff must search an individual number. First normal form expects atomic values rather than repeating lists in one column. It does not directly satisfy the present constraint: A support application must add one new record to an existing Orders table. The needed outcome is: The new row appears once without replacing existing orders.

B:

Use UPDATE with a WHERE predicate selecting ItemId 402. This is a legitimate approach for a different problem: An inventory correction must change Quantity for only item 402 without affecting any other item. UPDATE modifies existing records and WHERE limits the target set. It does not directly satisfy the present constraint: A support application must add one new record to an existing Orders table. The needed outcome is: The new row appears once without replacing existing orders.

C:

Use GROUP BY category with SUM of the order amount. This is a legitimate approach for a different problem: A report needs total ordered value by product category instead of one row per sales item. GROUP BY forms groups for aggregate functions such as SUM. It does not directly satisfy the present constraint: A support application must add one new record to an existing Orders table. The needed outcome is: The new row appears once without replacing existing orders.

Question 142

A support application must add one new record to an existing Orders table. A team proposes: Use INSERT INTO with the required column values. Which observation would BEST demonstrate that this exact requirement was met?

  1. The new row appears once without replacing existing orders.
  2. A query returns the exact matching telephone value without splitting a single cell.
  3. Only the intended item's quantity changes after the transaction commits.
  4. The query returns one aggregate total for each category.

Explanation

Correct Answer

A:

The new row appears once without replacing existing orders. INSERT adds rows to a table while CREATE defines database objects. It is tied to this case: A support application must add one new record to an existing Orders table.

Incorrect Answers

B:

A query returns the exact matching telephone value without splitting a single cell. This would validate a different scenario: A table stores three phone numbers in one comma-separated field but support staff must search an individual number. The proposed change here is Use INSERT INTO with the required column values. and its decisive acceptance check is The new row appears once without replacing existing orders.

C:

Only the intended item's quantity changes after the transaction commits. This would validate a different scenario: An inventory correction must change Quantity for only item 402 without affecting any other item. The proposed change here is Use INSERT INTO with the required column values. and its decisive acceptance check is The new row appears once without replacing existing orders.

D:

The query returns one aggregate total for each category. This would validate a different scenario: A report needs total ordered value by product category instead of one row per sales item. The proposed change here is Use INSERT INTO with the required column values. and its decisive acceptance check is The new row appears once without replacing existing orders.

Question 143

During an architecture review, the team proposes: Use INSERT INTO with the required column values. The requirement is: A support application must add one new record to an existing Orders table. Which technical explanation BEST justifies this specific recommendation?

  1. First normal form expects atomic values rather than repeating lists in one column.
  2. INSERT adds rows to a table while CREATE defines database objects.
  3. UPDATE modifies existing records and WHERE limits the target set.
  4. GROUP BY forms groups for aggregate functions such as SUM.

Explanation

Correct Answer

B:

INSERT adds rows to a table while CREATE defines database objects. Evidence would be: The new row appears once without replacing existing orders. The choice avoids this risk: Using CREATE TABLE would create a schema object rather than a business record.

Incorrect Answers

A:

First normal form expects atomic values rather than repeating lists in one column. That principle applies to the separate requirement: A table stores three phone numbers in one comma-separated field but support staff must search an individual number. It may be true in that setting, but does not specifically explain why Use INSERT INTO with the required column values. is the best fit here. The relevant reason is INSERT adds rows to a table while CREATE defines database objects.

C:

UPDATE modifies existing records and WHERE limits the target set. That principle applies to the separate requirement: An inventory correction must change Quantity for only item 402 without affecting any other item. It may be true in that setting, but does not specifically explain why Use INSERT INTO with the required column values. is the best fit here. The relevant reason is INSERT adds rows to a table while CREATE defines database objects.

D:

GROUP BY forms groups for aggregate functions such as SUM. That principle applies to the separate requirement: A report needs total ordered value by product category instead of one row per sales item. It may be true in that setting, but does not specifically explain why Use INSERT INTO with the required column values. is the best fit here. The relevant reason is INSERT adds rows to a table while CREATE defines database objects.

Question 144

A support application must add one new record to an existing Orders table. If the team ignores the targeted approach (Use INSERT INTO with the required column values.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. Multiple values inside one field violate the usual first-normal-form design goal.
  2. Omitting WHERE from an UPDATE can change every row in the table.
  3. Using CREATE TABLE would create a schema object rather than a business record.
  4. A plain ORDER BY merely sorts detail rows and does not aggregate totals.

Explanation

Correct Answer

C:

Using CREATE TABLE would create a schema object rather than a business record. This risk follows from the exact scenario: A support application must add one new record to an existing Orders table. The reason is iNSERT adds rows to a table while CREATE defines database objects. The direct mitigation is: Use INSERT INTO with the required column values.

Incorrect Answers

A:

Multiple values inside one field violate the usual first-normal-form design goal. This is a real potential problem in a different scenario: A table stores three phone numbers in one comma-separated field but support staff must search an individual number. The present case instead concerns A support application must add one new record to an existing Orders table. With the targeted action omitted, the direct exposure is Using CREATE TABLE would create a schema object rather than a business record.

B:

Omitting WHERE from an UPDATE can change every row in the table. This is a real potential problem in a different scenario: An inventory correction must change Quantity for only item 402 without affecting any other item. The present case instead concerns A support application must add one new record to an existing Orders table. With the targeted action omitted, the direct exposure is Using CREATE TABLE would create a schema object rather than a business record.

D:

A plain ORDER BY merely sorts detail rows and does not aggregate totals. This is a real potential problem in a different scenario: A report needs total ordered value by product category instead of one row per sales item. The present case instead concerns A support application must add one new record to an existing Orders table. With the targeted action omitted, the direct exposure is Using CREATE TABLE would create a schema object rather than a business record.

Question 145

An inventory correction must change Quantity for only item 402 without affecting any other item. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Use UPDATE with a WHERE predicate selecting ItemId 402.
  2. Use GROUP BY category with SUM of the order amount.
  3. Define a primary key using a stable CustomerId field.
  4. Evaluate an index on the frequently filtered column and confirm its query plan.

Explanation

Correct Answer

A:

Use UPDATE with a WHERE predicate selecting ItemId 402. This directly addresses the case: An inventory correction must change Quantity for only item 402 without affecting any other item. The deciding technical reason is that uPDATE modifies existing records and WHERE limits the target set. Verify the solution by checking: Only the intended item's quantity changes after the transaction commits.

Incorrect Answers

B:

Use GROUP BY category with SUM of the order amount. This is a legitimate approach for a different problem: A report needs total ordered value by product category instead of one row per sales item. GROUP BY forms groups for aggregate functions such as SUM. It does not directly satisfy the present constraint: An inventory correction must change Quantity for only item 402 without affecting any other item. The needed outcome is: Only the intended item's quantity changes after the transaction commits.

C:

Define a primary key using a stable CustomerId field. This is a legitimate approach for a different problem: A customer table must uniquely identify each customer even when two people have the same display name. A primary key uniquely identifies each row and disallows null key values. It does not directly satisfy the present constraint: An inventory correction must change Quantity for only item 402 without affecting any other item. The needed outcome is: Only the intended item's quantity changes after the transaction commits.

D:

Evaluate an index on the frequently filtered column and confirm its query plan. This is a legitimate approach for a different problem: Queries frequently filter a very large Orders table by OrderDate and scan too many unrelated rows. Indexes improve selective access patterns at a cost to updates and space. It does not directly satisfy the present constraint: An inventory correction must change Quantity for only item 402 without affecting any other item. The needed outcome is: Only the intended item's quantity changes after the transaction commits.

Question 146

An inventory correction must change Quantity for only item 402 without affecting any other item. A team proposes: Use UPDATE with a WHERE predicate selecting ItemId 402. Which observation would BEST demonstrate that this exact requirement was met?

  1. The query returns one aggregate total for each category.
  2. Only the intended item's quantity changes after the transaction commits.
  3. The database rejects duplicate CustomerId values while allowing duplicate names.
  4. The query plan uses an appropriate index to avoid unnecessary row scanning where beneficial.

Explanation

Correct Answer

B:

Only the intended item's quantity changes after the transaction commits. UPDATE modifies existing records and WHERE limits the target set. It is tied to this case: An inventory correction must change Quantity for only item 402 without affecting any other item.

Incorrect Answers

A:

The query returns one aggregate total for each category. This would validate a different scenario: A report needs total ordered value by product category instead of one row per sales item. The proposed change here is Use UPDATE with a WHERE predicate selecting ItemId 402. and its decisive acceptance check is Only the intended item's quantity changes after the transaction commits.

C:

The database rejects duplicate CustomerId values while allowing duplicate names. This would validate a different scenario: A customer table must uniquely identify each customer even when two people have the same display name. The proposed change here is Use UPDATE with a WHERE predicate selecting ItemId 402. and its decisive acceptance check is Only the intended item's quantity changes after the transaction commits.

D:

The query plan uses an appropriate index to avoid unnecessary row scanning where beneficial. This would validate a different scenario: Queries frequently filter a very large Orders table by OrderDate and scan too many unrelated rows. The proposed change here is Use UPDATE with a WHERE predicate selecting ItemId 402. and its decisive acceptance check is Only the intended item's quantity changes after the transaction commits.

Question 147

During an architecture review, the team proposes: Use UPDATE with a WHERE predicate selecting ItemId 402. The requirement is: An inventory correction must change Quantity for only item 402 without affecting any other item. Which technical explanation BEST justifies this specific recommendation?

  1. GROUP BY forms groups for aggregate functions such as SUM.
  2. A primary key uniquely identifies each row and disallows null key values.
  3. UPDATE modifies existing records and WHERE limits the target set.
  4. Indexes improve selective access patterns at a cost to updates and space.

Explanation

Correct Answer

C:

UPDATE modifies existing records and WHERE limits the target set. Evidence would be: Only the intended item's quantity changes after the transaction commits. The choice avoids this risk: Omitting WHERE from an UPDATE can change every row in the table.

Incorrect Answers

A:

GROUP BY forms groups for aggregate functions such as SUM. That principle applies to the separate requirement: A report needs total ordered value by product category instead of one row per sales item. It may be true in that setting, but does not specifically explain why Use UPDATE with a WHERE predicate selecting ItemId 402. is the best fit here. The relevant reason is UPDATE modifies existing records and WHERE limits the target set.

B:

A primary key uniquely identifies each row and disallows null key values. That principle applies to the separate requirement: A customer table must uniquely identify each customer even when two people have the same display name. It may be true in that setting, but does not specifically explain why Use UPDATE with a WHERE predicate selecting ItemId 402. is the best fit here. The relevant reason is UPDATE modifies existing records and WHERE limits the target set.

D:

Indexes improve selective access patterns at a cost to updates and space. That principle applies to the separate requirement: Queries frequently filter a very large Orders table by OrderDate and scan too many unrelated rows. It may be true in that setting, but does not specifically explain why Use UPDATE with a WHERE predicate selecting ItemId 402. is the best fit here. The relevant reason is UPDATE modifies existing records and WHERE limits the target set.

Question 148

An inventory correction must change Quantity for only item 402 without affecting any other item. If the team ignores the targeted approach (Use UPDATE with a WHERE predicate selecting ItemId 402.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. A plain ORDER BY merely sorts detail rows and does not aggregate totals.
  2. Using a nonunique display name as a row identifier can misidentify customers.
  3. Adding an index indiscriminately can increase write maintenance and storage overhead.
  4. Omitting WHERE from an UPDATE can change every row in the table.

Explanation

Correct Answer

D:

Omitting WHERE from an UPDATE can change every row in the table. This risk follows from the exact scenario: An inventory correction must change Quantity for only item 402 without affecting any other item. The reason is uPDATE modifies existing records and WHERE limits the target set. The direct mitigation is: Use UPDATE with a WHERE predicate selecting ItemId 402.

Incorrect Answers

A:

A plain ORDER BY merely sorts detail rows and does not aggregate totals. This is a real potential problem in a different scenario: A report needs total ordered value by product category instead of one row per sales item. The present case instead concerns An inventory correction must change Quantity for only item 402 without affecting any other item. With the targeted action omitted, the direct exposure is Omitting WHERE from an UPDATE can change every row in the table.

B:

Using a nonunique display name as a row identifier can misidentify customers. This is a real potential problem in a different scenario: A customer table must uniquely identify each customer even when two people have the same display name. The present case instead concerns An inventory correction must change Quantity for only item 402 without affecting any other item. With the targeted action omitted, the direct exposure is Omitting WHERE from an UPDATE can change every row in the table.

C:

Adding an index indiscriminately can increase write maintenance and storage overhead. This is a real potential problem in a different scenario: Queries frequently filter a very large Orders table by OrderDate and scan too many unrelated rows. The present case instead concerns An inventory correction must change Quantity for only item 402 without affecting any other item. With the targeted action omitted, the direct exposure is Omitting WHERE from an UPDATE can change every row in the table.

Question 149

A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Use a JOIN predicate on the matching customer keys.
  2. Create a SQL view over the current Customers table with its active filter.
  3. Use INSERT INTO with the required column values.
  4. Use UPDATE with a WHERE predicate selecting ItemId 402.

Explanation

Correct Answer

B:

Create a SQL view over the current Customers table with its active filter. This directly addresses the case: A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. The deciding technical reason is that a standard SQL view stores a query definition over base tables. Verify the solution by checking: Selecting the view returns current qualifying customers after base records change.

Incorrect Answers

A:

Use a JOIN predicate on the matching customer keys. This is a legitimate approach for a different problem: An analyst needs customers and their invoices in one result, matched by CustomerId across two tables. SQL JOIN relates matching rows from separate tables. It does not directly satisfy the present constraint: A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. The needed outcome is: Selecting the view returns current qualifying customers after base records change.

C:

Use INSERT INTO with the required column values. This is a legitimate approach for a different problem: A support application must add one new record to an existing Orders table. INSERT adds rows to a table while CREATE defines database objects. It does not directly satisfy the present constraint: A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. The needed outcome is: Selecting the view returns current qualifying customers after base records change.

D:

Use UPDATE with a WHERE predicate selecting ItemId 402. This is a legitimate approach for a different problem: An inventory correction must change Quantity for only item 402 without affecting any other item. UPDATE modifies existing records and WHERE limits the target set. It does not directly satisfy the present constraint: A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. The needed outcome is: Selecting the view returns current qualifying customers after base records change.

Question 150

A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly. A team proposes: Create a SQL view over the current Customers table with its active filter. Which observation would BEST demonstrate that this exact requirement was met?

  1. Each invoice row is combined with the corresponding customer without guessing name equality.
  2. The new row appears once without replacing existing orders.
  3. Selecting the view returns current qualifying customers after base records change.
  4. Only the intended item's quantity changes after the transaction commits.

Explanation

Correct Answer

C:

Selecting the view returns current qualifying customers after base records change. A standard SQL view stores a query definition over base tables. It is tied to this case: A reporting team wants a reusable filtered representation of active customers without copying all customer rows nightly.

Incorrect Answers

A:

Each invoice row is combined with the corresponding customer without guessing name equality. This would validate a different scenario: An analyst needs customers and their invoices in one result, matched by CustomerId across two tables. The proposed change here is Create a SQL view over the current Customers table with its active filter. and its decisive acceptance check is Selecting the view returns current qualifying customers after base records change.

B:

The new row appears once without replacing existing orders. This would validate a different scenario: A support application must add one new record to an existing Orders table. The proposed change here is Create a SQL view over the current Customers table with its active filter. and its decisive acceptance check is Selecting the view returns current qualifying customers after base records change.

D:

Only the intended item's quantity changes after the transaction commits. This would validate a different scenario: An inventory correction must change Quantity for only item 402 without affecting any other item. The proposed change here is Create a SQL view over the current Customers table with its active filter. and its decisive acceptance check is Selecting the view returns current qualifying customers after base records change.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests

Purchase Individually

  • Premium File

    332 Questions & Answers
    Last Update: Nov 14, 2026

    $76.99
    $69.99
  • Training Course

    32 Lectures

    $43.99
    $39.99
  • Study Guide

    672 Pages

    $43.99
    $39.99

SPECIAL OFFER: GET 10% OFF
This is ONE TIME OFFER

You save
10%

Enter Your Email Address to Receive Your 10% Off Discount Code

SPECIAL OFFER: GET 10% OFF

You save
10%

Use Discount Code:

A confirmation link was sent to your e-mail.

Please check your mailbox for a message from support@examlabs.com and follow the directions.

Download Free Demo of VCE Exam Simulator

Experience Avanset VCE Exam Simulator for yourself.

Simply submit your email address below to get started with our interactive software demo of your free trial.

  • Realistic exam simulation and exam editor with preview functions
  • Whole exam in a single file with several different question types
  • Customizable exam-taking mode & detailed score reports