Which of the following benefits does adding Multi-AZ deployment in RDS provide?
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - A and D.
Option A is CORRECT because in Multi-AZ deployment, if an availability zone (AZ) goes down, the automatic failover occurs.
The DB instance CNAME gets pointed to the synchronously updated secondary instance in another AZ.
Option B is incorrect because Multi-AZ deployment does not affect the latency of the application's DB access.
Option C is incorrect because DB access time does not get affected by Multi-AZ deployment.
Option D is CORRECT because, during the maintenance tasks, the DB instance CNAME can point to the second instance in another AZ to carry out the DB tasks.
Some of the advantages of Multi-AZ rds deployments are given below.
If an Availability Zone failure or DB Instance failure occurs, your availability impact is limited to the time automatic failover takes to complete.
The availability benefits of Multi-AZ deployments also extend to planned maintenance and backups.
In the case of system upgrades like OS patching or DB Instance scaling, these operations are applied first on the standby, before the automatic failover.
As a result, your availability impact is, again, only the time required for automatic failover to complete.
If a storage volume on your primary fails in a Multi-AZ deployment, Amazon RDS automatically initiates a failover to the up-to-date standby.
For more information on Multi-AZ rds deployments, please visit the link.
https://aws.amazon.com/rds/details/multi-az/Multi-AZ (Availability Zone) deployment in Amazon RDS (Relational Database Service) provides high availability and resilience for your database. When you enable Multi-AZ deployment, a secondary database instance is automatically created in a different Availability Zone. Both the primary and secondary instances are kept in sync through synchronous replication.
The benefits of adding Multi-AZ deployment in RDS are as follows:
A. Multi-AZ deployed database can tolerate an Availability Zone failure: The primary database instance is located in one Availability Zone, while the secondary instance is located in another Availability Zone. In case of a planned or unplanned outage of the primary instance or its Availability Zone, Amazon RDS automatically promotes the secondary instance to the primary instance, providing uninterrupted database availability. This helps to prevent data loss and minimizes downtime.
B. Decrease latencies if app servers accessing the database are in multiple Availability zones: With Multi-AZ deployment, if your application servers are also distributed across multiple Availability Zones, they can access the secondary database instance that is located in the same Availability Zone as the app server, reducing the network latency and improving the application's response time.
C. Make database access times faster for all app servers: While Multi-AZ deployment may not necessarily improve the performance of your database, it can help ensure that database access times are consistent across all app servers, regardless of their location. This is because all app servers can access the same endpoint to connect to the database, which always points to the primary instance.
D. Make database more available during maintenance tasks: When Amazon RDS performs maintenance tasks on your database, such as patching the database engine or upgrading the database instance class, it performs these tasks on the secondary instance first. Once the secondary instance is up-to-date, it's promoted to the primary instance, and the maintenance tasks are then performed on the old primary instance. This helps to minimize downtime and ensure that your database remains available during maintenance tasks.
Therefore, the correct answer is A. Multi-AZ deployed database can tolerate an Availability Zone failure.