hardmultiple choiceObjective-mapped

Exhibit

CloudFront behavior summary for path pattern /static/*:
- Allowed methods: GET, HEAD
- Cache policy: forwards all query strings
- Origin request policy: forwards all cookies and the Authorization header
- Average cache hit ratio: 11%
Sample request log lines:
GET /static/app.js?v=18&userId=123 Cookie: session=abcd
GET /static/app.js?v=18&userId=987 Cookie: session=xyzt
GET /static/logo.svg?v=18&locale=en Cookie: session=mnop
Origin responses:
- All objects are identical for every viewer
- Objects are versioned only by the v query parameter

Based on the exhibit, which change will most improve the CloudFront cache hit ratio for the static assets while still serving the same files to all users?

Question 1hardmultiple choice
Full question →

Based on the exhibit, which change will most improve the CloudFront cache hit ratio for the static assets while still serving the same files to all users?

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 custom cache policy that includes only the v query string and excludes cookies.

This removes unnecessary cache-key fragmentation. Since all users receive identical static files, forwarding user-specific cookies and irrelevant query strings destroys cache reuse. Keeping only the version parameter preserves correct object variation while allowing many more requests to hit the same cached object at the edge.

B

Distractor review

Enable Origin Shield and keep the current cache behavior unchanged.

Origin Shield can reduce origin load after a miss, but it does not fix a cache key that is fragmented by unnecessary request data.

C

Distractor review

Move the static assets to individual presigned URLs for each viewer.

Presigned URLs are for controlled access, not for improving cache efficiency when the content itself is identical for everyone.

D

Distractor review

Increase the CloudFront default TTL to 24 hours while continuing to forward all cookies and query strings.

A longer TTL helps only after a cacheable object is identified; forwarding user-specific data still creates too many distinct cache entries.

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 custom cache policy that includes only the v query string and excludes cookies. — The exhibit shows that CloudFront is treating nearly every request as a different object because it forwards all cookies and all query strings. For identical static files, the cache key should be as small as possible while still preserving legitimate versioning. A custom cache policy that includes only the v parameter and excludes cookies lets CloudFront reuse cached objects across viewers, which raises the hit ratio and reduces origin traffic. Why others are wrong: Origin Shield can lower the load on the origin after a miss, but it does not increase cache reuse at the edge. Presigned URLs solve access control problems, not cache fragmentation. Extending the TTL alone does little when the cache key remains overly specific, because each user-specific request still produces a separate cached object.

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.