SAA-C03 Design Secure Architectures Practice Question
A backup process restores a 2 TB production database from an EBS snapshot onto a new volume. During the first hours after restore, the application sees slow reads whenever previously unused blocks are accessed. What is the best way to avoid this performance issue in future restores?
⚠ Common exam trap
Many candidates think increasing volume size or switching to a different storage class will fix the lazy hydration delay, but only Fast Snapshot Restore directly addresses the root cause by pre-initializing the data blocks.
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
✓
Enable Fast Snapshot Restore on the snapshots used for recovery.
When an EBS volume is restored from a snapshot, it is lazily loaded from Amazon S3 in the background. Accessing data blocks that have not yet been loaded triggers a read penalty because the volume must fetch them from S3 before serving the I/O. Enabling Fast Snapshot Restore (FSR) pre-warms the snapshot data so that restored volumes have full performance immediately, eliminating the slow reads on first access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the volume size to give the database more free space.
Why it's wrong here
A larger volume can help with capacity planning, but it does not prevent the initial read latency caused by lazy loading from a snapshot. The problem is about first-access performance, not storage exhaustion. Expanding the volume changes available space, but it does not pre-initialize blocks that have not yet been read.
When this WOULD be correct
A scenario where the database is running out of storage space and experiencing performance degradation due to insufficient IOPS or throughput, and increasing volume size would also increase the volume's baseline performance.
- ✓
Enable Fast Snapshot Restore on the snapshots used for recovery.
Why this is correct
Fast Snapshot Restore removes the initial performance penalty that occurs when a restored EBS volume reads blocks that have not yet been hydrated. By pre-warming the snapshot data in the target AZ, it helps ensure consistent read performance immediately after restore. This is especially valuable for databases and other workloads that must recover quickly without waiting for the background hydration process.
- ✗
Move the database files to Amazon EFS after the restore completes.
Why it's wrong here
EFS is a shared file system, not a block storage service for database volumes. It is not the right fit for a database that expects EBS-style block semantics and consistent low-latency storage behavior. Switching to EFS would change the storage model and could hurt database performance and compatibility.
When this WOULD be correct
A scenario where the application requires shared access to the database files across multiple EC2 instances, or where the database needs to be accessed from different Availability Zones for high availability, and the performance impact of snapshot hydration is acceptable or mitigated by other means.
- ✗
Use magnetic standard volumes because they avoid snapshot hydration delays.
Why it's wrong here
Magnetic volumes are legacy and far slower than modern EBS SSD volume types. They are not a performance solution for database workloads and would likely make the situation worse. The issue is not the volume family alone; it is the first-read penalty after snapshot restore, which requires a recovery-focused feature instead.
When this WOULD be correct
A question asks for the most cost-effective storage for a large, sequential-access data warehouse that is rarely accessed and can tolerate lower IOPS. Magnetic volumes would be correct due to their low cost per GB.
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.
✓Enable Fast Snapshot Restore on the snapshots used for recovery.Correct answer▾
Why this is correct
Fast Snapshot Restore removes the initial performance penalty that occurs when a restored EBS volume reads blocks that have not yet been hydrated. By pre-warming the snapshot data in the target AZ, it helps ensure consistent read performance immediately after restore. This is especially valuable for databases and other workloads that must recover quickly without waiting for the background hydration process.
✗Increase the volume size to give the database more free space.Wrong answer — click to see why▾
Why this is wrong here
Increasing volume size does not address the 'first touch' latency caused by lazy loading of data from snapshot to S3; it only provides more storage capacity.
★ When this WOULD be the correct answer
A scenario where the database is running out of storage space and experiencing performance degradation due to insufficient IOPS or throughput, and increasing volume size would also increase the volume's baseline performance.
Why candidates choose this
Candidates may think larger volumes inherently perform better or that more free space reduces fragmentation, but the issue is specifically about snapshot hydration delays, not capacity.
✗Move the database files to Amazon EFS after the restore completes.Wrong answer — click to see why▾
Why this is wrong here
Moving database files to Amazon EFS after restore does not address the slow reads caused by lazy loading of data from EBS snapshots (snapshot hydration). EFS is a network file system with its own performance characteristics and does not eliminate the need to initialize EBS blocks.
★ When this WOULD be the correct answer
A scenario where the application requires shared access to the database files across multiple EC2 instances, or where the database needs to be accessed from different Availability Zones for high availability, and the performance impact of snapshot hydration is acceptable or mitigated by other means.
Why candidates choose this
Candidates may think that using a different storage service like EFS, which is fully managed and scalable, could bypass the EBS snapshot hydration issue, not realizing that the problem is specific to EBS volumes restored from snapshots.
✗Use magnetic standard volumes because they avoid snapshot hydration delays.Wrong answer — click to see why▾
Why this is wrong here
Magnetic standard volumes (st1/sc1) also suffer from snapshot hydration delays and have lower baseline performance than gp2/gp3, making them unsuitable for avoiding slow reads on previously unused blocks.
★ When this WOULD be the correct answer
A question asks for the most cost-effective storage for a large, sequential-access data warehouse that is rarely accessed and can tolerate lower IOPS. Magnetic volumes would be correct due to their low cost per GB.
Why candidates choose this
Candidates may think that older, simpler technology (magnetic) avoids the 'hydration' issue because they misunderstand that all EBS snapshots lazily restore blocks, regardless of volume type.
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?”
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 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 →
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.