hardmulti selectObjective-mapped

A media company serves versioned JavaScript and CSS files from an Amazon S3 origin through CloudFront. After each release, origin requests spike even though the files are public. Browser requests include a tracking cookie, an Authorization header, and a cache-busting query string that the site no longer needs. Which three changes will most improve the CloudFront cache hit ratio without exposing private content? Select three.

Question 1hardmulti select
Full question →

A media company serves versioned JavaScript and CSS files from an Amazon S3 origin through CloudFront. After each release, origin requests spike even though the files are public. Browser requests include a tracking cookie, an Authorization header, and a cache-busting query string that the site no longer needs. Which three changes will most improve the CloudFront cache hit ratio without exposing private content? Select three.

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

Rename each static asset with a content hash or release version in the filename before publishing.

Versioned filenames let CloudFront cache each asset for a long time without worrying about stale content. When the file name changes on release, clients naturally fetch the new object, and old cached objects remain valid for older pages until they expire.

B

Best answer

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

If query strings and cookies are not part of the asset identity, keeping them out of the cache key prevents CloudFront from storing many duplicate copies of the same file. That directly increases cache reuse for identical assets requested with different viewer metadata.

C

Best answer

Use an origin request policy that forwards only the headers and cookies the origin truly needs.

Forwarding only required viewer values keeps the cache key smaller and avoids unnecessary origin variation. For public static content, the origin usually does not need Authorization or tracking cookies, so stripping them from origin requests improves cacheability and reduces origin load.

D

Distractor review

Enable CloudFront compression and configure the origin to return Cache-Control: no-store for all files.

Compression can help transfer size, but no-store tells CloudFront and browsers not to cache the objects. That would worsen origin fetches rather than improve the hit ratio, especially for immutable static assets.

E

Distractor review

Forward all viewer headers to the origin so CloudFront can personalize every request.

Forwarding every header makes the cache key highly fragmented and usually reduces hit ratio sharply. Static JavaScript and CSS files should be cached by content identity, not by per-user metadata that the origin does not need.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

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?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Rename each static asset with a content hash or release version in the filename before publishing. — CloudFront performs best for static assets when the cache key is stable and the objects are versioned. Hashing filenames lets you use long TTLs safely because each release becomes a new object name. Excluding unnecessary query strings, cookies, and headers prevents needless cache fragmentation, while forwarding only required values keeps origin requests lean. Together, these changes maximize reuse of already cached assets without exposing private content or relying on stale data. Compression is useful for transfer efficiency, but no-store disables caching and hurts performance. Forwarding all viewer headers causes cache fragmentation and increases origin requests, which is the opposite of the goal. The scenario already says the files are public, so personalization behavior is unnecessary and harmful here.

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.