mediummulti selectObjective-mapped

A marketing site serves versioned JavaScript and CSS from an Amazon S3 origin through Amazon CloudFront. After each release, the cache hit ratio drops sharply because clients keep sending request headers and query strings that are not needed for asset retrieval. Which two changes should improve cache efficiency the most? Select two.

Question 1mediummulti select
Full question →

A marketing site serves versioned JavaScript and CSS from an Amazon S3 origin through Amazon CloudFront. After each release, the cache hit ratio drops sharply because clients keep sending request headers and query strings that are not needed for asset retrieval. Which two changes should improve cache efficiency the most? Select two.

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

Best answer

Create a CloudFront cache policy that excludes unnecessary headers, query strings, and cookies from the cache key.

CloudFront uses the cache key to decide whether two requests can share the same cached object. If irrelevant headers, query strings, or cookies are included, the same file is cached as many variants and the hit ratio drops.

B

Best answer

Use versioned filenames or content hashes for static assets and apply long-lived immutable caching.

Versioned asset names let you cache files aggressively because each release gets a new URL. That avoids frequent revalidation or invalidation of an object that should never change once published.

C

Distractor review

Move the S3 origin behind an Application Load Balancer so CloudFront can cache responses more effectively.

An ALB is unnecessary for static S3 content and does not improve CloudFront cache reuse for files. It adds complexity without addressing the cache-key fragmentation described in the scenario.

D

Distractor review

Store the objects in Amazon S3 Standard-IA so repeated requests are cheaper.

Storage class changes affect storage cost and retrieval pricing, but they do not change the CloudFront cache hit ratio. The problem is about request variation, not object storage economics.

E

Distractor review

Lower the CloudFront TTL to zero so viewers always receive the newest content immediately.

A zero TTL forces more origin fetches and usually reduces cache hit ratio. That increases origin load and is the opposite of the goal of improving cache efficiency.

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: Create a CloudFront cache policy that excludes unnecessary headers, query strings, and cookies from the cache key. — The highest-impact changes are to shrink the cache key and make the asset URLs immutable. If CloudFront varies the cache key on headers, query strings, or cookies that do not affect the file, it stores many duplicate versions of the same object. Versioned filenames or hashes then allow long TTLs because a new release uses a new URL, so the old and new content do not conflict. Together, these changes maximize cache reuse and stabilize hit ratio after releases. Putting S3 behind an ALB does not address cache fragmentation and is not needed for static content. Changing the S3 storage class does not improve CloudFront cache reuse. Lowering TTL to zero increases origin traffic and usually makes the cache hit ratio worse, which directly conflicts with the objective.

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.