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 52

Question 510

A data professional makes this decision: Choose an appropriate partition key aligned with common access patterns. Which outcome is the most direct expected result?

  1. Logical partitions distribute records and influence scalability and query efficiency.
  2. The service provides an Azure-managed option compatible with the selected MongoDB driver model.
  3. Expired items are removed according to the TTL policy.
  4. RU/s capacity can adjust within the configured autoscale range.

Explanation

Correct Answer

A:

This is the expected outcome for Cosmos partition key: Logical partitions distribute records and influence scalability and query efficiency.

Incorrect Answers

B:

This result would follow the different MongoDB compatibility decision (Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements.) rather than the specified design.

C:

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.

D:

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

Question 511

A customer-facing document container will grow quickly and needs predictable horizontal data distribution. Someone instead proposes: Consider autoscale throughput for the selected Cosmos DB workload. 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. Choose an appropriate partition key aligned with common access patterns.
  3. Configure Cosmos DB item or container time-to-live where supported.
  4. Consider autoscale throughput for the selected Cosmos DB workload.

Explanation

Correct Answer

B:

This correction addresses Cosmos partition key. Logical partitions distribute records and influence scalability and query efficiency.

Incorrect Answers

A:

This choice is for MongoDB compatibility, not the specific requirement. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

C:

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

D:

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

Question 512

A data architect recommends this approach: Choose an appropriate partition key aligned with common access patterns. Which situation most clearly calls for that approach?

  1. An application's Cosmos DB traffic rises and falls sharply during different hours each day.
  2. Telemetry documents should automatically expire after a configured retention period without a daily cleanup job.
  3. A customer-facing document container will grow quickly and needs predictable horizontal data distribution.
  4. A development team wants an Azure globally distributed database accessed through compatible MongoDB client APIs.

Explanation

Correct Answer

C:

This situation calls for Cosmos partition key. Logical partitions distribute records and influence scalability and query efficiency.

Incorrect Answers

A:

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.

B:

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.

D:

The other situation is better matched to Choose Azure Cosmos DB for MongoDB vCore or the supported MongoDB API offering according to workload requirements. The service provides an Azure-managed option compatible with the selected MongoDB driver model.

Question 513

One partition key value receives almost all requests while other values receive very few. Which data concept, Azure service, or design decision most directly satisfies the requirement?

  1. Use a Cosmos DB point read by item ID and partition key.
  2. Redesign the partitioning or access pattern to avoid a heavily skewed key.
  3. Consume the supported Azure Cosmos DB change feed.
  4. Consider Azure Cosmos DB for Apache Cassandra.

Explanation

Correct Answer

B:

The requirement concerns Hot partition risk. Traffic can spread more evenly across the container's available resources.

Incorrect Answers

A:

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

C:

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

D:

That action instead addresses Cassandra API: A managed Azure option can expose Cassandra-compatible interfaces for supported use cases. It does not directly satisfy the described Hot partition risk need.

Question 514

A data professional makes this decision: Redesign the partitioning or access pattern to avoid a heavily skewed key. Which outcome is the most direct expected result?

  1. Applications can process a stream of document changes incrementally.
  2. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.
  3. Traffic can spread more evenly across the container's available resources.
  4. The targeted lookup can avoid a broad cross-partition query.

Explanation

Correct Answer

C:

This is the expected outcome for Hot partition risk: Traffic can spread more evenly across the container's available resources.

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 Cassandra API decision (Consider Azure Cosmos DB for Apache Cassandra.) rather than the specified design.

D:

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.

Question 515

One partition key value receives almost all requests while other values receive very few. Someone instead proposes: Use a Cosmos DB point read by item ID and partition key. Which alternative is the best correction for the original requirement?

  1. Use a Cosmos DB point read by item ID and partition key.
  2. Consume the supported Azure Cosmos DB change feed.
  3. Consider Azure Cosmos DB for Apache Cassandra.
  4. Redesign the partitioning or access pattern to avoid a heavily skewed key.

Explanation

Correct Answer

D:

This correction addresses Hot partition risk. Traffic can spread more evenly across the container's available resources.

Incorrect Answers

A:

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

B:

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

C:

This choice is for Cassandra API, not the specific requirement. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

Question 516

A data architect recommends this approach: Redesign the partitioning or access pattern to avoid a heavily skewed key. 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. A microservice needs to react when documents are inserted or updated in a Cosmos DB container.
  4. A service knows a document's unique item ID and partition key and needs one exact lookup.

Explanation

Correct Answer

A:

This situation calls for Hot partition risk. Traffic can spread more evenly across the container's available resources.

Incorrect Answers

B:

The other situation is better matched to Consider Azure Cosmos DB for Apache Cassandra. A managed Azure option can expose Cassandra-compatible interfaces for supported use cases.

C:

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

D:

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.

Question 517

A team cannot explain why Cosmos DB operations consume provisioned capacity when reading and writing documents. Which data concept, Azure service, or design decision most directly satisfies the requirement?

  1. Use request units as the standardized measure of database operation cost.
  2. Use the Azure Cosmos DB for NoSQL SQL-like query language.
  3. Use Azure Cosmos DB for Apache Gremlin for the property graph workload.
  4. Organize JSON records as items inside containers grouped within a database and account.

Explanation

Correct Answer

A:

The requirement concerns Request units. Queries and writes consume RU-based throughput according to their work.

Incorrect Answers

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 Request units need.

C:

That action instead addresses Graph traversal: Vertices and edges can represent and traverse connected entities. It does not directly satisfy the described Request units 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 Request units need.

Question 518

A data professional makes this decision: Use request units as the standardized measure of database operation cost. Which outcome is the most direct expected result?

  1. Resource hierarchy separates account settings, database groupings and stored items.
  2. Queries and writes consume RU-based throughput according to their work.
  3. Vertices and edges can represent and traverse connected entities.
  4. Document properties can be filtered and projected with the service's query syntax.

Explanation

Correct Answer

B:

This is the expected outcome for Request units: Queries and writes consume RU-based throughput according to their work.

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.

C:

This result would follow the different Graph traversal decision (Use Azure Cosmos DB for Apache Gremlin for the property graph workload.) rather than the specified design.

D:

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.

Question 519

A team cannot explain why Cosmos DB operations consume provisioned capacity when reading and writing documents. Someone instead proposes: Use the Azure Cosmos DB for NoSQL SQL-like query language. Which alternative is the best correction for the original requirement?

  1. Organize JSON records as items inside containers grouped within a database and account.
  2. Use the Azure Cosmos DB for NoSQL SQL-like query language.
  3. Use request units as the standardized measure of database operation cost.
  4. Use Azure Cosmos DB for Apache Gremlin for the property graph workload.

Explanation

Correct Answer

C:

This correction addresses Request units. Queries and writes consume RU-based throughput according to their work.

Incorrect Answers

A:

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

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.

D:

This choice is for Graph traversal, not the specific requirement. Vertices and edges can represent and traverse connected entities.

Question 520

A data architect recommends this approach: Use request units as the standardized measure of database operation cost. Which situation most clearly calls for that approach?

  1. A social network application frequently follows many-hop relationships among members and groups using graph queries.
  2. A developer confuses Cosmos DB accounts, databases, containers and individual items.
  3. An app needs to filter JSON documents by an indexed property and project selected fields.
  4. A team cannot explain why Cosmos DB operations consume provisioned capacity when reading and writing documents.

Explanation

Correct Answer

D:

This situation calls for Request units. Queries and writes consume RU-based throughput according to their work.

Incorrect Answers

A:

The other situation is better matched to Use Azure Cosmos DB for Apache Gremlin for the property graph workload. Vertices and edges can represent and traverse connected entities.

B:

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.

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.