- A
Set long cache headers (for example, Cache-Control: max-age and immutable) on those versioned assets so CloudFront caches them longer.
Because the filenames are versioned, each URL is effectively immutable. Longer TTL/max-age cache headers increase the cache hit ratio, so CloudFront serves subsequent requests from edge caches instead of re-fetching from the origin.
- B
Disable compression to reduce CPU time spent at the edge and therefore reduce total cost.
Why wrong: Disabling compression typically increases the amount of data transferred, which can increase latency and overall origin/egress costs rather than reducing CloudFront costs.
- C
Lower the cache policy TTLs so clients always get the newest assets quickly.
Why wrong: Shorter TTLs cause content to expire sooner, increasing cache misses and origin fetches, which usually increases cost and can reduce performance.
- D
Remove version identifiers from filenames so CloudFront caches fewer unique objects.
Why wrong: If files are not versioned, updates require cache invalidations or very short TTLs. That increases revalidation/origin activity and risks users receiving stale assets, which can increase overall origin fetches and operational cost.
Quick Answer
The answer is to set long cache headers like `Cache-Control: max-age=31536000, immutable` on those versioned assets. This is correct because CloudFront respects the origin’s cache-control directives; when a versioned file such as `app.1.4.2.js` is served with a max-age of one year and the `immutable` flag, CloudFront caches that specific object at edge locations for the full duration. Since the filename changes with each new version, CloudFront treats each as a unique object and never re-fetches the old version from the origin, which directly reduces origin fetches and lowers your CloudFront bill. On the SAA-C03 exam, this scenario tests your understanding of how CloudFront caching behavior interacts with HTTP headers and versioned asset strategies—a common trap is to assume that a shorter TTL or invalidation is needed, but versioned filenames eliminate that need entirely. Memory tip: “Versioned name + immutable = cache and forget.”
SAA-C03 Design Cost-Optimized Architectures Practice Question
This SAA-C03 practice question tests your understanding of design cost-optimized architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 website serves versioned JavaScript and CSS files through CloudFront, but origin fetches are still high and the CloudFront bill increased. Developers confirm that URLs include a version in the filename (for example, app.1.4.2.js). What CloudFront behavior/configuration is most likely to reduce origin fetches and associated costs?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
Set long cache headers (for example, Cache-Control: max-age and immutable) on those versioned assets so CloudFront caches them longer.
Setting long cache headers like `Cache-Control: max-age=31536000, immutable` on versioned assets tells CloudFront to cache these objects at edge locations for an extended period. Since the filename changes with each new version, CloudFront treats each version as a unique object and will not re-fetch the old version from the origin, dramatically reducing origin fetches and associated costs.
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.
- ✓
Set long cache headers (for example, Cache-Control: max-age and immutable) on those versioned assets so CloudFront caches them longer.
Why this is correct
Because the filenames are versioned, each URL is effectively immutable. Longer TTL/max-age cache headers increase the cache hit ratio, so CloudFront serves subsequent requests from edge caches instead of re-fetching from the origin.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Disable compression to reduce CPU time spent at the edge and therefore reduce total cost.
Why it's wrong here
Disabling compression typically increases the amount of data transferred, which can increase latency and overall origin/egress costs rather than reducing CloudFront costs.
- ✗
Lower the cache policy TTLs so clients always get the newest assets quickly.
Why it's wrong here
Shorter TTLs cause content to expire sooner, increasing cache misses and origin fetches, which usually increases cost and can reduce performance.
- ✗
Remove version identifiers from filenames so CloudFront caches fewer unique objects.
Why it's wrong here
If files are not versioned, updates require cache invalidations or very short TTLs. That increases revalidation/origin activity and risks users receiving stale assets, which can increase overall origin fetches and operational cost.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think lowering TTLs or removing versioning helps with freshness or cost, but the key insight is that versioned filenames already solve cache invalidation, so extending cache duration is the cost-optimized approach.
Detailed technical explanation
How to think about this question
The `immutable` directive (RFC 8246) tells CloudFront and browsers that the asset will never change for that URL, allowing them to skip conditional revalidation (e.g., `If-None-Match` or `If-Modified-Since`) entirely. In practice, combining a long `max-age` with `immutable` on versioned filenames ensures CloudFront serves the cached copy until the TTL expires, and since the filename changes on each deployment, the old object is never requested again, making origin fetches nearly zero for stable versions.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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.
- →
Design Cost-Optimized Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Cost-Optimized Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
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 Cost-Optimized Architectures — This question tests Design Cost-Optimized Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set long cache headers (for example, Cache-Control: max-age and immutable) on those versioned assets so CloudFront caches them longer. — Setting long cache headers like `Cache-Control: max-age=31536000, immutable` on versioned assets tells CloudFront to cache these objects at edge locations for an extended period. Since the filename changes with each new version, CloudFront treats each version as a unique object and will not re-fetch the old version from the origin, dramatically reducing origin fetches and associated costs.
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: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Last reviewed: Jun 11, 2026
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.