A company runs a production application using an Amazon RDS for MariaDB DB instance configured in a Multi-AZ deployment. During a scheduled maintenance window, Amazon RDS performs a failover to the standby replica. The SysOps Administrator needs to confirm that the failover was successful and ensure that the application servers reconnect to the newly promoted primary instance as quickly as possible. Which of the following actions should the SysOps Administrator take? (Select TWO.)
- Monitor the Amazon RDS events for the DB instance to verify that a failover has started and completed.Answer
- Ensure that the DNS caching configuration (TTL) on the application servers is set to a low value so that they quickly resolve the DB instance CNAME record to the new primary IP address.Answer
- CManually promote the standby read replica to primary using the Amazon RDS console to complete the failover process.
- DModify the application configuration files to point to the dedicated DNS endpoint of the standby replica.
- EConfigure an Amazon Route 53 failover routing policy to redirect database connections from the primary database IP address to the standby database IP address.
Answer
To verify the failover status and ensure rapid application reconnection, the administrator should monitor the Amazon RDS events and configure a low DNS caching TTL on the application servers.
The correct options recommend monitoring Amazon RDS events to verify failover completion and configuring client-side DNS TTL settings to a low value. Since Amazon RDS manages Multi-AZ failover by updating the CNAME record for the DB instance endpoint, the application needs to query DNS for the new IP address quickly without using cached values.
Step-by-Step Solution
Key Concept
Amazon RDS Multi-AZ failover utilizes automatic CNAME redirection, requiring short client-side DNS caching (TTL) for quick application recovery.