mediummulti selectObjective-mapped

A marketing site serves versioned JavaScript and CSS files from an Amazon S3 origin through Amazon CloudFront. After a frontend release, the CloudFront cache hit ratio dropped because browsers now send an Authorization header on every static asset request even though the assets are public and do not require authentication. The team wants to lower origin load and improve cache efficiency. Which two actions should it take? Select two.

Question 1mediummulti select
Full question →

A marketing site serves versioned JavaScript and CSS files from an Amazon S3 origin through Amazon CloudFront. After a frontend release, the CloudFront cache hit ratio dropped because browsers now send an Authorization header on every static asset request even though the assets are public and do not require authentication. The team wants to lower origin load and improve cache efficiency. Which two actions should it take? 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 separate CloudFront behavior for static assets with a cache policy and origin request policy that exclude the Authorization header.

CloudFront cache efficiency depends on the cache key. If Authorization is included in the cache key or forwarded unnecessarily to the origin, each request can be treated as unique and the cache hit ratio drops. A dedicated behavior for immutable static content should use a cache policy that does not include Authorization and an origin request policy that does not forward it, so the same object can be reused across many viewers.

B

Best answer

Use hashed or versioned object names and long Cache-Control max-age values for immutable assets.

Versioned filenames such as app.3f2c1.js let the team cache aggressively because a new release changes the object name instead of overwriting the old file. Adding a long TTL and immutable-style caching headers reduces revalidation and repeated origin fetches, which improves edge cache reuse and lowers S3 origin traffic.

C

Distractor review

Forward the Authorization header to the origin for all static asset requests.

Forwarding Authorization for public assets makes the request context more specific than necessary and can fragment cache entries. That increases origin requests and reduces the chance that CloudFront can serve the object from cache.

D

Distractor review

Set the cache TTL to zero so browsers always revalidate content.

A zero TTL forces frequent revalidation and pushes more requests back to the origin. That increases latency and origin cost, which is the opposite of what the team wants for versioned static content.

E

Distractor review

Store the static assets in Amazon EFS so CloudFront can cache them more effectively.

Amazon EFS does not solve the cache-key problem and is not a cost-effective origin for public web assets. The issue is header variance in CloudFront, not the file system behind the origin.

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: Create a separate CloudFront behavior for static assets with a cache policy and origin request policy that exclude the Authorization header. — The best fixes are to remove Authorization from the cache path for public static files and to make the assets immutable through versioned names with long-lived cache headers. That combination lets CloudFront reuse edge objects across viewers and avoids unnecessary requests to the S3 origin. Because the assets are public and versioned, per-request authorization context adds cost without adding value. Forwarding Authorization increases cache fragmentation. Setting TTL to zero forces more origin revalidation. EFS is not a practical origin optimization for this use case. The right answer reduces cache-key variance and makes the assets safe to cache for a long time.

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.