Examkin

Soru

Zorluk: OrtaAzure Cosmos DB and NoSQL Solutions

A company is designing a global booking application for hotel reservations. The application must support:
- Sub-10ms read and write response times for users worldwide.
- High-throughput write ingestion of reservation records.
- Resilience against regional outages without requiring manual failover.
- Queries that primarily retrieve individual booking details using a unique booking ID, and secondary queries that list all bookings by hotel.

You need to design the Azure Cosmos DB NoSQL solution. Which two configurations should you recommend to meet the requirements?

  1. Enable multi-region writes and configure the container's partition key using the booking ID.Cevap
  2. Configure the Azure Cosmos DB account to replicate across multiple regions and enable service-managed failover.Cevap
  3. C
    Configure the container's partition key using the hotel country code.
  4. D
    Deploy the database account to use single-region locally redundant storage (LRS) to minimize write replication latency.
  5. E
    Generate a Shared Access Signature (SAS) token with a lifetime of 5 years to authenticate client application instances.

Cevap

Enable multi-region writes, configure the container's partition key using the booking ID, replicate the account across multiple regions, and enable service-managed failover.
The correct architecture uses a high-cardinality partition key (booking ID) to distribute operations evenly across physical partitions, avoiding throttling. To meet the latency and availability goals, the Azure Cosmos DB account must replicate to multiple regions with multi-region writes enabled, and service-managed failover must be enabled to automate disaster recovery.

Adım Adım Çözüm

1
Select a partition key with high cardinality.
Using the unique booking ID ensures writes and reads are distributed evenly across logical partitions, avoiding hot partitions.
Choosing a low-cardinality key like hotel country code would create hot partitions, which violates Cosmos DB best practices.
2
Configure global distribution and failover options.
Enabling multi-region writes and replicating to multiple regions provides low latency and geo-redundancy, while service-managed failover automates disaster recovery.
This configuration provides sub-10ms writes globally and guarantees automatic failover in the event of a regional outage.

Anahtar Kavram

Azure Cosmos DB partition key design and high-availability configuration
Bu soruyu puanla

Konular

Azure Cosmos DB and NoSQL Solutions

Bu konudan daha fazla soru