SAP-C02 Continuous Improvement for Existing Solutions Practice Question
A company has a legacy application that runs on a single EC2 instance. The application stores data on an attached EBS volume. The company wants to improve availability and reduce the recovery time objective (RTO) in case of instance failure. What should the company do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create an Auto Scaling group with a minimum of 2 instances across multiple Availability Zones and use a load balancer.
An Auto Scaling group with a minimum of two instances across multiple Availability Zones combined with a load balancer provides high availability and automatic failover, reducing RTO significantly. Option B is wrong: while EBS snapshots are useful for backups, restoring from a snapshot to create a new instance involves manual steps and can take minutes, not improving RTO adequately. Option C is wrong: Multi-Attach EBS volumes are for specific clustered applications (e.g., Windows Server Failover Clustering) and not all applications support it; also, it does not provide automatic failover. Option D is wrong: converting to an AMI and launching in another AZ requires manual intervention and does not ensure rapid recovery; it's a migration step, not an availability solution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create an Auto Scaling group with a minimum of 2 instances across multiple Availability Zones and use a load balancer.
Why this is correct
An Auto Scaling group with a minimum of 2 instances across multiple Availability Zones and a load balancer provides automatic failover and load distribution, reducing recovery time and improving availability.
- ✗
Take frequent EBS snapshots and automate the creation of a new instance from the latest snapshot.
Why it's wrong here
Taking frequent EBS snapshots and automating instance creation from snapshots can restore data but involves launching a new instance and attaching volumes, which takes time and does not provide instant failover. The RTO may be longer than desired.
- ✗
Configure the EBS volume as a Multi-Attach volume and attach it to a standby instance.
Why it's wrong here
Multi-Attach EBS volumes are designed for clustered applications and not all applications support them. Moreover, attaching a Multi-Attach volume to a standby instance does not automatically handle traffic failover; manual intervention is still required.
- ✗
Convert the instance to an AMI and launch a new instance from that AMI in a different Availability Zone.
Why it's wrong here
Converting the instance to an AMI and launching in another Availability Zone is a manual migration process that requires manual steps to redirect traffic (e.g., updating DNS or route tables). It does not provide automatic failover and results in a longer RTO.
Go deeper
Related to this question
About these practice questions
This SAP-C02 question is part of Courseiva's 1,660-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAP-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAP-C02 exam.