What would happen to an RDS (Relational Database Service) multi-Availability Zone deployment if the primary DB instance fails?
The IP of the primary DB Instance is switched to the standby DB Instance.
A new DB instance is created in the standby availability zone.
The canonical name record (CNAME) is changed from primary to standby.
The RDS (Relational Database Service) DB instance reboots.
Explanations:
In a multi-AZ deployment, the IP address of the primary DB instance is not switched to the standby. Instead, the standby instance takes over as the new primary, but its IP address remains different.
A new DB instance is not created in the standby availability zone. The existing standby instance is promoted to primary status, utilizing its existing resources, rather than provisioning a new instance.
The canonical name record (CNAME) associated with the DB instance endpoint is updated to point to the new primary DB instance (the standby). This allows clients to connect to the new primary without needing to know its IP address.
The RDS instance does not reboot upon failover. Instead, the failover process involves promoting the standby to primary without a reboot of either instance. The transition is handled automatically by RDS.