Question 1,013 of 1,040
Design High-Performing ArchitecturesmediumMultiple SelectObjective-mapped

SAA-C03 Design High-Performing Architectures Practice Question

This SAA-C03 practice question tests your understanding of design high-performing architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: versioned object names create unique URLs for each content change.. 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 marketing site serves versioned JavaScript and CSS files from Amazon S3 through CloudFront. Origin bandwidth costs are rising because CloudFront keeps revalidating objects and fetching too much content from the bucket. Which two changes most directly improve cache hit ratio and reduce origin load? Select two.

Question 1mediummulti select
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

Use versioned object names and long cache TTLs for immutable assets.

Option A is correct because using versioned object names (e.g., app-v1.js, app-v2.js) combined with long cache TTLs (e.g., one year) tells CloudFront that these assets are immutable. Once cached, CloudFront never revalidates them, eliminating origin requests for unchanged files. This directly reduces origin bandwidth costs by preventing unnecessary fetches from S3.

Key principle: Versioned object names create unique URLs for each content change.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use versioned object names and long cache TTLs for immutable assets.

    Why this is correct

    Versioned file names let you cache content aggressively because each new build gets a new URL and does not overwrite the old one.

    Related concept

    Versioned object names create unique URLs for each content change.

  • Forward all cookies and query strings so each request is treated as unique.

    Why it's wrong here

    Forwarding everything usually lowers cache hit ratio because CloudFront sees more unique cache keys and reuses objects less often.

  • Configure a cache policy that excludes unnecessary cookies, query strings, and headers.

    Why this is correct

    A focused cache policy keeps the cache key small, so CloudFront can reuse the same cached object across more viewer requests.

    Related concept

    Versioned object names create unique URLs for each content change.

  • Switch the bucket to S3 Intelligent-Tiering to reduce CloudFront origin requests.

    Why it's wrong here

    Intelligent-Tiering can reduce storage cost, but it does not improve CloudFront cache behavior or reduce origin fetch frequency.

  • Add more NAT Gateways to improve the speed of CloudFront origin fetches.

    Why it's wrong here

    CloudFront does not use your VPC NAT Gateways for origin caching behavior, so this does not address the problem.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates confuse S3 storage classes (like Intelligent-Tiering) with caching performance, or think that increasing network throughput (NAT Gateways) can fix a cache miss problem, when the real solution lies in optimizing cache keys and TTLs.

Detailed technical explanation

How to think about this question

CloudFront's default behavior is to cache based on the URL and specified cache keys. By using versioned filenames, you can safely set a Cache-Control: max-age=31536000, immutable header, which tells browsers and CloudFront to never revalidate. Under the hood, CloudFront uses the Cache-Control and Expires headers to determine TTL; without the immutable directive, CloudFront sends an If-Modified-Since or If-None-Match request to S3 even for cached objects, incurring S3 GET request charges. In real-world scenarios, marketing sites with frequent deployments benefit from this pattern by reducing origin load by over 90%.

KKey Concepts to Remember

  • Versioned object names create unique URLs for each content change.
  • Long cache TTLs allow CloudFront to cache immutable objects aggressively.
  • CloudFront uses the full URL as part of its cache key.
  • Aggressive caching with versioning reduces origin revalidation and fetches.

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

Versioned object names create unique URLs for each content change.

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.

Review versioned object names create unique URLs for each content change., then practise related SAA-C03 questions on the same topic to reinforce the concept.

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 High-Performing Architectures — This question tests Design High-Performing Architectures — Versioned object names create unique URLs for each content change..

What is the correct answer to this question?

The correct answer is: Use versioned object names and long cache TTLs for immutable assets. — Option A is correct because using versioned object names (e.g., app-v1.js, app-v2.js) combined with long cache TTLs (e.g., one year) tells CloudFront that these assets are immutable. Once cached, CloudFront never revalidates them, eliminating origin requests for unchanged files. This directly reduces origin bandwidth costs by preventing unnecessary fetches from S3.

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

Review versioned object names create unique URLs for each content change., then practise related SAA-C03 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Versioned object names create unique URLs for each content change.

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

Keep practising

More SAA-C03 practice questions

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.