Home › AWS SysOps Associate › cloudcomputing › sysopsmonitoring › A multi-AZ RDS deployment for a write-heavy data…
A multi-AZ RDS deployment for a write-heavy database experiences a primary AZ failure. What happens?
ABoth primary and standby are lost together
BRDS migrates the database to Amazon Glacier
CRDS automatically fails over to the standby in the other AZ, updates the DNS endpoint, and applications reconnect with brief downtime
DCustomers must manually re-provision the database from scratch
Answer & Solution
Correct answer: C. RDS automatically fails over to the standby in the other AZ, updates the DNS endpoint, and applications reconnect with brief downtime
Multi-AZ Maintains a synchronous standby in another AZ; automatic failover with DNS endpoint update is the value prop. The other options misstate Multi-AZ.
Related questions
An EC2 Auto Scaling group is set to launch from an AMI baked weekly. After the latest AMI A team needs disaster recovery with an RTO ≤ 15 minutes and RPO ≤ 5 minutes across two AWSWhich service detects unexpected drift between an AWS resource's actual configuration and Which automation pattern is BEST for self-healing a stuck EC2 instance — for example, restAn RDS database needs point-in-time-restore for 14 days plus a guaranteed daily backup. WhAn EC2 instance's CPU steady-state is fine but bursts to 100% during scheduled jobs. The tWhich Route 53 routing policy is used to fail traffic over from a primary endpoint to a stAn EC2 fleet behind an ALB needs to scale out when average CPU goes above 70% for 5 minute