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 22

Question 210

A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. A team proposes: Use an Azure Files SMB file share with appropriate client access. Which observation would BEST demonstrate that this exact requirement was met?

  1. The client mounts the share over NFS and accesses its required directory tree.
  2. Both permitted VMs can mount and read the same directory via SMB.
  3. The archived object remains online for authorized retrieval with the expected tier cost trade-off.
  4. A client retrieves the correct image through its blob identifier and authorized access path.

Explanation

Correct Answer

B:

Both permitted VMs can mount and read the same directory via SMB. Azure Files supplies managed network file shares with SMB support. It is tied to this case: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs.

Incorrect Answers

A:

The client mounts the share over NFS and accesses its required directory tree. This would validate a different scenario: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. The proposed change here is Use an Azure Files SMB file share with appropriate client access. and its decisive acceptance check is Both permitted VMs can mount and read the same directory via SMB.

C:

The archived object remains online for authorized retrieval with the expected tier cost trade-off. This would validate a different scenario: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The proposed change here is Use an Azure Files SMB file share with appropriate client access. and its decisive acceptance check is Both permitted VMs can mount and read the same directory via SMB.

D:

A client retrieves the correct image through its blob identifier and authorized access path. This would validate a different scenario: A media website must store millions of JPEG images and deliver individual objects over HTTPS. The proposed change here is Use an Azure Files SMB file share with appropriate client access. and its decisive acceptance check is Both permitted VMs can mount and read the same directory via SMB.

Question 211

During an architecture review, the team proposes: Use an Azure Files SMB file share with appropriate client access. The requirement is: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. Which technical explanation BEST justifies this specific recommendation?

  1. Azure Files can provide NFS file shares for appropriate Linux scenarios.
  2. Azure Blob online tiers trade storage price against access charges and minimum retention.
  3. Azure Files supplies managed network file shares with SMB support.
  4. Azure Blob Storage is an object store for unstructured data such as images and documents.

Explanation

Correct Answer

C:

Azure Files supplies managed network file shares with SMB support. Evidence would be: Both permitted VMs can mount and read the same directory via SMB. The choice avoids this risk: Blob object URLs do not satisfy an existing application's SMB mount requirement.

Incorrect Answers

A:

Azure Files can provide NFS file shares for appropriate Linux scenarios. That principle applies to the separate requirement: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. It may be true in that setting, but does not specifically explain why Use an Azure Files SMB file share with appropriate client access. is the best fit here. The relevant reason is Azure Files supplies managed network file shares with SMB support.

B:

Azure Blob online tiers trade storage price against access charges and minimum retention. That principle applies to the separate requirement: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. It may be true in that setting, but does not specifically explain why Use an Azure Files SMB file share with appropriate client access. is the best fit here. The relevant reason is Azure Files supplies managed network file shares with SMB support.

D:

Azure Blob Storage is an object store for unstructured data such as images and documents. That principle applies to the separate requirement: A media website must store millions of JPEG images and deliver individual objects over HTTPS. It may be true in that setting, but does not specifically explain why Use an Azure Files SMB file share with appropriate client access. is the best fit here. The relevant reason is Azure Files supplies managed network file shares with SMB support.

Question 212

A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. If the team ignores the targeted approach (Use an Azure Files SMB file share with appropriate client access.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. An SMB-only share is not the NFS mount specified by the application.
  2. Choosing the offline Blob archive tier would require rehydration before ordinary access.
  3. Choosing a relational row for each large binary can complicate scalable object retrieval.
  4. Blob object URLs do not satisfy an existing application's SMB mount requirement.

Explanation

Correct Answer

D:

Blob object URLs do not satisfy an existing application's SMB mount requirement. This risk follows from the exact scenario: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. The reason is azure Files supplies managed network file shares with SMB support. The direct mitigation is: Use an Azure Files SMB file share with appropriate client access.

Incorrect Answers

A:

An SMB-only share is not the NFS mount specified by the application. This is a real potential problem in a different scenario: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. The present case instead concerns A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. With the targeted action omitted, the direct exposure is Blob object URLs do not satisfy an existing application's SMB mount requirement.

B:

Choosing the offline Blob archive tier would require rehydration before ordinary access. This is a real potential problem in a different scenario: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The present case instead concerns A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. With the targeted action omitted, the direct exposure is Blob object URLs do not satisfy an existing application's SMB mount requirement.

C:

Choosing a relational row for each large binary can complicate scalable object retrieval. This is a real potential problem in a different scenario: A media website must store millions of JPEG images and deliver individual objects over HTTPS. The present case instead concerns A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. With the targeted action omitted, the direct exposure is Blob object URLs do not satisfy an existing application's SMB mount requirement.

Question 213

A lightweight application stores sparse sensor settings keyed by region and sensor identifier. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Use an Azure Files SMB file share with appropriate client access.
  2. Use Azure Table Storage entities with PartitionKey and RowKey.
  3. Use a supported Azure Files NFS share for the Linux clients.
  4. Evaluate the archive Blob access tier and plan rehydration before reads.

Explanation

Correct Answer

B:

Use Azure Table Storage entities with PartitionKey and RowKey. This directly addresses the case: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. The deciding technical reason is that azure Table Storage offers a schemaless key/attribute entity model. Verify the solution by checking: The application retrieves a sensor setting using its partition and row key despite variable attributes.

Incorrect Answers

A:

Use an Azure Files SMB file share with appropriate client access. This is a legitimate approach for a different problem: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. Azure Files supplies managed network file shares with SMB support. It does not directly satisfy the present constraint: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. The needed outcome is: The application retrieves a sensor setting using its partition and row key despite variable attributes.

C:

Use a supported Azure Files NFS share for the Linux clients. This is a legitimate approach for a different problem: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. Azure Files can provide NFS file shares for appropriate Linux scenarios. It does not directly satisfy the present constraint: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. The needed outcome is: The application retrieves a sensor setting using its partition and row key despite variable attributes.

D:

Evaluate the archive Blob access tier and plan rehydration before reads. This is a legitimate approach for a different problem: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. Blob archive access trades low storage cost for retrieval latency and operational constraints. It does not directly satisfy the present constraint: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. The needed outcome is: The application retrieves a sensor setting using its partition and row key despite variable attributes.

Question 214

A lightweight application stores sparse sensor settings keyed by region and sensor identifier. A team proposes: Use Azure Table Storage entities with PartitionKey and RowKey. Which observation would BEST demonstrate that this exact requirement was met?

  1. Both permitted VMs can mount and read the same directory via SMB.
  2. The client mounts the share over NFS and accesses its required directory tree.
  3. The application retrieves a sensor setting using its partition and row key despite variable attributes.
  4. The stored blob is preserved at archival cost and is readable after supported rehydration.

Explanation

Correct Answer

C:

The application retrieves a sensor setting using its partition and row key despite variable attributes. Azure Table Storage offers a schemaless key/attribute entity model. It is tied to this case: A lightweight application stores sparse sensor settings keyed by region and sensor identifier.

Incorrect Answers

A:

Both permitted VMs can mount and read the same directory via SMB. This would validate a different scenario: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. The proposed change here is Use Azure Table Storage entities with PartitionKey and RowKey. and its decisive acceptance check is The application retrieves a sensor setting using its partition and row key despite variable attributes.

B:

The client mounts the share over NFS and accesses its required directory tree. This would validate a different scenario: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. The proposed change here is Use Azure Table Storage entities with PartitionKey and RowKey. and its decisive acceptance check is The application retrieves a sensor setting using its partition and row key despite variable attributes.

D:

The stored blob is preserved at archival cost and is readable after supported rehydration. This would validate a different scenario: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. The proposed change here is Use Azure Table Storage entities with PartitionKey and RowKey. and its decisive acceptance check is The application retrieves a sensor setting using its partition and row key despite variable attributes.

Question 215

During an architecture review, the team proposes: Use Azure Table Storage entities with PartitionKey and RowKey. The requirement is: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. Which technical explanation BEST justifies this specific recommendation?

  1. Azure Files supplies managed network file shares with SMB support.
  2. Azure Files can provide NFS file shares for appropriate Linux scenarios.
  3. Blob archive access trades low storage cost for retrieval latency and operational constraints.
  4. Azure Table Storage offers a schemaless key/attribute entity model.

Explanation

Correct Answer

D:

Azure Table Storage offers a schemaless key/attribute entity model. Evidence would be: The application retrieves a sensor setting using its partition and row key despite variable attributes. The choice avoids this risk: Treating the table as a SQL table with foreign keys assumes unsupported relational constraints.

Incorrect Answers

A:

Azure Files supplies managed network file shares with SMB support. That principle applies to the separate requirement: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. It may be true in that setting, but does not specifically explain why Use Azure Table Storage entities with PartitionKey and RowKey. is the best fit here. The relevant reason is Azure Table Storage offers a schemaless key/attribute entity model.

B:

Azure Files can provide NFS file shares for appropriate Linux scenarios. That principle applies to the separate requirement: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. It may be true in that setting, but does not specifically explain why Use Azure Table Storage entities with PartitionKey and RowKey. is the best fit here. The relevant reason is Azure Table Storage offers a schemaless key/attribute entity model.

C:

Blob archive access trades low storage cost for retrieval latency and operational constraints. That principle applies to the separate requirement: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. It may be true in that setting, but does not specifically explain why Use Azure Table Storage entities with PartitionKey and RowKey. is the best fit here. The relevant reason is Azure Table Storage offers a schemaless key/attribute entity model.

Question 216

A lightweight application stores sparse sensor settings keyed by region and sensor identifier. If the team ignores the targeted approach (Use Azure Table Storage entities with PartitionKey and RowKey.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. Treating the table as a SQL table with foreign keys assumes unsupported relational constraints.
  2. Blob object URLs do not satisfy an existing application's SMB mount requirement.
  3. An SMB-only share is not the NFS mount specified by the application.
  4. Treating the archive tier as an immediately readable online tier can delay retrieval unexpectedly.

Explanation

Correct Answer

A:

Treating the table as a SQL table with foreign keys assumes unsupported relational constraints. This risk follows from the exact scenario: A lightweight application stores sparse sensor settings keyed by region and sensor identifier. The reason is azure Table Storage offers a schemaless key/attribute entity model. The direct mitigation is: Use Azure Table Storage entities with PartitionKey and RowKey.

Incorrect Answers

B:

Blob object URLs do not satisfy an existing application's SMB mount requirement. This is a real potential problem in a different scenario: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. The present case instead concerns A lightweight application stores sparse sensor settings keyed by region and sensor identifier. With the targeted action omitted, the direct exposure is Treating the table as a SQL table with foreign keys assumes unsupported relational constraints.

C:

An SMB-only share is not the NFS mount specified by the application. This is a real potential problem in a different scenario: A Linux scientific application requires a mounted NFS network share rather than REST blob operations. The present case instead concerns A lightweight application stores sparse sensor settings keyed by region and sensor identifier. With the targeted action omitted, the direct exposure is Treating the table as a SQL table with foreign keys assumes unsupported relational constraints.

D:

Treating the archive tier as an immediately readable online tier can delay retrieval unexpectedly. This is a real potential problem in a different scenario: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. The present case instead concerns A lightweight application stores sparse sensor settings keyed by region and sensor identifier. With the targeted action omitted, the direct exposure is Treating the table as a SQL table with foreign keys assumes unsupported relational constraints.

Question 217

A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. Which solution or configuration choice MOST directly satisfies the stated requirement without changing unrelated behavior?

  1. Evaluate the archive Blob access tier and plan rehydration before reads.
  2. Use an Azure Files SMB file share with appropriate client access.
  3. Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention.
  4. Store entities with tenant-partition keys and explicit RowKeys rather than a mandatory global SQL schema.

Explanation

Correct Answer

C:

Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. This directly addresses the case: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The deciding technical reason is that azure Blob online tiers trade storage price against access charges and minimum retention. Verify the solution by checking: The archived object remains online for authorized retrieval with the expected tier cost trade-off.

Incorrect Answers

A:

Evaluate the archive Blob access tier and plan rehydration before reads. This is a legitimate approach for a different problem: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. Blob archive access trades low storage cost for retrieval latency and operational constraints. It does not directly satisfy the present constraint: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The needed outcome is: The archived object remains online for authorized retrieval with the expected tier cost trade-off.

B:

Use an Azure Files SMB file share with appropriate client access. This is a legitimate approach for a different problem: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. Azure Files supplies managed network file shares with SMB support. It does not directly satisfy the present constraint: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The needed outcome is: The archived object remains online for authorized retrieval with the expected tier cost trade-off.

D:

Store entities with tenant-partition keys and explicit RowKeys rather than a mandatory global SQL schema. This is a legitimate approach for a different problem: A business records customer preferences in Azure Table Storage, and each tenant has a distinct set of optional properties. Table Storage entities can vary in properties while retaining PartitionKey and RowKey. It does not directly satisfy the present constraint: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The needed outcome is: The archived object remains online for authorized retrieval with the expected tier cost trade-off.

Question 218

A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. A team proposes: Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. Which observation would BEST demonstrate that this exact requirement was met?

  1. The stored blob is preserved at archival cost and is readable after supported rehydration.
  2. Both permitted VMs can mount and read the same directory via SMB.
  3. Two records with different optional property sets can coexist and be retrieved by their keys.
  4. The archived object remains online for authorized retrieval with the expected tier cost trade-off.

Explanation

Correct Answer

D:

The archived object remains online for authorized retrieval with the expected tier cost trade-off. Azure Blob online tiers trade storage price against access charges and minimum retention. It is tied to this case: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process.

Incorrect Answers

A:

The stored blob is preserved at archival cost and is readable after supported rehydration. This would validate a different scenario: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. The proposed change here is Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. and its decisive acceptance check is The archived object remains online for authorized retrieval with the expected tier cost trade-off.

B:

Both permitted VMs can mount and read the same directory via SMB. This would validate a different scenario: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. The proposed change here is Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. and its decisive acceptance check is The archived object remains online for authorized retrieval with the expected tier cost trade-off.

C:

Two records with different optional property sets can coexist and be retrieved by their keys. This would validate a different scenario: A business records customer preferences in Azure Table Storage, and each tenant has a distinct set of optional properties. The proposed change here is Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. and its decisive acceptance check is The archived object remains online for authorized retrieval with the expected tier cost trade-off.

Question 219

During an architecture review, the team proposes: Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. The requirement is: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. Which technical explanation BEST justifies this specific recommendation?

  1. Azure Blob online tiers trade storage price against access charges and minimum retention.
  2. Blob archive access trades low storage cost for retrieval latency and operational constraints.
  3. Azure Files supplies managed network file shares with SMB support.
  4. Table Storage entities can vary in properties while retaining PartitionKey and RowKey.

Explanation

Correct Answer

A:

Azure Blob online tiers trade storage price against access charges and minimum retention. Evidence would be: The archived object remains online for authorized retrieval with the expected tier cost trade-off. The choice avoids this risk: Choosing the offline Blob archive tier would require rehydration before ordinary access.

Incorrect Answers

B:

Blob archive access trades low storage cost for retrieval latency and operational constraints. That principle applies to the separate requirement: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. It may be true in that setting, but does not specifically explain why Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. is the best fit here. The relevant reason is Azure Blob online tiers trade storage price against access charges and minimum retention.

C:

Azure Files supplies managed network file shares with SMB support. That principle applies to the separate requirement: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. It may be true in that setting, but does not specifically explain why Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. is the best fit here. The relevant reason is Azure Blob online tiers trade storage price against access charges and minimum retention.

D:

Table Storage entities can vary in properties while retaining PartitionKey and RowKey. That principle applies to the separate requirement: A business records customer preferences in Azure Table Storage, and each tenant has a distinct set of optional properties. It may be true in that setting, but does not specifically explain why Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention. is the best fit here. The relevant reason is Azure Blob online tiers trade storage price against access charges and minimum retention.

Question 220

A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. If the team ignores the targeted approach (Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention.), which consequence or limitation MOST directly follows from leaving that requirement unaddressed?

  1. Treating the archive tier as an immediately readable online tier can delay retrieval unexpectedly.
  2. Choosing the offline Blob archive tier would require rehydration before ordinary access.
  3. Blob object URLs do not satisfy an existing application's SMB mount requirement.
  4. Assuming every entity requires identical columns contradicts the schemaless table model.

Explanation

Correct Answer

B:

Choosing the offline Blob archive tier would require rehydration before ordinary access. This risk follows from the exact scenario: A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. The reason is azure Blob online tiers trade storage price against access charges and minimum retention. The direct mitigation is: Select a suitable online infrequent-access Blob tier such as cool or cold based on usage and retention.

Incorrect Answers

A:

Treating the archive tier as an immediately readable online tier can delay retrieval unexpectedly. This is a real potential problem in a different scenario: A video platform needs cheaper long-term storage for files not accessed for months and accepts delayed retrieval. The present case instead concerns A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. With the targeted action omitted, the direct exposure is Choosing the offline Blob archive tier would require rehydration before ordinary access.

C:

Blob object URLs do not satisfy an existing application's SMB mount requirement. This is a real potential problem in a different scenario: A Windows-based line-of-business application requires a shared directory mounted by SMB from Azure VMs. The present case instead concerns A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. With the targeted action omitted, the direct exposure is Choosing the offline Blob archive tier would require rehydration before ordinary access.

D:

Assuming every entity requires identical columns contradicts the schemaless table model. This is a real potential problem in a different scenario: A business records customer preferences in Azure Table Storage, and each tenant has a distinct set of optional properties. The present case instead concerns A backup archive contains objects rarely read but they must be retrieved without the separate archive rehydration process. With the targeted action omitted, the direct exposure is Choosing the offline Blob archive tier would require rehydration before ordinary access.

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