Microsoft DP-900 Dumps
Microsoft DP-900 Practice Test 65
Question 640
At Meadowport Travel a worldwide itinerary service needs low-latency document reads. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: C
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 Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
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 Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
Assume a single-region local file database automatically delivers globally distributed consistency. The scenario is: At Meadowport Travel a worldwide itinerary service needs low-latency document reads. This undermines the mechanism: Cosmos DB supports managed multi-region distribution for eligible APIs and workloads while design choices affect cost and consistency. Instead: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
Publish a perpetual account-level SAS with write and delete rights for a one-file download. This concerns another issue: At Silverlake Media a partner needs temporary read access to one approved asset. In the stated case—At Meadowport Travel a worldwide itinerary service needs low-latency document reads—reject: Assume a single-region local file database automatically delivers globally distributed consistency. The safer response is: Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs.
Question 641
At Cedarfield Apps developers build a new JSON-first profile service. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: D
Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This addresses a different situation: At Silverbrook Commerce customers in several continents update shopping preferences. The present case is: At Cedarfield Apps developers build a new JSON-first profile service. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
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 Cedarfield Apps developers build a new JSON-first profile service. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Use an appropriate cool or cold blob tier for infrequently accessed but still online objects. This addresses a different situation: At Silverbridge Insurance last year's claim attachments are accessed only occasionally. The present case is: At Cedarfield Apps developers build a new JSON-first profile service. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. This works because: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. The scenario is: At Cedarfield Apps developers build a new JSON-first profile service. Verify the outcome by: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Question 642
At Cedarfield Apps developers build a new JSON-first profile service. The team proposes this approach: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. Which technical principle explains the choice?
Answer & Explanations
Correct answer: B
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 Cedarfield Apps developers build a new JSON-first profile service. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. This principle supports the intervention: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. The relevant scenario is: At Cedarfield Apps developers build a new JSON-first profile service. Verify the result by: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
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 Cedarfield Apps developers build a new JSON-first profile service. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. That explains a separate situation: At Harborpoint Software an existing document app uses MongoDB clients. The current case is: At Cedarfield Apps developers build a new JSON-first profile service. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
Question 643
At Cedarfield Apps developers build a new JSON-first profile service. After implementing this approach—Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents—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 Cedarfield Apps developers build a new JSON-first profile service. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
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 Cedarfield Apps developers build a new JSON-first profile service. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields. This tests the targeted action: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. The reason is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. The reported case is: At Cedarfield Apps developers build a new JSON-first profile service.
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 Cedarfield Apps developers build a new JSON-first profile service. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Question 644
At Cedarfield Apps developers build a new JSON-first profile service. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: C
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 Cedarfield Apps developers build a new JSON-first profile service—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
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 Cedarfield Apps developers build a new JSON-first profile service—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The scenario is: At Cedarfield Apps developers build a new JSON-first profile service. This undermines the mechanism: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. Instead: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Provision throughput based only on storage capacity without testing query complexity. This concerns another issue: At Pineport Retail product searches consume more resources than simple ID reads. In the stated case—At Cedarfield Apps developers build a new JSON-first profile service—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Question 645
At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: D
Enable hierarchical namespace for Azure Data Lake Storage Gen2 when directory semantics and analytics engines require it. This addresses a different situation: At Oakridge Analytics Spark jobs work with folder-based lake partitions. The present case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Choose Azure Cosmos DB for globally distributed document applications with defined latency and consistency needs. This addresses a different situation: At Silverbrook Commerce customers in several continents update shopping preferences. The present case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
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 Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The relevant action here is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. This works because: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. The scenario is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Verify the outcome by: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Question 646
At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The team proposes this approach: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. Which technical principle explains the choice?
Answer & Explanations
Correct answer: 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 Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
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 Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. This principle supports the intervention: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. The relevant scenario is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Verify the result by: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Blob access tiers trade storage price for retrieval and transaction costs according to access frequency. That explains a separate situation: At Pinefield Retail product images are fetched continuously by shoppers. The current case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. The actual mechanism is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model.
Question 647
At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. After implementing this approach—Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents—which result would most directly confirm success?
Answer & Explanations
Correct answer: B
Create a test document and read it from a configured second region under the selected consistency policy. This tests a separate situation: At Silverbrook Commerce customers in several continents update shopping preferences. The observed case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields. This tests the targeted action: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents. The reason is: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. The reported case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL.
Upload and retrieve a synthetic image while an unauthenticated test request is denied by policy. This tests a separate situation: At Harborcrest Media hundreds of thousands of images need private object storage. The observed case is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
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 Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Use this acceptance check instead: Insert a fictional JSON profile and execute a supported Cosmos DB for NoSQL query over its fields.
Question 648
At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. Which shortcut most directly threatens the intended data outcome?
Answer & Explanations
Correct answer: B
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 Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The scenario is: At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL. This undermines the mechanism: The NoSQL API addresses JSON items through containers, partition keys and the service's own query model. Instead: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Grant ordinary application users delete rights to all archived compliance evidence. This concerns another issue: At Harborland Securities trade evidence requires enforced retention. In the stated case—At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Run a full container cross-partition query for every known primary-key lookup. This concerns another issue: At Cedarbrook Finance an application looks up one invoice document by known keys. In the stated case—At Pineview Retail a product catalog has nested properties accessed through Cosmos DB NoSQL—reject: Assume a relational T-SQL stored procedure runs unchanged against every Cosmos DB API. The safer response is: Choose the Azure Cosmos DB for NoSQL API when an application uses native JSON item operations and SQL-like queries for documents.
Question 649
At Harborpoint Software an existing document app uses MongoDB clients. Which design or Azure data approach best fits this requirement?
Answer & Explanations
Correct answer: A
Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors. This works because: API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. The scenario is: At Harborpoint Software an existing document app uses MongoDB clients. Verify the outcome by: Run a representative test using the application's MongoDB driver and verify its required operations.
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 Harborpoint Software an existing document app uses MongoDB clients. The relevant action here is: Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors.
Use a point read with both ID and partition key when a known Cosmos DB item must be retrieved efficiently. This addresses a different situation: At Cedarbrook Finance an application looks up one invoice document by known keys. The present case is: At Harborpoint Software an existing document app uses MongoDB clients. The relevant action here is: Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors.
Pick sensible partition keys for Table Storage based on common access patterns and partition distribution. This addresses a different situation: At Pineport Logistics each region has a large independent group of shipment metadata records. The present case is: At Harborpoint Software an existing document app uses MongoDB clients. The relevant action here is: Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors.
Question 650
At Harborpoint Software an existing document app uses MongoDB clients. The team proposes this approach: Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors. Which technical principle explains the choice?
Answer & Explanations
Correct answer: D
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 Harborpoint Software an existing document app uses MongoDB clients. The actual mechanism is: API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
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 Harborpoint Software an existing document app uses MongoDB clients. The actual mechanism is: API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
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 Harborpoint Software an existing document app uses MongoDB clients. The actual mechanism is: API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering.
API compatibility is a migration consideration and supported features must be confirmed for the chosen Cosmos offering. This principle supports the intervention: Evaluate the Cosmos DB API for MongoDB when an existing application depends on supported MongoDB drivers and query behaviors. The relevant scenario is: At Harborpoint Software an existing document app uses MongoDB clients. Verify the result by: Run a representative test using the application's MongoDB driver and verify its required operations.
Microsoft Azure Data Fundamentals (DP-900) Practice Tests
- Microsoft DP-900 Practice Test 63 - 10 Questions (Last Reviewed 13-Nov-2026)
- Microsoft DP-900 Practice Test 64 - 10 Questions (Last Reviewed 12-Nov-2026)
- Microsoft DP-900 Practice Test 65 - 10 Questions (Last Reviewed 11-Nov-2026)
- 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)