Optimize Query Performance When Using the API for Azure Cosmos DB for NoSQL DP-420 Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A logistics company uses Azure Cosmos DB for NoSQL to store shipment tracking events. The container receives a high volume of writes, and the application frequently queries recent shipments by `shipmentId` and `status`. The development team wants to reduce write latency and RU consumption, but they are concerned about query consistency. They are considering switching the indexing mode from Consistent to Lazy. What should you recommend?

   • AKeep Consistent indexing because Lazy indexing can cause queries to miss recently written items, which is unacceptable for a tracking application.
   • BSwitch to Lazy indexing and also change the default consistency level to Strong to ensure queries see the latest writes.
   • CSwitch to Lazy indexing because it reduces write RU cost and write latency, and queries will still be eventually consistent.
   • DKeep Consistent indexing and also enable the integrated cache to reduce query RU cost.
   Reveal Solution Discussion Select an answer first
2. 12foundation · easy

   Which indexing mode in Azure Cosmos DB provides the most up-to-date query results immediately after a write operation?

   • AConsistent indexing
   • BNone indexing
   • CAutomatic indexing
   • DLazy indexing
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   You have a workload with high write throughput and you can tolerate slightly stale query results. Which indexing mode would you choose to reduce write latency?

   • ALazy indexing
   • BNo indexing
   • CComposite indexing
   • DConsistent indexing
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A developer wants to retrieve the RU cost of a specific point read operation in Azure Cosmos DB for NoSQL. They are using the .NET SDK. Which approach should they use?

   • AUse the Azure Portal's 'Metrics' blade to see the RU cost for the last point read.
   • BEnable diagnostic logs and query the logs for the RU cost.
   • CUse the `x-ms-request-charge` header in the HTTP response, but only if using the REST API.
   • DRead the `RequestCharge` property from the response object of the point read operation.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A team is planning to migrate an on-premises MongoDB workload to Azure Cosmos DB for NoSQL. They need to estimate the RU cost for a typical query that filters on a single property and returns a small result set. They have the query execution statistics from the current MongoDB database. What is the best way to estimate the RU cost in Cosmos DB?

   • AAssume the RU cost will be the same as the MongoDB query cost in milliseconds.
   • BUse the Azure Cosmos DB capacity planner and input the query pattern and data size.
   • CUse the Azure Monitor metrics from the MongoDB instance to estimate RU.
   • DRun the query in Cosmos DB with a sample dataset and measure the RU cost.
   Reveal Solution Discussion Select an answer first