Practice Exams:

Microsoft DP-900 Dumps

EXAM: Microsoft Azure Data Fundamentals
Verified By Experts
Premium Bundle
$40.00
$59.97 $99.97

DP-900 Premium Bundle


  • Premium File 332 Questions & Answers
  • Training Course 32 Lectures
  • Study Guide 672 Pages

Microsoft DP-900 Practice Test 67

Question 660

At Meadowfield Games user profiles are read by unique player ID under heavy load. Which shortcut most directly threatens the intended data outcome?

  1. Use the same fixed partition value for all high-volume users to simplify code.
  2. Assume every normal blob prefix has exactly the same atomic directory operations as a hierarchical namespace.
  3. Rename the database endpoint without evaluating driver and operator support.
  4. Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API.

Answer & Explanations

Correct answer: A

A.

Use the same fixed partition value for all high-volume users to simplify code. The scenario is: At Meadowfield Games user profiles are read by unique player ID under heavy load. This undermines the mechanism: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. Instead: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

B.

Assume every normal blob prefix has exactly the same atomic directory operations as a hierarchical namespace. This concerns another issue: At Oakridge Analytics Spark jobs work with folder-based lake partitions. In the stated case—At Meadowfield Games user profiles are read by unique player ID under heavy load—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

C.

Rename the database endpoint without evaluating driver and operator support. This concerns another issue: At Harborpoint Software an existing document app uses MongoDB clients. In the stated case—At Meadowfield Games user profiles are read by unique player ID under heavy load—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

D.

Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. This concerns another issue: At Cedarfield Apps developers build a new JSON-first profile service. In the stated case—At Meadowfield Games user profiles are read by unique player ID under heavy load—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

Question 661

At Westlake Commerce multi-tenant carts require scalable tenant-key access. Which design or Azure data approach best fits this requirement?

  1. Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors.
  2. Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.
  3. Apply least-privilege Azure RBAC and data-plane permissions to private storage containers.
  4. Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics.

Answer & Explanations

Correct answer: B

A.

Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors. This addresses a different situation: At Harborpoint Software an existing document app uses MongoDB clients. The present case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The relevant action here is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

B.

Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. This works because: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. The scenario is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. Verify the outcome by: Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.

C.

Apply least-privilege Azure RBAC and data-plane permissions to private storage containers. This addresses a different situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The present case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The relevant action here is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

D.

Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics. This addresses a different situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The present case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The relevant action here is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

Question 662

At Westlake Commerce multi-tenant carts require scalable tenant-key access. The team proposes this approach: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. Which technical principle explains the choice?

  1. A hierarchical namespace supports file and directory-oriented operations that differ from flat blob-name prefixes.
  2. Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.
  3. Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes.
  4. A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

Answer & Explanations

Correct answer: B

A.

A hierarchical namespace supports file and directory-oriented operations that differ from flat blob-name prefixes. That explains a separate situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The current case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The actual mechanism is: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.

B.

Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. This principle supports the intervention: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. The relevant scenario is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. Verify the result by: Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.

C.

Cosmos DB automatically indexes data under its policy; excluding unnecessary paths can reduce index maintenance for writes. That explains a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The current case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The actual mechanism is: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.

D.

A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. That explains a separate situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The current case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. The actual mechanism is: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries.

Question 663

At Westlake Commerce multi-tenant carts require scalable tenant-key access. After implementing this approach—Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns—which result would most directly confirm success?

  1. Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.
  2. Compare a representative query and insert workload before and after adjusting a test indexing policy.
  3. Query one tenant's fictional records by partition and row key while measuring request behavior.
  4. Run a representative test using the application's MongoDB driver and verify its required operations.

Answer & Explanations

Correct answer: A

A.

Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key. This tests the targeted action: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. The reason is: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. The reported case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access.

B.

Compare a representative query and insert workload before and after adjusting a test indexing policy. This tests a separate situation: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. The observed case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. Use this acceptance check instead: Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.

C.

Query one tenant's fictional records by partition and row key while measuring request behavior. This tests a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The observed case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. Use this acceptance check instead: Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.

D.

Run a representative test using the application's MongoDB driver and verify its required operations. This tests a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The observed case is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. Use this acceptance check instead: Simulate tenant traffic and verify the selected key supports efficient reads without one dominant hot key.

Question 664

At Westlake Commerce multi-tenant carts require scalable tenant-key access. Which shortcut most directly threatens the intended data outcome?

  1. Assume locally redundant copies within one site protect against every regional disaster.
  2. Use the same fixed partition value for all high-volume users to simplify code.
  3. Remove every indexed path even though the production app filters on nested document fields.
  4. Treat every eventually consistent replica as guaranteeing immediate read-after-write globally.

Answer & Explanations

Correct answer: B

A.

Assume locally redundant copies within one site protect against every regional disaster. This concerns another issue: At Cedarbank Payments retained transaction exports require defined regional resilience. In the stated case—At Westlake Commerce multi-tenant carts require scalable tenant-key access—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

B.

Use the same fixed partition value for all high-volume users to simplify code. The scenario is: At Westlake Commerce multi-tenant carts require scalable tenant-key access. This undermines the mechanism: Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. Instead: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

C.

Remove every indexed path even though the production app filters on nested document fields. This concerns another issue: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. In the stated case—At Westlake Commerce multi-tenant carts require scalable tenant-key access—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

D.

Treat every eventually consistent replica as guaranteeing immediate read-after-write globally. This concerns another issue: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. In the stated case—At Westlake Commerce multi-tenant carts require scalable tenant-key access—reject: Use the same fixed partition value for all high-volume users to simplify code. The safer response is: Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns.

Question 665

At Cedarbrook Finance an application looks up one invoice document by known keys. Which design or Azure data approach best fits this requirement?

  1. Apply least-privilege Azure RBAC and data-plane permissions to private storage containers.
  2. Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
  3. Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.
  4. Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion.

Answer & Explanations

Correct answer: C

A.

Apply least-privilege Azure RBAC and data-plane permissions to private storage containers. This addresses a different situation: At Meadowcrest Banking one analytics service reads a restricted statements container. The present case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

B.

Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. This addresses a different situation: At Cedarfield Apps developers build a new JSON-first profile service. The present case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

C.

Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. This works because: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. The scenario is: At Cedarbrook Finance an application looks up one invoice document by known keys. Verify the outcome by: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

D.

Apply time-to-live settings to automatically expire Cosmos DB items when the application's retention policy permits deletion. This addresses a different situation: At Pinebank Services temporary user sessions must disappear after a defined window. The present case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

Question 666

At Cedarbrook Finance an application looks up one invoice document by known keys. The team proposes this approach: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. Which technical principle explains the choice?

  1. A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.
  2. The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
  3. LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties.
  4. Container or item TTL can remove expired records according to the configured lifetime and policy.

Answer & Explanations

Correct answer: A

A.

A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. This principle supports the intervention: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. The relevant scenario is: At Cedarbrook Finance an application looks up one invoice document by known keys. Verify the result by: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

B.

The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. That explains a separate situation: At Cedarfield Apps developers build a new JSON-first profile service. The current case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

C.

LRS, ZRS and geographically redundant options provide different replica placement and disaster-protection properties. That explains a separate situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The current case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

D.

Container or item TTL can remove expired records according to the configured lifetime and policy. That explains a separate situation: At Pinebank Services temporary user sessions must disappear after a defined window. The current case is: At Cedarbrook Finance an application looks up one invoice document by known keys. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

Question 667

At Cedarbrook Finance an application looks up one invoice document by known keys. After implementing this approach—Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently—which result would most directly confirm success?

  1. Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
  2. Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.
  3. Query one tenant's fictional records by partition and row key while measuring request behavior.
  4. Update a fictional order item and verify the consumer receives the change once under idempotent processing.

Answer & Explanations

Correct answer: B

A.

Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode. This tests a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The observed case is: At Cedarbrook Finance an application looks up one invoice document by known keys. Use this acceptance check instead: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

B.

Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan. This tests the targeted action: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. The reason is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. The reported case is: At Cedarbrook Finance an application looks up one invoice document by known keys.

C.

Query one tenant's fictional records by partition and row key while measuring request behavior. This tests a separate situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The observed case is: At Cedarbrook Finance an application looks up one invoice document by known keys. Use this acceptance check instead: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

D.

Update a fictional order item and verify the consumer receives the change once under idempotent processing. This tests a separate situation: At Harborview Retail inventory changes feed a search-index updater. The observed case is: At Cedarbrook Finance an application looks up one invoice document by known keys. Use this acceptance check instead: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

Question 668

At Cedarbrook Finance an application looks up one invoice document by known keys. Which shortcut most directly threatens the intended data outcome?

  1. Run a full container cross-partition query for every known primary-key lookup.
  2. Rename the database endpoint without evaluating driver and operator support.
  3. Remove every indexed path even though the production app filters on nested document fields.
  4. Put all high-volume independent tenants into one constant partition key without considering load.

Answer & Explanations

Correct answer: A

A.

Run a full container cross-partition query for every known primary-key lookup. The scenario is: At Cedarbrook Finance an application looks up one invoice document by known keys. This undermines the mechanism: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. Instead: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

B.

Rename the database endpoint without evaluating driver and operator support. This concerns another issue: At Harborpoint Software an existing document app uses MongoDB clients. In the stated case—At Cedarbrook Finance an application looks up one invoice document by known keys—reject: Run a full container cross-partition query for every known primary-key lookup. The safer response is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

C.

Remove every indexed path even though the production app filters on nested document fields. This concerns another issue: At Silvercrest Logistics rapid telemetry writes rarely query most optional JSON properties. In the stated case—At Cedarbrook Finance an application looks up one invoice document by known keys—reject: Run a full container cross-partition query for every known primary-key lookup. The safer response is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

D.

Put all high-volume independent tenants into one constant partition key without considering load. This concerns another issue: At Pineport Logistics each region has a large independent group of shipment metadata records. In the stated case—At Cedarbrook Finance an application looks up one invoice document by known keys—reject: Run a full container cross-partition query for every known primary-key lookup. The safer response is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

Question 669

At Harborfield Logistics a tracking API retrieves one package status record. Which design or Azure data approach best fits this requirement?

  1. Store large binary images and backups as blobs in Azure Blob Storage with appropriate container access policies.
  2. Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics.
  3. Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.
  4. Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.

Answer & Explanations

Correct answer: C

A.

Store large binary images and backups as blobs in Azure Blob Storage with appropriate container access policies. This addresses a different situation: At Harborcrest Media hundreds of thousands of images need private object storage. The present case is: At Harborfield Logistics a tracking API retrieves one package status record. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

B.

Select an appropriate Cosmos DB consistency level based on acceptable stale reads and business semantics. This addresses a different situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The present case is: At Harborfield Logistics a tracking API retrieves one package status record. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

C.

Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. This works because: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. The scenario is: At Harborfield Logistics a tracking API retrieves one package status record. Verify the outcome by: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

D.

Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. This addresses a different situation: At Pineport Retail product searches consume more resources than simple ID reads. The present case is: At Harborfield Logistics a tracking API retrieves one package status record. The relevant action here is: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently.

Question 670

At Harborfield Logistics a tracking API retrieves one package status record. The team proposes this approach: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. Which technical principle explains the choice?

  1. A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.
  2. Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions.
  3. Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
  4. Blob Storage is object storage designed for unstructured content, independently of relational table structures.

Answer & Explanations

Correct answer: A

A.

A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query. This principle supports the intervention: Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. The relevant scenario is: At Harborfield Logistics a tracking API retrieves one package status record. Verify the result by: Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan.

B.

Consistency choices trade visibility guarantees, availability and latency; stronger guarantees may be essential for some decisions. That explains a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The current case is: At Harborfield Logistics a tracking API retrieves one package status record. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

C.

Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. That explains a separate situation: At Pineport Retail product searches consume more resources than simple ID reads. The current case is: At Harborfield Logistics a tracking API retrieves one package status record. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

D.

Blob Storage is object storage designed for unstructured content, independently of relational table structures. That explains a separate situation: At Harborcrest Media hundreds of thousands of images need private object storage. The current case is: At Harborfield Logistics a tracking API retrieves one package status record. The actual mechanism is: A point read targets one item directly and commonly consumes fewer request units than an equivalent broad query.

Microsoft Azure Data Fundamentals (DP-900) Practice Tests