Configuring Aurora Cluster for High Availability
Question
You are helping the development team to create an Aurora MySQL cluster for a new web application.
The cluster was created with a Dev/Test template since it was unclear about the details of requirements.
There was only one writer in the DB cluster, and there was no read replica.
Recently, the Aurora database proved to be successful.
You were told to configure the DB cluster to make it highly available.
How should you set up the existing Aurora cluster?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer - A.
Aurora read replicas can spread over multiple Availability Zones to improve the availability of the DB cluster.
About how to add replicas, refer to.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-replicas-adding.html.Option A is CORRECT: Because a replica can be easily added in AWS console:
Option B is incorrect: Because it is unnecessary to remove and recreate the cluster.
Option C is incorrect: Because the question does not mention that cross-region replications are needed.
A regional replica should already meet the need.
Option D is incorrect: Because the serverless feature mainly solves the problem of capacity.
Aurora Serverless clusters and provisioned clusters have the same kind of highly available storage volume.
The best option for making the Aurora cluster highly available is to add Aurora replicas to the existing Dev/Test Aurora cluster using the RDS console by selecting "Actions" and then "Add reader." Therefore, the correct answer is A.
Explanation:
Aurora is a high-performance, scalable relational database engine built for the cloud, that combines the speed and availability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. Aurora is a MySQL and PostgreSQL-compatible relational database management system (RDBMS) that is available on Amazon Web Services (AWS). Aurora provides two types of replicas: Aurora Replicas and Amazon RDS MySQL or PostgreSQL Read Replicas. Aurora replicas can help to increase availability and scale reads to a larger number of applications.
In this case, there is only one writer in the Aurora cluster, which means if the writer fails, the database will be down, and there will be no availability. Therefore, to make the Aurora cluster highly available, it is necessary to add Aurora replicas to the cluster. Aurora replicas can handle read traffic, and if the writer fails, one of the replicas can be promoted to become the new writer automatically.
Option B, which suggests deleting and recreating the Aurora cluster with a Production template, is not a feasible option as the active Aurora cluster cannot configure read replicas. Deleting the Aurora cluster would result in the loss of all data stored in the cluster.
Option C suggests using AWS CLI to configure cross-region replication for the DB cluster to make it highly available. Cross-region replication is a good option for disaster recovery, but it does not provide high availability. Cross-region replication is used to create a copy of the data in another region to prevent data loss in case of a disaster.
Option D suggests deleting the existing cluster and creating a new Aurora cluster with a serverless feature to make it highly available. This option is not the best approach since the cluster already contains data that could be lost if the cluster is deleted. Additionally, serverless Aurora is a good option for managing capacity in a cost-effective manner, but it does not guarantee high availability.