mediummulti selectObjective-mapped

A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles are fetched repeatedly from the origin. Logs show that requests include unneeded query strings and cookies, which prevent cache reuse. Which two changes should the team make to reduce origin traffic and cost? Select two.

Question 1mediummulti select
Full question →

A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles are fetched repeatedly from the origin. Logs show that requests include unneeded query strings and cookies, which prevent cache reuse. Which two changes should the team make to reduce origin traffic and cost? 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

Configure a CloudFront cache policy that forwards only the query strings, headers, and cookies the app actually needs.

Reducing the cache key to only required values increases cache hit ratio and lowers origin fetches. CloudFront can reuse responses more effectively when unnecessary request data is not forwarded.

B

Best answer

Use versioned file names for static assets and set a long TTL for immutable objects.

Versioned filenames let you cache assets aggressively without risking stale content after deployments. Long TTLs reduce repeated origin requests and lower both transfer and request costs.

C

Distractor review

Increase the size of the S3 bucket.

Bucket size does not improve cache reuse or reduce request costs. The issue is cacheability, not storage capacity.

D

Distractor review

Place an Application Load Balancer in front of S3.

An ALB is not used as a front end for static S3 content in this pattern. It adds unnecessary infrastructure and does not address the cache key problem.

E

Distractor review

Disable caching so clients always get the latest files.

Disabling caching guarantees more origin traffic and higher cost. The deployment already uses versioned assets, so cache efficiency should increase rather than disappear.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Configure a CloudFront cache policy that forwards only the query strings, headers, and cookies the app actually needs. — The cost problem is caused by poor cache reuse, not by S3 itself. CloudFront should forward only the request elements the application truly needs so that more requests hit the cache. Versioned filenames let the team safely use long TTLs for immutable assets, which avoids repeated origin fetches after deployments. Those two changes directly reduce data transfer and request charges. Increasing bucket size does nothing for caching. An ALB in front of S3 is the wrong service pattern and adds cost. Disabling caching would make origin traffic worse, which is the opposite of the desired outcome.

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.