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 1

Question 1

A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Represent the payroll extract as structured rows and typed columns.
  2. Classify the originals as unstructured binary content and retain metadata separately.
  3. Classify the request log as semi-structured data and preserve its nested key hierarchy.
  4. Use the existing relational table structure for repeated order-to-product lookups.

Explanation

Correct Answer

A:

Represent the payroll extract as structured rows and typed columns. This directly addresses the case: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The deciding technical reason is that structured data has a predefined schema with consistent field types. Verify the solution by checking: The schema validates each record and SQL can filter Salary as a numeric field.

Incorrect Answers

B:

Classify the originals as unstructured binary content and retain metadata separately. This is a legitimate approach for a different problem: A legal department archives scanned contract images and audio depositions without searchable data columns. Unstructured files do not naturally follow a fixed row-and-column schema. It does not directly satisfy the present constraint: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The needed outcome is: The schema validates each record and SQL can filter Salary as a numeric field.

C:

Classify the request log as semi-structured data and preserve its nested key hierarchy. This is a legitimate approach for a different problem: An application exports newline-delimited JSON records for each API request including a variable nested context object. JSON supports hierarchical objects and optional fields under a semi-structured model. It does not directly satisfy the present constraint: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The needed outcome is: The schema validates each record and SQL can filter Salary as a numeric field.

D:

Use the existing relational table structure for repeated order-to-product lookups. This is a legitimate approach for a different problem: An invoice database has a Products table and a separate Orders table linked by product identifiers. Related relational tables preserve entities and associations through shared keys. It does not directly satisfy the present constraint: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The needed outcome is: The schema validates each record and SQL can filter Salary as a numeric field.

Question 2

A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. A team proposes: Represent the payroll extract as structured rows and typed columns. Which observation would BEST demonstrate that this exact requirement was met?

  1. The original image and audio bytes remain accessible even though their contents are not relational rows.
  2. The schema validates each record and SQL can filter Salary as a numeric field.
  3. An ingest job parses optional nested properties while retaining each complete JSON event.
  4. A join retrieves each order with its related product without duplicating every product description.

Explanation

Correct Answer

B:

The schema validates each record and SQL can filter Salary as a numeric field. Structured data has a predefined schema with consistent field types. It is tied to this case: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row.

Incorrect Answers

A:

The original image and audio bytes remain accessible even though their contents are not relational rows. This would validate a different scenario: A legal department archives scanned contract images and audio depositions without searchable data columns. The proposed change here is Represent the payroll extract as structured rows and typed columns. and its decisive acceptance check is The schema validates each record and SQL can filter Salary as a numeric field.

C:

An ingest job parses optional nested properties while retaining each complete JSON event. This would validate a different scenario: An application exports newline-delimited JSON records for each API request including a variable nested context object. The proposed change here is Represent the payroll extract as structured rows and typed columns. and its decisive acceptance check is The schema validates each record and SQL can filter Salary as a numeric field.

D:

A join retrieves each order with its related product without duplicating every product description. This would validate a different scenario: An invoice database has a Products table and a separate Orders table linked by product identifiers. The proposed change here is Represent the payroll extract as structured rows and typed columns. and its decisive acceptance check is The schema validates each record and SQL can filter Salary as a numeric field.

Question 3

During an architecture review, the team proposes: Represent the payroll extract as structured rows and typed columns. The requirement is: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. Which technical explanation BEST justifies this specific recommendation?

  1. Unstructured files do not naturally follow a fixed row-and-column schema.
  2. JSON supports hierarchical objects and optional fields under a semi-structured model.
  3. Structured data has a predefined schema with consistent field types.
  4. Related relational tables preserve entities and associations through shared keys.

Explanation

Correct Answer

C:

Structured data has a predefined schema with consistent field types. Evidence would be: The schema validates each record and SQL can filter Salary as a numeric field. The choice avoids this risk: Treating typed columns as free-form text loses reliable validation and comparisons.

Incorrect Answers

A:

Unstructured files do not naturally follow a fixed row-and-column schema. That principle applies to the separate requirement: A legal department archives scanned contract images and audio depositions without searchable data columns. It may be true in that setting, but does not specifically explain why Represent the payroll extract as structured rows and typed columns. is the best fit here. The relevant reason is Structured data has a predefined schema with consistent field types.

B:

JSON supports hierarchical objects and optional fields under a semi-structured model. That principle applies to the separate requirement: An application exports newline-delimited JSON records for each API request including a variable nested context object. It may be true in that setting, but does not specifically explain why Represent the payroll extract as structured rows and typed columns. is the best fit here. The relevant reason is Structured data has a predefined schema with consistent field types.

D:

Related relational tables preserve entities and associations through shared keys. That principle applies to the separate requirement: An invoice database has a Products table and a separate Orders table linked by product identifiers. It may be true in that setting, but does not specifically explain why Represent the payroll extract as structured rows and typed columns. is the best fit here. The relevant reason is Structured data has a predefined schema with consistent field types.

Question 4

A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. If the team ignores the targeted approach (Represent the payroll extract as structured rows and typed columns.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. Trying to impose simple numeric columns on raw media does not preserve its content.
  2. Flattening every event into one mandatory column list risks losing nested context.
  3. Copying complete product details into each order can introduce update anomalies.
  4. Treating typed columns as free-form text loses reliable validation and comparisons.

Explanation

Correct Answer

D:

Treating typed columns as free-form text loses reliable validation and comparisons. This risk follows from the exact scenario: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The reason is structured data has a predefined schema with consistent field types. The direct mitigation is: Represent the payroll extract as structured rows and typed columns.

Incorrect Answers

A:

Trying to impose simple numeric columns on raw media does not preserve its content. This is a real potential problem in a different scenario: A legal department archives scanned contract images and audio depositions without searchable data columns. The present case instead concerns A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. With the targeted action omitted, the direct exposure is Treating typed columns as free-form text loses reliable validation and comparisons.

B:

Flattening every event into one mandatory column list risks losing nested context. This is a real potential problem in a different scenario: An application exports newline-delimited JSON records for each API request including a variable nested context object. The present case instead concerns A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. With the targeted action omitted, the direct exposure is Treating typed columns as free-form text loses reliable validation and comparisons.

C:

Copying complete product details into each order can introduce update anomalies. This is a real potential problem in a different scenario: An invoice database has a Products table and a separate Orders table linked by product identifiers. The present case instead concerns A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. With the targeted action omitted, the direct exposure is Treating typed columns as free-form text loses reliable validation and comparisons.

Question 5

A device uploads JSON telemetry in which some events include an optional batteryLevel property. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Recognize the feed as semi-structured records with tags describing each field.
  2. Treat each event as semi-structured JSON with optional fields.
  3. Represent the payroll extract as structured rows and typed columns.
  4. Handle the messages as unstructured text requiring extraction before tabular analysis.

Explanation

Correct Answer

B:

Treat each event as semi-structured JSON with optional fields. This directly addresses the case: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The deciding technical reason is that semi-structured data has recognizable tags or keys but does not require one fixed column schema. Verify the solution by checking: Two valid events with different property sets can be ingested without fabricating empty fixed columns.

Incorrect Answers

A:

Recognize the feed as semi-structured records with tags describing each field. This is a legitimate approach for a different problem: A product feed uses XML tags to describe different attributes for clothing and electronics. XML elements provide an explicit structure even when records differ in shape. It does not directly satisfy the present constraint: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The needed outcome is: Two valid events with different property sets can be ingested without fabricating empty fixed columns.

C:

Represent the payroll extract as structured rows and typed columns. This is a legitimate approach for a different problem: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. Structured data has a predefined schema with consistent field types. It does not directly satisfy the present constraint: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The needed outcome is: Two valid events with different property sets can be ingested without fabricating empty fixed columns.

D:

Handle the messages as unstructured text requiring extraction before tabular analysis. This is a legitimate approach for a different problem: A marketing team receives plain-text customer emails with no standardized key-value delimiters. Unstructured natural language must be processed to derive consistent analyzable fields. It does not directly satisfy the present constraint: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The needed outcome is: Two valid events with different property sets can be ingested without fabricating empty fixed columns.

Question 6

A device uploads JSON telemetry in which some events include an optional batteryLevel property. A team proposes: Treat each event as semi-structured JSON with optional fields. Which observation would BEST demonstrate that this exact requirement was met?

  1. The parser reads category-dependent tags without requiring identical elements in every product.
  2. The schema validates each record and SQL can filter Salary as a numeric field.
  3. Two valid events with different property sets can be ingested without fabricating empty fixed columns.
  4. A text-processing step extracts usable concepts without pretending every email is a fixed SQL row.

Explanation

Correct Answer

C:

Two valid events with different property sets can be ingested without fabricating empty fixed columns. Semi-structured data has recognizable tags or keys but does not require one fixed column schema. It is tied to this case: A device uploads JSON telemetry in which some events include an optional batteryLevel property.

Incorrect Answers

A:

The parser reads category-dependent tags without requiring identical elements in every product. This would validate a different scenario: A product feed uses XML tags to describe different attributes for clothing and electronics. The proposed change here is Treat each event as semi-structured JSON with optional fields. and its decisive acceptance check is Two valid events with different property sets can be ingested without fabricating empty fixed columns.

B:

The schema validates each record and SQL can filter Salary as a numeric field. This would validate a different scenario: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The proposed change here is Treat each event as semi-structured JSON with optional fields. and its decisive acceptance check is Two valid events with different property sets can be ingested without fabricating empty fixed columns.

D:

A text-processing step extracts usable concepts without pretending every email is a fixed SQL row. This would validate a different scenario: A marketing team receives plain-text customer emails with no standardized key-value delimiters. The proposed change here is Treat each event as semi-structured JSON with optional fields. and its decisive acceptance check is Two valid events with different property sets can be ingested without fabricating empty fixed columns.

Question 7

During an architecture review, the team proposes: Treat each event as semi-structured JSON with optional fields. The requirement is: A device uploads JSON telemetry in which some events include an optional batteryLevel property. Which technical explanation BEST justifies this specific recommendation?

  1. XML elements provide an explicit structure even when records differ in shape.
  2. Structured data has a predefined schema with consistent field types.
  3. Unstructured natural language must be processed to derive consistent analyzable fields.
  4. Semi-structured data has recognizable tags or keys but does not require one fixed column schema.

Explanation

Correct Answer

D:

Semi-structured data has recognizable tags or keys but does not require one fixed column schema. Evidence would be: Two valid events with different property sets can be ingested without fabricating empty fixed columns. The choice avoids this risk: A rigid identical-column assumption can reject legitimate event variants.

Incorrect Answers

A:

XML elements provide an explicit structure even when records differ in shape. That principle applies to the separate requirement: A product feed uses XML tags to describe different attributes for clothing and electronics. It may be true in that setting, but does not specifically explain why Treat each event as semi-structured JSON with optional fields. is the best fit here. The relevant reason is Semi-structured data has recognizable tags or keys but does not require one fixed column schema.

B:

Structured data has a predefined schema with consistent field types. That principle applies to the separate requirement: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. It may be true in that setting, but does not specifically explain why Treat each event as semi-structured JSON with optional fields. is the best fit here. The relevant reason is Semi-structured data has recognizable tags or keys but does not require one fixed column schema.

C:

Unstructured natural language must be processed to derive consistent analyzable fields. That principle applies to the separate requirement: A marketing team receives plain-text customer emails with no standardized key-value delimiters. It may be true in that setting, but does not specifically explain why Treat each event as semi-structured JSON with optional fields. is the best fit here. The relevant reason is Semi-structured data has recognizable tags or keys but does not require one fixed column schema.

Question 8

A device uploads JSON telemetry in which some events include an optional batteryLevel property. If the team ignores the targeted approach (Treat each event as semi-structured JSON with optional fields.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. A rigid identical-column assumption can reject legitimate event variants.
  2. Assuming fixed relational fields can discard category-specific attributes.
  3. Treating typed columns as free-form text loses reliable validation and comparisons.
  4. Directly casting arbitrary prose to mandatory typed columns causes malformed records.

Explanation

Correct Answer

A:

A rigid identical-column assumption can reject legitimate event variants. This risk follows from the exact scenario: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The reason is semi-structured data has recognizable tags or keys but does not require one fixed column schema. The direct mitigation is: Treat each event as semi-structured JSON with optional fields.

Incorrect Answers

B:

Assuming fixed relational fields can discard category-specific attributes. This is a real potential problem in a different scenario: A product feed uses XML tags to describe different attributes for clothing and electronics. The present case instead concerns A device uploads JSON telemetry in which some events include an optional batteryLevel property. With the targeted action omitted, the direct exposure is A rigid identical-column assumption can reject legitimate event variants.

C:

Treating typed columns as free-form text loses reliable validation and comparisons. This is a real potential problem in a different scenario: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The present case instead concerns A device uploads JSON telemetry in which some events include an optional batteryLevel property. With the targeted action omitted, the direct exposure is A rigid identical-column assumption can reject legitimate event variants.

D:

Directly casting arbitrary prose to mandatory typed columns causes malformed records. This is a real potential problem in a different scenario: A marketing team receives plain-text customer emails with no standardized key-value delimiters. The present case instead concerns A device uploads JSON telemetry in which some events include an optional batteryLevel property. With the targeted action omitted, the direct exposure is A rigid identical-column assumption can reject legitimate event variants.

Question 9

A legal department archives scanned contract images and audio depositions without searchable data columns. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Represent the payroll extract as structured rows and typed columns.
  2. Treat each event as semi-structured JSON with optional fields.
  3. Classify the originals as unstructured binary content and retain metadata separately.
  4. Use the existing relational table structure for repeated order-to-product lookups.

Explanation

Correct Answer

C:

Classify the originals as unstructured binary content and retain metadata separately. This directly addresses the case: A legal department archives scanned contract images and audio depositions without searchable data columns. The deciding technical reason is that unstructured files do not naturally follow a fixed row-and-column schema. Verify the solution by checking: The original image and audio bytes remain accessible even though their contents are not relational rows.

Incorrect Answers

A:

Represent the payroll extract as structured rows and typed columns. This is a legitimate approach for a different problem: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. Structured data has a predefined schema with consistent field types. It does not directly satisfy the present constraint: A legal department archives scanned contract images and audio depositions without searchable data columns. The needed outcome is: The original image and audio bytes remain accessible even though their contents are not relational rows.

B:

Treat each event as semi-structured JSON with optional fields. This is a legitimate approach for a different problem: A device uploads JSON telemetry in which some events include an optional batteryLevel property. Semi-structured data has recognizable tags or keys but does not require one fixed column schema. It does not directly satisfy the present constraint: A legal department archives scanned contract images and audio depositions without searchable data columns. The needed outcome is: The original image and audio bytes remain accessible even though their contents are not relational rows.

D:

Use the existing relational table structure for repeated order-to-product lookups. This is a legitimate approach for a different problem: An invoice database has a Products table and a separate Orders table linked by product identifiers. Related relational tables preserve entities and associations through shared keys. It does not directly satisfy the present constraint: A legal department archives scanned contract images and audio depositions without searchable data columns. The needed outcome is: The original image and audio bytes remain accessible even though their contents are not relational rows.

Question 10

A legal department archives scanned contract images and audio depositions without searchable data columns. A team proposes: Classify the originals as unstructured binary content and retain metadata separately. Which observation would BEST demonstrate that this exact requirement was met?

  1. The schema validates each record and SQL can filter Salary as a numeric field.
  2. Two valid events with different property sets can be ingested without fabricating empty fixed columns.
  3. A join retrieves each order with its related product without duplicating every product description.
  4. The original image and audio bytes remain accessible even though their contents are not relational rows.

Explanation

Correct Answer

D:

The original image and audio bytes remain accessible even though their contents are not relational rows. Unstructured files do not naturally follow a fixed row-and-column schema. It is tied to this case: A legal department archives scanned contract images and audio depositions without searchable data columns.

Incorrect Answers

A:

The schema validates each record and SQL can filter Salary as a numeric field. This would validate a different scenario: A payroll import contains fixed columns EmployeeId, Department, and Salary with a predictable type for every row. The proposed change here is Classify the originals as unstructured binary content and retain metadata separately. and its decisive acceptance check is The original image and audio bytes remain accessible even though their contents are not relational rows.

B:

Two valid events with different property sets can be ingested without fabricating empty fixed columns. This would validate a different scenario: A device uploads JSON telemetry in which some events include an optional batteryLevel property. The proposed change here is Classify the originals as unstructured binary content and retain metadata separately. and its decisive acceptance check is The original image and audio bytes remain accessible even though their contents are not relational rows.

C:

A join retrieves each order with its related product without duplicating every product description. This would validate a different scenario: An invoice database has a Products table and a separate Orders table linked by product identifiers. The proposed change here is Classify the originals as unstructured binary content and retain metadata separately. and its decisive acceptance check is The original image and audio bytes remain accessible even though their contents are not relational rows.

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