Design a Data Partitioning Strategy for Azure Cosmos DB for NoSQL DP-420 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   In Azure Cosmos DB for NoSQL, how can you support multiple partition keys for different access patterns in a single container?

   • AUse a partition key that is a random value, and rely on cross-partition queries for all access patterns
   • BCreate multiple containers, each with a different partition key, and synchronize data between them
   • CUse a hierarchical partition key that includes the properties used in the different access patterns
   • DUse a partition key that is the concatenation of all possible keys, and always filter on the full key
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   An application stores IoT sensor readings in Azure Cosmos DB for NoSQL. Each reading is a separate item, and the application frequently queries readings for a specific device within a time range. Which partitioning strategy is most appropriate?

   • APartition by a random GUID for each reading to ensure even distribution
   • BPartition by timestamp so that all readings at the same time are together
   • CPartition by the sensor type to group similar sensors
   • DPartition by device ID so that all readings for a device are in the same logical partition
   Reveal Solution Discussion Select an answer first
4. 8expert · hard

   A retail analytics system stores sales transactions with storeId, productId, customerId, and saleDate. The business runs three equally important query patterns: sales by store, sales by product, and sales by customer. The system must minimize cross-partition queries for all three patterns. What is the most appropriate partitioning strategy?

   • AUse a synthetic partition key combining storeId, productId, and customerId.
   • BUse a hierarchical partition key: /storeId//productId//customerId.
   • CCreate three separate containers, each with a different partition key (storeId, productId, customerId), and synchronize data via change feed.
   • DUse storeId as the partition key and rely on indexing for product and customer queries.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A banking application stores account documents and transaction documents in the same container. The partition key is accountId. A stored procedure must transfer funds between two accounts. The two accounts are known at runtime and may be in different partitions. What is the best way to ensure the transfer is atomic?

   • ARun the stored procedure on each account's partition sequentially.
   • BUse a client-side transaction that spans both partitions.
   • CUse a synthetic partition key that groups the two accounts into the same logical partition (e.g., a joint account ID).
   • DUse the change feed to reconcile balances after the transfer.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A chat application stores messages with fields: conversationId, senderId, timestamp, and messageText. The partition key is conversationId. Some conversations are very active, while others are idle. What is the primary throughput-related risk?

   • AActive conversations will consume most of the provisioned throughput, causing throttling for other requests.
   • BIdle conversations will be deleted automatically.
   • CThe container will automatically scale to handle the hot conversations.
   • DThroughput will be evenly distributed across all conversations.
   Reveal Solution Discussion Select an answer first