Your production team has created a Multi-AZ Amazon RDS instance. The application connects to the instance via a custom DNS A record. There was an instance wherein the primary database failed, and the application could no longer connect to the database. What needs to be done to ensure that this same issue does not happen in the future?

Answer options:

A.Ensure that the application is using the Amazon RDS hostname.
B.Ensure the primary database is quickly swapped with the secondary one.
C.Ensure that the application is using the IP address of primary database instance.
D.Ensure that the application is using the IP address of secondary database instance.

Answer – A
You need to ensure that the application connects using the Amazon RDS hostname. In the case of a primary instance issue, automatically in the backend, the swap will occur to the secondary instance.
Option B is invalid because the switch over is done by AWS.
Options C and D are invalid because you should never point to the IP address of the databases.
For more information on MultiAZ for databases, just browse to the below URL:
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html