A company has an application running on EC2 that stores data in an Amazon RDS for MySQL Single- AZ DB instance. The application requires both read and write operations, and the company needs…

Question

Options

• AModify the DB instance to be a Multi-AZ DB instance deployment.
• BAdd a read replica in the same Availability Zone where the DB instance is deployed.
• CAdd the DB instance to an Auto Scaling group that has a minimum capacity of 2 and a desired
• DUse RDS Proxy to configure a proxy in front of the DB instance.

• A
  89% (39)
• B
  2% (1)
• C
  7% (3)
• D
  2% (1)

Explanation

Explanation

Converting the RDS instance to a Multi-AZ deployment directly addresses the failover requirement by automatically maintaining a synchronous standby replica in a separate Availability Zone - if the primary instance fails, RDS automatically promotes the standby with minimal downtime (typically 60–120 seconds), requiring no application changes.

Why the distractors are wrong:

• Option B is incorrect because a read replica in the same AZ provides no failover capability and only handles read traffic - it defeats the purpose of high availability
• Option C is incorrect because RDS DB instances are not EC2 instances; they cannot be placed in Auto Scaling groups, which manage compute capacity, not managed database instances
• Option D is incorrect because RDS Proxy improves connection pooling and reduces database load, but it does not provide failover or high availability on its own - it acts as a connection manager, not a redundancy solution

Memory Tip: Think of Multi-AZ = High Availability (HA) and Read Replicas = Scalability. Whenever an exam question mentions failover or minimal downtime for RDS, Multi-AZ is almost always the answer. The two concepts are commonly tested together, so keeping them clearly separated will help you quickly eliminate distractors.

No community discussion yet for this question.