- A
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
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
Forward the Authorization header to the origin for all static asset requests.
Why wrong: 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
Set the cache TTL to zero so browsers always revalidate content.
Why wrong: 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
Store the static assets in Amazon EFS so CloudFront can cache them more effectively.
Why wrong: 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.
SAA-C03 Design Cost-Optimized Architectures Practice Question
This SAA-C03 practice question tests your understanding of design cost-optimized architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: cloudFront cache keys determine cache entry uniqueness.. 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 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
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Create a separate CloudFront behavior for static assets with a cache policy and origin request policy that exclude the Authorization header.
Option A is correct because creating a separate CloudFront behavior for static assets allows you to attach a cache policy and an origin request policy that explicitly exclude the Authorization header. By not forwarding the Authorization header to the S3 origin, CloudFront can treat all requests for the same asset as cache hits, regardless of the header value, which restores the cache hit ratio and reduces origin load.
Key principle: CloudFront cache keys determine cache entry uniqueness.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a separate CloudFront behavior for static assets with a cache policy and origin request policy that exclude the Authorization header.
Why this is correct
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.
Related concept
CloudFront cache keys determine cache entry uniqueness.
- ✓
Use hashed or versioned object names and long Cache-Control max-age values for immutable assets.
Why this is correct
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.
Related concept
CloudFront cache keys determine cache entry uniqueness.
- ✗
Forward the Authorization header to the origin for all static asset requests.
Why it's wrong here
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.
- ✗
Set the cache TTL to zero so browsers always revalidate content.
Why it's wrong here
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.
- ✗
Store the static assets in Amazon EFS so CloudFront can cache them more effectively.
Why it's wrong here
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 traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think forwarding the Authorization header is necessary for security or that setting TTL to zero is a safe fallback, but both actions actually increase origin load and degrade cache performance for public static assets.
Detailed technical explanation
How to think about this question
CloudFront uses the cache key (which includes headers, query strings, and cookies defined in the cache policy) to determine whether a request is a cache hit. When the Authorization header is included in the cache key by default, each unique token or value creates a separate cached object, even for identical public assets. By using an origin request policy to strip the Authorization header before the request reaches S3, and a cache policy that excludes it from the cache key, CloudFront can serve the same cached object to all users, dramatically improving the cache hit ratio.
KKey Concepts to Remember
- CloudFront cache keys determine cache entry uniqueness.
- Unnecessary headers in the cache key reduce cache hit ratio.
- CloudFront behaviors allow granular cache policy configuration.
- Origin request policies control headers forwarded to the origin.
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
CloudFront cache keys determine cache entry uniqueness.
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 cloudFront cache keys determine cache entry uniqueness., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design Cost-Optimized Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Cost-Optimized 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 Cost-Optimized Architectures — This question tests Design Cost-Optimized Architectures — CloudFront cache keys determine cache entry uniqueness..
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. — Option A is correct because creating a separate CloudFront behavior for static assets allows you to attach a cache policy and an origin request policy that explicitly exclude the Authorization header. By not forwarding the Authorization header to the S3 origin, CloudFront can treat all requests for the same asset as cache hits, regardless of the header value, which restores the cache hit ratio and reduces origin load.
What should I do if I get this SAA-C03 question wrong?
Review cloudFront cache keys determine cache entry uniqueness., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
CloudFront cache keys determine cache entry uniqueness.
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.