DVA-C02 Troubleshooting and Optimization Practice Question
A developer is using AWS CloudFront to serve static content. Users in some geographic regions report slow load times. Which CloudFront feature can the developer use to reduce latency for these users?
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
✓
Change the CloudFront price class to include all edge locations.
CloudFront's price class determines which edge locations are used to serve content. By default, CloudFront may use only a subset of edge locations (Price Class 100 or 200) to reduce costs, which can cause higher latency for users in regions not covered. Changing the price class to 'All Edge Locations' (Price Class All) ensures that CloudFront uses every global edge location, providing lower latency for all users. Option B is incorrect because creating multiple origins in different regions addresses origin distance, not edge location coverage. Option C is incorrect because S3 Transfer Acceleration is for speeding up uploads to S3, not for improving CloudFront content delivery. Option D is incorrect because Lambda@Edge can modify content at edge locations but does not expand the set of edge locations used.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Change the CloudFront price class to include all edge locations.
Why this is correct
CloudFront's price classes determine which edge locations are utilized for content delivery. Selecting "Price Class All" ensures that CloudFront leverages its entire global network of edge locations, including those in regions with higher infrastructure costs. This maximizes the geographic proximity of cached content to end-users worldwide, thereby minimizing latency for static content delivery regardless of the user's physical location.
- ✗
Create multiple origins in different regions.
Why it's wrong here
Creating multiple origins in different regions for the *same* static content does not inherently reduce latency for end-users. CloudFront distributions are designed to cache content efficiently at global edge locations from a single origin (or multiple origins for distinct content paths). Introducing redundant origins for identical content would increase operational complexity and management overhead without improving content delivery latency, as CloudFront's primary function is to serve from the nearest edge cache.
- ✗
Enable S3 Transfer Acceleration on the origin S3 bucket.
Why it's wrong here
S3 Transfer Acceleration is a feature specifically designed to speed up data transfers *into* an S3 bucket from clients over long distances, by routing uploads through CloudFront's edge network. It does not, however, affect the speed at which CloudFront retrieves content from the origin S3 bucket or delivers content *from* CloudFront edge locations to end-users. Therefore, enabling it is irrelevant for optimizing the delivery of static content *from* CloudFront to end-users.
- ✗
Use Lambda@Edge to optimize content delivery.
Why it's wrong here
Lambda@Edge allows developers to execute custom code at CloudFront edge locations in response to various CloudFront events, enabling dynamic content manipulation, custom authentication, or intelligent routing decisions. While powerful for adding dynamic logic, it introduces compute overhead and is not primarily designed to reduce latency for serving *static* content directly. For static assets, the fundamental latency reduction comes from efficient caching at edge locations, which Lambda@Edge does not inherently enhance.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
Go deeper
Related to this question
About these practice questions
This DVA-C02 question is part of Courseiva's 1,135-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DVA-C02 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 DVA-C02 exam.