Design and implement data distribution

A retail company runs an Azure Cosmos DB account with a single write region in East US. Their customer base has expanded significantly to Western Europe, and European users are reporting slow write latency when submitting orders, while reads remain acceptable. The team wants to reduce write latency for European customers with minimal application changes and without sacrificing the ability to resolve conflicting concurrent writes. Which configuration change should they make?

A financial services company runs a single-write-region Cosmos DB account with the write region in East US and read regions in West US and North Europe. They have enabled service-managed (automatic) failover and configured failover priorities as: 0 = East US, 1 = North Europe, 2 = West US. During a regional outage that makes East US unavailable, what happens to the write region?

A financial services company runs a globally distributed Cosmos DB account with a single write region in East US and read regions in West Europe and Southeast Asia. Compliance requires that reads never lag the write region by more than a defined number of write operations OR a defined time interval, whichever comes first, so auditors can bound the maximum data divergence. Which consistency level satisfies this requirement, and what must the team configure?

A social media application writes a sequence of user actions to a single-region Cosmos DB account: a user posts a comment (write 1), then edits it (write 2), then deletes it (write 3). The team wants readers in the same region to never see these writes out of order (for example, seeing the delete before the edit), but they want the lowest possible read latency and RU cost that still guarantees ordered reads. They do NOT require reads to always return the most recent write. Which consistency level should they configure?

A global gaming leaderboard application uses Azure Cosmos DB with read regions in North America, Europe, and Asia. The product team prioritizes the absolute lowest read latency, highest read availability, and the lowest read RU charge. They explicitly state that occasionally showing slightly out-of-order or stale scores to players is completely acceptable. Which consistency level should you configure to best meet these requirements?

A financial services company runs an Azure Cosmos DB account with a single write region in East US and read regions in West Europe and Southeast Asia. Automatic failover is enabled. The operations team wants to validate their disaster recovery runbook by promoting West Europe to be the write region during a controlled maintenance window, without simulating an actual regional outage. What should they do?

A retail company runs a Cosmos DB account with multi-region writes enabled across four Azure regions. Their inventory container receives concurrent updates to the same item from multiple regions. Business rules require that when two conflicting writes occur, the write with the highest 'stockLevel' value must always win, regardless of timestamp. The team wants this resolution to happen automatically without application-side intervention. Which conflict resolution configuration should they use?

A logistics company runs a globally distributed Cosmos DB account with multi-region writes enabled across four regions. Their shipment-tracking documents are frequently updated concurrently in different regions, and business rules require that when two updates conflict, the conflicting values must be merged into a single document by keeping the highest recorded package weight and concatenating the two status notes. Simple last-writer-wins behavior is not acceptable. Which conflict resolution configuration should they implement?

A retail company runs a Cosmos DB account with a single write region. Their engineering team reports that the shopping-cart feature must guarantee that a user always reads their own most recent cart updates, but reads from other users' sessions can tolerate slight lag. The team wants the lowest possible RU cost and highest availability while meeting this requirement. The application already routes all traffic for a given user through the same client session token. Which consistency level should you configure?

A retail company runs a Cosmos DB for NoSQL account backing a shopping cart microservice. Each user's session must immediately see their own cart updates after a write, but the workload is globally distributed and the team wants to minimize RU cost and write latency. Reads from other users' sessions may tolerate slight staleness. Which default consistency level should the team configure at the account level to meet these requirements?

A financial reporting application has an Azure Cosmos DB account deployed in East US as the sole write region. Analysts in Europe and Asia experience high read latency. Compliance requires that all write operations continue to be validated and serialized through a single location, and the team wants to minimize the risk of write conflicts while improving read performance for the distributed analysts. Which configuration best meets these requirements?

A financial services team is configuring an Azure Cosmos DB account that must be deployed across three Azure regions (East US, West Europe, and Southeast Asia). Their compliance team demands that every read return the most recent committed write with a linearizable guarantee. During design, an architect proposes enabling multi-region writes so that clients in each region write to their nearest region for lower write latency. What should you advise the team?