Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 68
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?
Answer & Explanations
Correct answer: 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.
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.
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.
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.
Question 671
At Harborfield Logistics a tracking API retrieves one package status record. 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?
Answer & Explanations
Correct answer: 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 Harborfield Logistics a tracking API retrieves one package status record. 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.
Attempt a controlled deletion of a test retained object and verify policy prevents it. This tests a separate situation: At Harborland Securities trade evidence requires enforced retention. The observed case is: At Harborfield Logistics a tracking API retrieves one package status record. 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.
Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields. This tests a separate situation: At Cedarfield Apps developers build a new JSON-first profile service. The observed case is: At Harborfield Logistics a tracking API retrieves one package status record. 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.
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 Harborfield Logistics a tracking API retrieves one package status record.
Question 672
At Harborfield Logistics a tracking API retrieves one package status record. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Run a full container cross-partition query for every known primary-key lookup. The scenario is: At Harborfield Logistics a tracking API retrieves one package status record. 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.
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 Harborfield Logistics a tracking API retrieves one package status record—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.
Enable an extremely short TTL on all compliance records without reviewing retention obligations. This concerns another issue: At Pinebank Services temporary user sessions must disappear after a defined window. In the stated case—At Harborfield Logistics a tracking API retrieves one package status record—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.
Put daily application assets directly into archive tier to minimize storage price alone. This concerns another issue: At Pinefield Retail product images are fetched continuously by shoppers. In the stated case—At Harborfield Logistics a tracking API retrieves one package status record—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 673
At Pineport Retail product searches consume more resources than simple ID reads. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: B
Choose appropriate Azure Storage redundancy based on durability, availability and geographic recovery requirements. This addresses a different situation: At Cedarbank Payments retained transaction exports require defined regional resilience. The present case is: At Pineport Retail product searches consume more resources than simple ID reads. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. This works because: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. The scenario is: At Pineport Retail product searches consume more resources than simple ID reads. Verify the outcome by: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
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 Pineport Retail product searches consume more resources than simple ID reads. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
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 Pineport Retail product searches consume more resources than simple ID reads. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Question 674
At Pineport Retail product searches consume more resources than simple ID reads. The team proposes this approach: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. Which technical principle explains the choice?
Answer & Explanations
Correct answer: C
Partition-key distribution affects scaling, hot partitions and the need for cross-partition queries. That explains a separate situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The current case is: At Pineport Retail product searches consume more resources than simple ID reads. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
WORM-style immutable storage controls restrict modifications or deletions according to configured retention or hold settings. That explains a separate situation: At Harborland Securities trade evidence requires enforced retention. The current case is: At Pineport Retail product searches consume more resources than simple ID reads. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. This principle supports the intervention: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. The relevant scenario is: At Pineport Retail product searches consume more resources than simple ID reads. Verify the result by: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
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 Pineport Retail product searches consume more resources than simple ID reads. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
Question 675
At Pineport Retail product searches consume more resources than simple ID reads. After implementing this approach—Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
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 Pineport Retail product searches consume more resources than simple ID reads. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode. This tests the targeted action: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. The reason is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. The reported case is: At Pineport Retail product searches consume more resources than simple ID reads.
Measure a sample workload with repeated object reads and verify the chosen tier supports required latency. This tests a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The observed case is: At Pineport Retail product searches consume more resources than simple ID reads. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Fetch a fictional profile by its ID and partition key and compare its request-unit charge with a query scan. This tests a separate situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The observed case is: At Pineport Retail product searches consume more resources than simple ID reads. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Question 676
At Pineport Retail product searches consume more resources than simple ID reads. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Provision throughput based only on storage capacity without testing query complexity. The scenario is: At Pineport Retail product searches consume more resources than simple ID reads. This undermines the mechanism: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. Instead: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Assume every rare-access object must be archived offline even when prompt retrieval is required. This concerns another issue: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. In the stated case—At Pineport Retail product searches consume more resources than simple ID reads—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Assume a single-region local file database automatically delivers globally distributed consistency. This concerns another issue: At Silverbrook Commerce customers in several continents update shopping preferences. In the stated case—At Pineport Retail product searches consume more resources than simple ID reads—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Re-export the entire container for every notification and assume no duplicate updates can occur. This concerns another issue: At Harborview Retail inventory changes feed a search-index updater. In the stated case—At Pineport Retail product searches consume more resources than simple ID reads—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Question 677
At Meadowcrest Banking high-volume status writes require predictable request capacity. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: C
Use a time-bounded, narrowly scoped shared access signature when temporary Blob Storage access is required. This addresses a different situation: At Silverlake Media a partner needs temporary read access to one approved asset. The present case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Choose a Cosmos DB partition key that spreads throughput and matches important point-read access patterns. This addresses a different situation: At Meadowfield Games user profiles are read by unique player ID under heavy load. The present case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. This works because: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. The scenario is: At Meadowcrest Banking high-volume status writes require predictable request capacity. Verify the outcome by: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
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 Meadowcrest Banking high-volume status writes require predictable request capacity. The relevant action here is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Question 678
At Meadowcrest Banking high-volume status writes require predictable request capacity. The team proposes this approach: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. Which technical principle explains the choice?
Answer & Explanations
Correct answer: A
Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. This principle supports the intervention: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. The relevant scenario is: At Meadowcrest Banking high-volume status writes require predictable request capacity. Verify the result by: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
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 Meadowcrest Banking high-volume status writes require predictable request capacity. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. That explains a separate situation: At Silverbrook Commerce customers in several continents update shopping preferences. The current case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
SAS credentials can grant defined resource operations and expiry without granting the recipient broad storage account administration. That explains a separate situation: At Silverlake Media a partner needs temporary read access to one approved asset. The current case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. The actual mechanism is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup.
Question 679
At Meadowcrest Banking high-volume status writes require predictable request capacity. After implementing this approach—Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning—which result would most directly confirm success?
Answer & Explanations
Correct answer: C
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 Meadowcrest Banking high-volume status writes require predictable request capacity. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Create test objects with different prefixes and verify only the approved eligible prefix changes tier. This tests a separate situation: At Westlake Finance statement exports move from hot to cool after an approved interval. The observed case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode. This tests the targeted action: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning. The reason is: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. The reported case is: At Meadowcrest Banking high-volume status writes require predictable request capacity.
Write a synthetic value and test subsequent reads across configured clients and regions. This tests a separate situation: At Silverline Events a newly reserved seat must have a carefully defined visibility guarantee. The observed case is: At Meadowcrest Banking high-volume status writes require predictable request capacity. Use this acceptance check instead: Replay a fictional read-write mix and inspect RU consumption and throttling under the chosen throughput mode.
Question 680
At Meadowcrest Banking high-volume status writes require predictable request capacity. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: A
Provision throughput based only on storage capacity without testing query complexity. The scenario is: At Meadowcrest Banking high-volume status writes require predictable request capacity. This undermines the mechanism: Request units measure normalized resource use; complex cross-partition queries cost more than a simple point lookup. Instead: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
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 Meadowcrest Banking high-volume status writes require predictable request capacity—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
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 Meadowcrest Banking high-volume status writes require predictable request capacity—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Enable an extremely short TTL on all compliance records without reviewing retention obligations. This concerns another issue: At Pinebank Services temporary user sessions must disappear after a defined window. In the stated case—At Meadowcrest Banking high-volume status writes require predictable request capacity—reject: Provision throughput based only on storage capacity without testing query complexity. The safer response is: Estimate Cosmos DB request-unit throughput for reads, writes and query patterns before provisioning.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- Microsoft DP-900 Practice Test 66 - 10 Questions (Last Reviewed 10-Nov-2026)
- Microsoft DP-900 Practice Test 67 - 10 Questions (Last Reviewed 09-Nov-2026)
- Microsoft DP-900 Practice Test 68 - 10 Questions (Last Reviewed 08-Nov-2026)
- Microsoft DP-900 Practice Test 69 - 10 Questions (Last Reviewed 07-Nov-2026)
- Microsoft DP-900 Practice Test 70 - 10 Questions (Last Reviewed 06-Nov-2026)