Q13 — AWS SAP-C02 Ch.1
Question 13 of 75 | ← Chapter 1
Q88. An application is using an Amazon RDS for MySQL Multi-AZ DB instance in the us-east-1 Region After a failover test, the application lost the connections to the database and could not re-establish the connections. After a restart of the application, the application re-established the connections. A solutions architect must implement a solution so that the application can re-establish connections to the database without requiring a restart.Which solution will meet these requirements?
- A. Create an Amazon Aurora MySQL Serverless v1 DB instance Migrate the RDS DB instance to the Aurora Serverless v1 DB instance Update the connection settings in the application to point to the Aurora reader endpoint
- B. Create an RDS proxy. Configure the existing RDS endpoint as a target Update the connection settings in the application to point to the RDS proxy endpoint ✓
- C. Create a two-node Amazon Aurora MySQL DB cluster. Migrate the RDS DB instance to the Aurora DB cluster. Create an RDS proxy. Configure the existing RDS endpoint as a target. Update the connection settings in the application to point to the RDS proxy endpoint
- D. Create an Amazon S3 bucket. Export the database to Amazon S3 by using AWS Database Migration Service (AWS DMS). Configure Amazon Athena to use the S3 bucket as a data store. Install the latest Open Database Connectivity (ODBC) driver for the application Update the connection settings in the application to point to the Athena endpoint
Correct Answer: B. Create an RDS proxy. Configure the existing RDS endpoint as a target Update the connection settings in the application to point to the RDS proxy endpoint
Explanation
The solution that will meet the requirements of allowing the application to re-establish connections to the database without requiring a restart is: B. Create an RDS proxy. Configure the existing RDS endpoint as a target. Update the connection settings in the application to point to the RDS proxy endpoint. Explanation: Option B: Creating an RDS proxy and configuring the existing RDS endpoint as a target is the appropriate solution for allowing the application to re-establish connections to the database without requiring a restart. The RDS proxy acts as an intermediary between the application and the database, managing connections and providing connection pooling capabilities. By updating the connection settings in the application to point to the RDS proxy endpoint, the application can establish and maintain connections to the database even during failovers. Option A is incorrect because migrating the RDS DB instance to an Aurora Serverless v1 DB instance does not directly address the requirement of allowing the application to re-establish connections without requiring a restart. While Aurora Serverless provides automatic scaling and high availability, it does not eliminate the need for reconnecting after a failover. Option C is incorrect because creating a two-node Aurora MySQL DB cluster and configuring an RDS proxy as a target does not directly address the requirement of allowing the application to re-establish connections without requiring a restart. While Aurora provides high availability, the RDS proxy is the key component for managing connections during failovers. Option D is incorrect because exporting the database to S3 and using Athena as a data store does not directly address the requirement of allowing the application to re-establish connections without requiring a restart. Additionally, installing an ODBC driver and updating the connection settings to point to the Athena endpoint would require significant changes to the application and its architecture. Therefore, the correct solution is B: Create an RDS proxy, configure the existing RDS endpoint as a target, and update the connection settings in the application to point to the RDS proxy endpoint. This solution enables the application to re-establish connections to the database without requiring a restart.