mediummultiple choiceObjective-mapped

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?

Question 1mediummultiple choice
Full 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?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Increase the volume size to give the database more free space.

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.

B

Best answer

Enable Fast Snapshot Restore on the snapshots used for recovery.

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.

C

Distractor review

Move the database files to Amazon EFS after the restore completes.

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.

D

Distractor review

Use magnetic standard volumes because they avoid snapshot hydration delays.

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 trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

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. — Fast Snapshot Restore is designed for exactly this scenario. When an EBS volume is restored from a snapshot, blocks may be loaded on demand, causing slow reads the first time data is accessed. Enabling Fast Snapshot Restore in the relevant Availability Zone pre-warms the snapshot so the volume behaves consistently right after recovery. That makes it a strong fit for databases and other latency-sensitive workloads that cannot tolerate slow initial reads. Why others are wrong: Increasing size does not solve the lazy-loading penalty. EFS is the wrong storage model for a database volume that needs block storage behavior. Magnetic volumes are outdated and significantly slower, so they do not address the performance problem and can degrade it further. The key issue is initial block hydration after snapshot restore, which Fast Snapshot Restore is built to solve.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.