Q77 — AWS DOP-C02 Ch.1
Question 77 of 100 | ← Chapter 1
A company uses an Amazon Aurora cluster as the data store for its application. The Aurora cluster is configured with one DB instance. The application uses the cluster endpoint to perform read and write operations on the database. The company plans to apply updates to the cluster during an upcoming maintenance window. During the maintenance window, cluster availability must be maintained, with minimal disruption.
- A. Add a reader instance to the Aurora cluster. Update the application to use the Aurora cluster endpoint for write operations. Update the application to use the Aurora reader endpoint for read operations. ✓
- B. Add a reader instance to the Aurora cluster. Create a custom cluster endpoint. Update the application to use the custom cluster endpoint for both read and write operations.
- C. Enable the Multi-AZ option on the Aurora cluster. Update the application to use the Aurora cluster endpoint for write operations. Update the application to use the Aurora reader endpoint for read operations.
- D. Enable the Multi-AZ option on the Aurora cluster. Create a custom cluster endpoint. Update the application to use the custom cluster endpoint for both read and write operations.
Correct Answer: A. Add a reader instance to the Aurora cluster. Update the application to use the Aurora cluster endpoint for write operations. Update the application to use the Aurora reader endpoint for read operations.
Explanation
This question tests core concepts of Amazon Aurora high availability. The cluster endpoint always routes writes to the primary instance and reads to reader instances when used with the reader endpoint. Adding a reader instance enables read scaling and offloads read traffic during maintenance, preserving write availability through the cluster endpoint. While Multi-AZ provides automatic failover for disaster recovery, it does not inherently improve read scalability or reduce maintenance impact on writes. Custom endpoints do not provide routing intelligence for read/write separation and are unnecessary here. Option A correctly leverages native Aurora endpoints for optimal, low-disruption maintenance.