The answer is CloudFront caching with appropriate TTLs. This feature works by configuring a minimum TTL on your CloudFront distribution so that, even after the cached object expires, CloudFront will continue to serve the stale version from its edge locations when the S3 origin is unreachable, rather than returning an error. On the SAA-C03 exam, this scenario tests your understanding of origin failover versus cache behavior—many candidates mistakenly reach for a Lambda@Edge or a secondary origin, but the simplest managed-native solution is to rely on CloudFront’s built-in stale-while-revalidate mechanism. A common trap is thinking you need a custom error response or a separate backup bucket; instead, just set an appropriate minimum TTL (e.g., 0 for dynamic content or longer for static assets) to ensure cached pages are served during short outages. Memory tip: “Stale is safe with a TTL—CloudFront keeps the old page when the origin goes away.”
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: cloudFront caches content at edge locations globally.. 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 content publishing system exposes a static website from S3 and CloudFront. Users should still receive cached pages if the S3 origin has a short outage. Which feature helps most? The architecture review board prefers a managed AWS-native control.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
CloudFront caching with appropriate TTLs
CloudFront caching with appropriate TTLs ensures that even if the S3 origin becomes temporarily unavailable, CloudFront can serve cached content from its edge locations to users. By setting a minimum TTL (e.g., 0 seconds for dynamic content or longer for static assets), CloudFront will continue to serve stale responses from cache during an origin outage, maintaining availability. This is a managed AWS-native feature that requires no additional infrastructure and aligns with the architecture review board's preference.
Key principle: CloudFront caches content at edge locations globally.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
IAM Access Analyzer
Why it's wrong here
Access Analyzer reviews permissions and does not serve cached content.
✗
AWS Backup Vault Lock
Why it's wrong here
Backup Vault Lock protects backups, not CloudFront delivery.
✓
CloudFront caching with appropriate TTLs
Why this is correct
CloudFront can serve cached content from edge locations when the origin is temporarily unavailable.
Related concept
CloudFront caches content at edge locations globally.
✗
S3 Select
Why it's wrong here
S3 Select retrieves subsets of object data and does not increase origin outage tolerance.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates might confuse CloudFront's caching with other AWS services like AWS Global Accelerator or Route 53 health checks, or incorrectly assume that S3's built-in redundancy alone handles origin outages, overlooking CloudFront's ability to serve stale cached content during origin failures.
Detailed technical explanation
How to think about this question
CloudFront's caching behavior is governed by Cache-Control headers from the origin or default TTL settings in the distribution's cache behavior configuration. When the origin is unreachable, CloudFront can serve stale responses if the 'Stale responses' option is enabled (via the 'Minimum TTL' and 'Default TTL' settings), allowing it to return cached objects even after their TTL expires. In a real-world scenario, setting a minimum TTL of 0 seconds with a default TTL of 86400 seconds for static assets ensures that CloudFront refreshes from S3 when available but still serves cached content during short outages, reducing impact on end users.
KKey Concepts to Remember
CloudFront caches content at edge locations globally.
TTL (Time-To-Live) settings control cache duration.
CloudFront can serve stale content if the origin is unavailable.
It acts as a CDN, improving performance and availability.
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
CloudFront caches content at edge locations globally.
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.
Review cloudFront caches content at edge locations globally., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Resilient Architectures — This question tests Design Resilient Architectures — CloudFront caches content at edge locations globally..
What is the correct answer to this question?
The correct answer is: CloudFront caching with appropriate TTLs — CloudFront caching with appropriate TTLs ensures that even if the S3 origin becomes temporarily unavailable, CloudFront can serve cached content from its edge locations to users. By setting a minimum TTL (e.g., 0 seconds for dynamic content or longer for static assets), CloudFront will continue to serve stale responses from cache during an origin outage, maintaining availability. This is a managed AWS-native feature that requires no additional infrastructure and aligns with the architecture review board's preference.
What should I do if I get this SAA-C03 question wrong?
Review cloudFront caches content at edge locations globally., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
CloudFront caches content at edge locations globally.
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 →
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.
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.
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.
Sign in to join the discussion.