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

Questions 26–28

1. 26foundation · easy

   A container has a partition key with low cardinality, causing hot partitions. Which approach uses a synthetic partition key to improve distribution?

   • ACreate a new property that combines the existing partition key with a unique identifier, such as CustomerId_DeviceId
   • BRemove the partition key and use a single partition
   • CUse the item's ID as the partition key
   • DChange the partition key to a random GUID for every item
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A financial application stores transactions. The current partition key is accountId. The application performs frequent point-reads by accountId and also runs end-of-day reports that aggregate all transactions for a branch. The reports are slow and expensive. You need to reduce the cost of the branch-level reports while keeping point-reads efficient. What should you do?

   • AUse a synthetic partition key of branchId_accountId
   • BAdd a composite index on (branchId, timestamp)
   • CChange the partition key of the existing container to branchId
   • DCreate a materialized view container partitioned by branchId, populated via change feed
   Reveal Solution Discussion Select an answer first
3. 28foundation · easy

   A partition key has high cardinality, meaning it has many distinct values. What is the primary benefit of this characteristic for data distribution?

   • AIt reduces the need for indexing
   • BIt allows for more even distribution of data and request units across physical partitions
   • CIt ensures that each physical partition contains exactly one logical partition
   • DIt guarantees that all queries will be single-partition queries
   Reveal Solution Discussion Select an answer first