Question 484 of 1,040
Design Secure ArchitecturesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to enable Fast Snapshot Restore on the snapshots used for recovery. This is correct because when you restore an EBS volume from a snapshot, the data is lazily loaded from Amazon S3 in the background, meaning any read request to a block that hasn't been fetched yet forces the volume to pull it from S3 before serving the I/O, causing slow reads. Fast Snapshot Restore pre-warms the snapshot data so restored volumes deliver full performance immediately, eliminating the penalty on first access. On the SAA-C03 exam, this scenario tests your understanding of EBS snapshot mechanics versus pre-warming features; a common trap is to suggest initializing the volume with dd or fio, but FSR is the managed, automated solution. Remember the memory tip: "FSR = Fast, Snappy Restore" — if you want to avoid the lazy load lag, flip on FSR before you restore.

SAA-C03 Design Secure Architectures Practice Question

This SAA-C03 practice question tests your understanding of design secure architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

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?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

  • Clue: "first"

    Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.

Question 1mediummultiple choice
Full question →

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.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

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.

  • 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.

    Clue confirmation

    The clue words "best", "first" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • 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.

  • 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.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may 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.

Trap categories for this question

  • Scenario analysis trap

    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.

Detailed technical explanation

How to think about this question

EBS snapshots are stored incrementally in Amazon S3, and when you create a volume from a snapshot, the data blocks are fetched on demand. Fast Snapshot Restore (FSR) creates a pre-warmed copy of the snapshot data in the Availability Zone, so that new volumes are fully initialized at creation time. FSR is billed per snapshot per AZ per hour, and is ideal for critical recovery scenarios where performance immediately after restore is essential.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SAA-C03 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Design Secure Architectures — This question tests Design Secure Architectures — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: 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.

What should I do if I get this SAA-C03 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "best", "first". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

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.