SOA-C02 Reliability and Business Continuity Practice Question
A company uses AWS CloudFormation to deploy its infrastructure. The SysOps administrator needs to ensure that the application stack can be recreated in another AWS Region in the event of a disaster. The stack includes an RDS MySQL database and an EC2 instance running a web server. The administrator wants to automate the backup of the RDS database and the EC2 instance configuration. What is the MOST efficient way to achieve this?
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
✓
Use AWS Backup to create backup plans that include the RDS instance and EC2 instance, and copy backups to the secondary region.
AWS Backup provides a centralized, automated backup service that can back up RDS databases (with automated backups) and EC2 instances (via AMIs). It supports cross-region copy, making it ideal for disaster recovery. Option A is wrong because storing database dump files and scripts in S3 is not a fully automated or integrated solution; it requires custom scripting and does not capture incremental changes efficiently. Option B is wrong because manual snapshots require manual intervention and are not automated. Option C is wrong because the CloudFormation template only captures infrastructure configuration, not the database data or EC2 instance state.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use S3 to store database dump files and instance configuration scripts.
Why it's wrong here
Storing database dumps and configuration scripts in S3 is a manual, DIY approach that requires custom tooling to export the database, upload files, and handle restore. It does not leverage AWS Backup's native integration with RDS or EC2, and it fails to capture point-in-time recovery or instance state such as installed software and running services. This approach introduces significant operational overhead and is prone to missing data or inconsistencies, making it unsuitable as a comprehensive disaster recovery strategy.
- ✗
Create manual snapshots of the RDS database and EC2 instance every day and copy them to the secondary region.
Why it's wrong here
Creating manual snapshots of RDS and EC2 instances every day requires an operator to trigger and monitor the snapshot process and then separately copy each snapshot to the secondary region, which is error-prone and not scalable. Unlike AWS Backup, manual snapshots do not provide a centralized backup plan, automated scheduling, retention rules, or automatic cross-region replication. This approach relies on continuous human intervention and lacks the reliability and consistency needed for ongoing disaster recovery.
- ✗
Store the CloudFormation template in S3 and use it to recreate the stack in the secondary region.
Why it's wrong here
A CloudFormation template defines the infrastructure architecture (resources, properties, and dependencies) but contains no runtime data, database contents, or EC2 instance state. Recreating the stack in the secondary region provisions new empty resources, but it cannot restore application data, installed configurations, or OS-level changes that exist on the original instances. Therefore, the template must be combined with data backup mechanisms, and by itself it does not satisfy recovery of actual data or instance state.
- ✓
Use AWS Backup to create backup plans that include the RDS instance and EC2 instance, and copy backups to the secondary region.
Why this is correct
AWS Backup provides a fully managed, policy-based backup solution that can target both RDS instances and EC2 instances (via Amazon Machine Images) within a single backup plan. You can schedule automated backups, apply retention and lifecycle policies, and configure cross-region replication to the secondary region, ensuring consistent disaster recovery without custom scripting or manual snapshots. This is the most efficient and reliable approach because it centralizes backup management and automates the entire DR copy process.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This SOA-C02 question is part of Courseiva's 247-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 SOA-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 SOA-C02 exam.