McAfee-Secured Website

Exam Bundle

Exam Code: DP-900

Exam Name Microsoft Azure Data Fundamentals

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Data Fundamentals

Microsoft DP-900 Bundle $25.00

100% Microsoft DP-900 Guaranteed Success With Testking Training Materials

Get Real DP-900 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    DP-900 Questions & Answers

    332 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual DP-900 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • DP-900 Video Course

    DP-900 Video Course

    32 Video Lectures

    DP-900 Video Course is developed by Microsoft Professionals to help you pass the DP-900 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Data Fundamentals exam.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    332 Questions

    $124.99
  • DP-900 Video Course

    Video Course

    32 Video Lectures

    $39.99

Microsoft DP-900 Practice Test 50

Question 490

A data professional makes this decision: Use Azure Cosmos DB for NoSQL. Which outcome is the most direct expected result?

  1. RU/s capacity can adjust within the configured autoscale range.
  2. Expired items are removed according to the TTL policy.
  3. The service supports an API model compatible with Table-oriented applications.
  4. The service stores queryable JSON-like items within managed scalable containers.

Explanation

Correct Answer

D:

This is the expected outcome for NoSQL document database: The service stores queryable JSON-like items within managed scalable containers.

Incorrect Answers

A:

This result would follow the different Autoscale throughput decision (Consider autoscale throughput for the selected Cosmos DB workload.) rather than the specified design.

B:

This result would follow the different Time to live decision (Configure Cosmos DB item or container time-to-live where supported.) rather than the specified design.

C:

This result would follow the different Table API decision (Evaluate Azure Cosmos DB for Table.) rather than the specified design.

Question 491

An app holds product objects with varying JSON fields and needs a managed globally distributed document service. Someone instead proposes: Evaluate Azure Cosmos DB for Table. Which alternative is the best correction for the original requirement?

  1. Use Azure Cosmos DB for NoSQL.
  2. Configure Cosmos DB item or container time-to-live where supported.
  3. Consider autoscale throughput for the selected Cosmos DB workload.
  4. Evaluate Azure Cosmos DB for Table.

Explanation

Correct Answer

A:

This correction addresses NoSQL document database. The service stores queryable JSON-like items within managed scalable containers.

Incorrect Answers

B:

This choice is for Time to live, not the specific requirement. Expired items are removed according to the TTL policy.

C:

This choice is for Autoscale throughput, not the specific requirement. RU/s capacity can adjust within the configured autoscale range.

D:

This choice is for Table API, not the specific requirement. The service supports an API model compatible with Table-oriented applications.

Question 492

A data architect recommends this approach: Use Azure Cosmos DB for NoSQL. Which situation most clearly calls for that approach?

  1. An application already uses Azure Table Storage-compatible SDK operations but wants additional Cosmos DB capabilities.
  2. An app holds product objects with varying JSON fields and needs a managed globally distributed document service.
  3. An application's Cosmos DB traffic rises and falls sharply during different hours each day.
  4. Telemetry documents should automatically expire after a configured retention period without a daily cleanup job.

Explanation

Correct Answer

B:

This situation calls for NoSQL document database. The service stores queryable JSON-like items within managed scalable containers.

Incorrect Answers

A:

The other situation is better matched to Evaluate Azure Cosmos DB for Table. The service supports an API model compatible with Table-oriented applications.

C:

The other situation is better matched to Consider autoscale throughput for the selected Cosmos DB workload. RU/s capacity can adjust within the configured autoscale range.

D:

The other situation is better matched to Configure Cosmos DB item or container time-to-live where supported. Expired items are removed according to the TTL policy.

Question 493

A development team wants an Azure globally distributed database accessed through compatible MongoDB client APIs. Which data concept, Azure service, or design decision most directly satisfies the requirement?

  1. Consume the supported Azure Cosmos DB change feed.
  2. Choose an appropriate partition key aligned with common access patterns.
  3. Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements.
  4. Use a Cosmos DB point read by item ID and partition key.

Explanation

Correct Answer

C:

The requirement concerns MongoDB compatibility. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Incorrect Answers

A:

That action instead addresses Change feed: Applications can process a stream of document changes incrementally. It does not directly satisfy the described MongoDB compatibility need.

B:

That action instead addresses Cosmos partition key: Logical partitions distribute records and influence scalability and query efficiency. It does not directly satisfy the described MongoDB compatibility need.

D:

That action instead addresses Cosmos point read: The targeted lookup can avoid a broad cross-partition query. It does not directly satisfy the described MongoDB compatibility need.

Question 494

A data professional makes this decision: Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements. Which outcome is the most direct expected result?

  1. Applications can process a stream of document changes incrementally.
  2. The targeted lookup can avoid a broad cross-partition query.
  3. Logical partitions distribute records and influence scalability and query efficiency.
  4. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Explanation

Correct Answer

D:

This is the expected outcome for MongoDB compatibility: The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Incorrect Answers

A:

This result would follow the different Change feed decision (Consume the supported Azure Cosmos DB change feed.) rather than the specified design.

B:

This result would follow the different Cosmos point read decision (Use a Cosmos DB point read by item ID and partition key.) rather than the specified design.

C:

This result would follow the different Cosmos partition key decision (Choose an appropriate partition key aligned with common access patterns.) rather than the specified design.

Question 495

A development team wants an Azure globally distributed database accessed through compatible MongoDB client APIs. Someone instead proposes: Choose an appropriate partition key aligned with common access patterns. Which alternative is the best correction for the original requirement?

  1. Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements.
  2. Use a Cosmos DB point read by item ID and partition key.
  3. Consume the supported Azure Cosmos DB change feed.
  4. Choose an appropriate partition key aligned with common access patterns.

Explanation

Correct Answer

A:

This correction addresses MongoDB compatibility. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Incorrect Answers

B:

This choice is for Cosmos point read, not the specific requirement. The targeted lookup can avoid a broad cross-partition query.

C:

This choice is for Change feed, not the specific requirement. Applications can process a stream of document changes incrementally.

D:

This choice is for Cosmos partition key, not the specific requirement. Logical partitions distribute records and influence scalability and query efficiency.

Question 496

A data architect recommends this approach: Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements. Which situation most clearly calls for that approach?

  1. A customer-facing document container will grow quickly and needs predictable horizontal data distribution.
  2. A development team wants an Azure globally distributed database accessed through compatible MongoDB client APIs.
  3. A service knows a document's unique item ID and partition key and needs one exact lookup.
  4. A microservice needs to react when documents are inserted or updated in a Cosmos DB container.

Explanation

Correct Answer

B:

This situation calls for MongoDB compatibility. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Incorrect Answers

A:

The other situation is better matched to Choose an appropriate partition key aligned with common access patterns. Logical partitions distribute records and influence scalability and query efficiency.

C:

The other situation is better matched to Use a Cosmos DB point read by item ID and partition key. The targeted lookup can avoid a broad cross-partition query.

D:

The other situation is better matched to Consume the supported Azure Cosmos DB change feed. Applications can process a stream of document changes incrementally.

Question 497

An existing application uses Cassandra-style CQL clients and partitioned wide-column data access. Which data concept, Azure service, or design decision most directly satisfies the requirement?

  1. Redesign the partitioning or access pattern to avoid a heavily skewed key.
  2. Use the Azure Cosmos DB for NoSQL SQL-like query language.
  3. Consider Azure Cosmos DB for Apache Cassandra.
  4. Organize JSON records as items inside containers grouped within a database and account.

Explanation

Correct Answer

C:

The requirement concerns Cassandra API. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Incorrect Answers

A:

That action instead addresses Hot partition risk: Traffic can spread more evenly across the container's available resources. It does not directly satisfy the described Cassandra API need.

B:

That action instead addresses Cosmos SQL query: Document properties can be filtered and projected with the service's query syntax. It does not directly satisfy the described Cassandra API need.

D:

That action instead addresses Cosmos item hierarchy: Resource hierarchy separates account settings, database groupings and stored items. It does not directly satisfy the described Cassandra API need.

Question 498

A data professional makes this decision: Consider Azure Cosmos DB for Apache Cassandra. Which outcome is the most direct expected result?

  1. Resource hierarchy separates account settings, database groupings and stored items.
  2. Document properties can be filtered and projected with the service's query syntax.
  3. Traffic can spread more evenly across the container's available resources.
  4. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Explanation

Correct Answer

D:

This is the expected outcome for Cassandra API: A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Incorrect Answers

A:

This result would follow the different Cosmos item hierarchy decision (Organize JSON records as items inside containers grouped within a database and account.) rather than the specified design.

B:

This result would follow the different Cosmos SQL query decision (Use the Azure Cosmos DB for NoSQL SQL-like query language.) rather than the specified design.

C:

This result would follow the different Hot partition risk decision (Redesign the partitioning or access pattern to avoid a heavily skewed key.) rather than the specified design.

Question 499

An existing application uses Cassandra-style CQL clients and partitioned wide-column data access. Someone instead proposes: Redesign the partitioning or access pattern to avoid a heavily skewed key. Which alternative is the best correction for the original requirement?

  1. Consider Azure Cosmos DB for Apache Cassandra.
  2. Use the Azure Cosmos DB for NoSQL SQL-like query language.
  3. Redesign the partitioning or access pattern to avoid a heavily skewed key.
  4. Organize JSON records as items inside containers grouped within a database and account.

Explanation

Correct Answer

A:

This correction addresses Cassandra API. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Incorrect Answers

B:

This choice is for Cosmos SQL query, not the specific requirement. Document properties can be filtered and projected with the service's query syntax.

C:

This choice is for Hot partition risk, not the specific requirement. Traffic can spread more evenly across the container's available resources.

D:

This choice is for Cosmos item hierarchy, not the specific requirement. Resource hierarchy separates account settings, database groupings and stored items.

Question 500

A data architect recommends this approach: Consider Azure Cosmos DB for Apache Cassandra. Which situation most clearly calls for that approach?

  1. One partition key value receives almost all requests while other values receive very few.
  2. An existing application uses Cassandra-style CQL clients and partitioned wide-column data access.
  3. An app needs to filter JSON documents by an indexed property and project selected fields.
  4. A developer confuses Cosmos DB accounts, databases, containers and individual items.

Explanation

Correct Answer

B:

This situation calls for Cassandra API. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Incorrect Answers

A:

The other situation is better matched to Redesign the partitioning or access pattern to avoid a heavily skewed key. Traffic can spread more evenly across the container's available resources.

C:

The other situation is better matched to Use the Azure Cosmos DB for NoSQL SQL-like query language. Document properties can be filtered and projected with the service's query syntax.

D:

The other situation is better matched to Organize JSON records as items inside containers grouped within a database and account. Resource hierarchy separates account settings, database groupings and stored items.