EBS Snapshots for Cross-Region Disaster Recovery
A company runs a stateful analytics workload on EC2 instances that use EBS volumes. The data must be restorable in another Region after a major outage, with frequent point-in-time recovery. Which approach provides the most suitable replication mechanism for the EBS-backed data?
Quick Answer
The correct approach relies on EBS snapshots because they are, by design, point-in-time captures of a volume's data, and AWS's cross-Region snapshot copy feature lets those captures be duplicated into another Region so a full, independent copy of the data exists there before any outage occurs. Scheduling these snapshots on a recurring basis is what satisfies the frequent-point-in-time-recovery requirement, since each new snapshot becomes another restore point, and doing the copy into the target Region ahead of time means recovery doesn't depend on any cross-Region operation happening during the outage itself, only a straightforward restore from an already-present snapshot. This is the right mechanism specifically because the workload is stateful and EBS-backed: the durability and consistency guarantees that matter here live at the block-storage layer, not somewhere that could be recreated some other way, like re-deploying compute or replicating an application-level cache. The approach also scales cleanly with recovery point objectives, since more frequent snapshots simply mean less data lost between the last snapshot and the outage. When a scenario asks for regional disaster recovery of EBS-backed data with recurring recovery points, that combination of point-in-time capture and copying into another Region is the cue to reach for scheduled snapshots with cross-Region copy rather than a live replication technology built for a different storage type.
⚠ Common exam trap
Candidates often confuse EBS multi-attach (which is for high availability within a single AZ) with cross-Region replication, or mistakenly think instance store provides durability for long-term data recovery.
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 scheduled EBS snapshots and copy them to another Region, then restore the volumes from those snapshots during recovery.
Scheduled EBS snapshots provide point-in-time backups of EBS volumes, which can be copied to another Region using the cross-Region snapshot copy feature. During recovery, you restore volumes from those snapshots in the target Region, ensuring the data is restorable after a major outage. This approach meets the requirements for frequent point-in-time recovery and cross-Region durability.
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 scheduled EBS snapshots and copy them to another Region, then restore the volumes from those snapshots during recovery.
Why this is correct
Snapshotting and cross-Region copying gives point-in-time images of EBS volumes that can be restored in the target Region.
- ✗
Enable EBS multi-attach to spread the workload across AZs and replicate snapshots automatically between Regions.
Why it's wrong here
Multi-attach increases concurrent access within certain designs but does not replicate data between Regions.
When this WOULD be correct
An exam question requiring high availability for a clustered application (e.g., a shared file system) within a single AZ, where multiple EC2 instances need concurrent read/write access to the same EBS volume, and the question asks for the feature that enables this.
- ✗
Use RDS read replicas in another Region and keep the analytics dataset in an RDS instance only.
Why it's wrong here
RDS replicas address database workloads, not EBS volume snapshots for existing EC2-backed storage.
When this WOULD be correct
A company runs a web application using Amazon RDS for MySQL and needs to offload read traffic to a secondary Region for low-latency queries. RDS read replicas in another Region would be the correct answer for read scaling and cross-Region disaster recovery.
- ✗
Rely on instance store for durability and copy only AMIs across Regions.
Why it's wrong here
Instance store is not reliable durable storage, and copying AMIs alone does not capture EBS volume data.
When this WOULD be correct
For a stateless workload where only the AMI (OS and application) needs to be available in another Region for disaster recovery, and the data is stored externally (e.g., in S3 or a database).
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Create scheduled EBS snapshots and copy them to another Region, then restore the volumes from those snapshots during recovery.Correct answer▾
Why this is correct
Snapshotting and cross-Region copying gives point-in-time images of EBS volumes that can be restored in the target Region.
✗Enable EBS multi-attach to spread the workload across AZs and replicate snapshots automatically between Regions.Wrong answer — click to see why▾
Why this is wrong here
EBS multi-attach allows attaching a volume to multiple EC2 instances in the same AZ, but it does not replicate snapshots across Regions or provide cross-Region disaster recovery. It is designed for clustered applications within a single AZ, not for multi-Region replication.
★ When this WOULD be the correct answer
An exam question requiring high availability for a clustered application (e.g., a shared file system) within a single AZ, where multiple EC2 instances need concurrent read/write access to the same EBS volume, and the question asks for the feature that enables this.
Why candidates choose this
Candidates may confuse 'multi-attach' with cross-Region replication, or think that spreading across AZs implies automatic cross-Region backup, not realizing multi-attach is limited to one AZ and does not handle snapshots.
✗Use RDS read replicas in another Region and keep the analytics dataset in an RDS instance only.Wrong answer — click to see why▾
Why this is wrong here
RDS read replicas are for relational databases, not for analytics workloads on EC2 with EBS volumes. The question specifies EBS-backed data, not RDS-managed data, so using RDS would require migrating the dataset and does not replicate EBS snapshots.
★ When this WOULD be the correct answer
A company runs a web application using Amazon RDS for MySQL and needs to offload read traffic to a secondary Region for low-latency queries. RDS read replicas in another Region would be the correct answer for read scaling and cross-Region disaster recovery.
Why candidates choose this
Candidates may confuse cross-Region replication capabilities of RDS with the need to replicate EBS data, assuming RDS can handle any analytics workload, or they may overlook that the question explicitly mentions EBS volumes and EC2 instances.
✗Rely on instance store for durability and copy only AMIs across Regions.Wrong answer — click to see why▾
Why this is wrong here
Instance store volumes are ephemeral and lose data on instance stop/termination, making them unsuitable for durable, restorable data. Copying AMIs does not replicate the analytics data itself.
★ When this WOULD be the correct answer
For a stateless workload where only the AMI (OS and application) needs to be available in another Region for disaster recovery, and the data is stored externally (e.g., in S3 or a database).
Why candidates choose this
Candidates may confuse instance store with EBS, or think that AMI copying provides data replication, overlooking the ephemeral nature of instance store.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-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 →
Same concept, more angles
1 more way this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company runs a stateful analytics workload on EC2 instances that use EBS volumes. The data must be restorable in another Region after a major outage, with frequent point-in-time recovery. Which approach provides the most suitable replication mechanism for the EBS-backed data?
medium- ✓ A.Create scheduled EBS snapshots and copy them to another Region, then restore the volumes from those snapshots during recovery.
- B.Enable EBS multi-attach to spread the workload across AZs and replicate snapshots automatically between Regions.
- C.Use RDS read replicas in another Region and keep the analytics dataset in an RDS instance only.
- D.Rely on instance store for durability and copy only AMIs across Regions.
Why A: Scheduled EBS snapshots provide point-in-time recovery and can be copied to another Region for cross-region disaster recovery. When a major outage occurs, you can restore EBS volumes from those snapshots in the target Region, meeting the requirement for frequent restorable backups. This approach is native to AWS, cost-effective, and supports the stateful analytics workload without architectural changes.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 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 SAA-C03 exam.