- A
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
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
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
Enable CloudFront compression and configure the origin to return Cache-Control: no-store for all files.
Why wrong: 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
Forward all viewer headers to the origin so CloudFront can personalize every request.
Why wrong: 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.
SAA-C03 Design High-Performing Architectures Practice Question
This SAA-C03 practice question tests your understanding of design high-performing architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: versioned filenames enable long TTLs for static assets.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
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
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Rename each static asset with a content hash or release version in the filename before publishing.
Option A is correct because renaming static assets with a content hash or version in the filename ensures that each new release creates a unique object key in S3. This allows CloudFront to treat the new file as a distinct object, avoiding cache invalidation issues and enabling long-term caching of the old version. Without this, even with cache-busting query strings, CloudFront might still serve stale content or require frequent invalidations, reducing the cache hit ratio.
Key principle: Versioned filenames enable long TTLs for static assets.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Rename each static asset with a content hash or release version in the filename before publishing.
Why this is correct
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.
Related concept
Versioned filenames enable long TTLs for static assets.
- ✓
Create a CloudFront cache policy that excludes unnecessary query strings and cookies from the cache key.
Why this is correct
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.
Related concept
Versioned filenames enable long TTLs for static assets.
- ✓
Use an origin request policy that forwards only the headers and cookies the origin truly needs.
Why this is correct
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.
Related concept
Versioned filenames enable long TTLs for static assets.
- ✗
Enable CloudFront compression and configure the origin to return Cache-Control: no-store for all files.
Why it's wrong here
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.
- ✗
Forward all viewer headers to the origin so CloudFront can personalize every request.
Why it's wrong here
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 traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse origin request policies (which control what is sent to the origin) with cache policies (which control the cache key), leading them to think forwarding headers or cookies to the origin will improve caching, when in fact it can harm the cache hit ratio if those values are included in the cache key.
Detailed technical explanation
How to think about this question
CloudFront uses the cache key (a combination of the object URL, query strings, headers, and cookies as defined by the cache policy) to determine if a cached response can be served. By excluding unnecessary query strings and cookies from the cache key (Option B), CloudFront can serve the same cached object to multiple requests that differ only in those ignored parameters. An origin request policy (Option C) controls what is forwarded to the origin but does not affect the cache key, so it must be paired with a cache policy to avoid cache misses caused by varying headers or cookies.
KKey Concepts to Remember
- Versioned filenames enable long TTLs for static assets.
- Content hashes in filenames ensure unique URLs for unique content.
- New releases automatically fetch new files due to changed filenames.
- Eliminates the need for cache-busting query strings.
TExam Day Tips
- 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.
Key takeaway
Versioned filenames enable long TTLs for static assets.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review versioned filenames enable long TTLs for static assets., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design High-Performing Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design High-Performing Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design High-Performing Architectures — This question tests Design High-Performing Architectures — Versioned filenames enable long TTLs for static assets..
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. — Option A is correct because renaming static assets with a content hash or version in the filename ensures that each new release creates a unique object key in S3. This allows CloudFront to treat the new file as a distinct object, avoiding cache invalidation issues and enabling long-term caching of the old version. Without this, even with cache-busting query strings, CloudFront might still serve stale content or require frequent invalidations, reducing the cache hit ratio.
What should I do if I get this SAA-C03 question wrong?
Review versioned filenames enable long TTLs for static assets., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Versioned filenames enable long TTLs for static assets.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
Last reviewed: Jun 11, 2026
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.