Examkin

Question

Difficulty: MediumResilient Database Configurations and High Availability

A global logistics platform is migrating its critical shipment tracking database to Amazon Aurora PostgreSQL. The database must be highly available within the local region, achieving a Recovery Time Objective (RTO) of less than 3030 seconds for failovers. Additionally, the system must handle a heavy volume of read requests without degrading the performance of write transactions. Which combination of configurations should a solutions architect implement to meet these requirements? (Select TWO.)

  1. Deploy an Amazon Aurora DB cluster across multiple Availability Zones with a primary writer instance and at least one reader instance.Answer
  2. Configure the application to use the Aurora cluster writer endpoint for write operations and the reader endpoint for read operations.Answer
  3. C
    Provision a single-AZ Aurora instance and configure an external RDS Read Replica in a different Availability Zone to serve as the automatic failover target.
  4. D
    Configure an Amazon Route 53 latency-based routing policy to split database write transactions between the primary instance and a read replica.
  5. E
    Implement a pilot light recovery strategy by exporting database snapshots to Amazon S3 and restoring them to a new cluster during an outage.

Answer

Deploy an Amazon Aurora DB cluster across multiple Availability Zones with a primary writer instance and at least one reader instance, and configure the application to use the Aurora cluster writer endpoint for write operations and the reader endpoint for read operations.
Deploying an Amazon Aurora DB cluster across multiple Availability Zones with a reader instance ensures automatic, rapid failover (typically under 3030 seconds) when the primary writer fails. By utilizing the cluster's dedicated writer and reader endpoints, the application can cleanly separate write transactions from heavy read volumes, ensuring read scaling does not degrade write performance.

Step-by-Step Solution

1
Select a database configuration that supports automatic regional failover under 3030 seconds.
Amazon Aurora Multi-AZ deployment with at least one Aurora Replica (reader) is chosen. In the event of a writer failure, Aurora promotes the reader to primary writer within 3030 seconds.
Meets the high availability and strict RTO requirements.
2
Address the read scaling requirement without impacting write performance.
Configure application connection endpoints to direct read traffic to the Aurora reader endpoint and write traffic to the writer endpoint.
This offloads read operations from the writer instance, preserving write transaction throughput.

Key Concept

Amazon Aurora Multi-AZ failover mechanics and endpoint routing for read/write scaling.
Rate this question

Topics

Resilient Database Configurations and High Availability

More questions from this topic