How Should You Load Test a New CloudFront Distribution?

SOA-C03 By islever Editorial Last updated

Configure domains, DNS services, and content delivery. Implement and optimize networking features and connectivity.

Short answer

D Send client requests from multiple geographic regions, make each client resolve DNS independently, and spread requests across the returned IPs.

Question

A CloudOps engineer must load test a new Amazon CloudFront distribution to assess data transfer and latency performance.
Which solution will meet this requirement?
  1. Send client requests from a single geographic region. Configure the load test so that each client makes an identical DNS request. Focus the client requests on the IP address that the DNS returns.
  2. Send client requests from a single geographic region. Configure the load test so that each client makes an independent DNS request. Spread the client requests across the set of IP addresses that the DNS returns.
  3. Send client requests from multiple geographic regions. Configure the load test so that each client makes an identical DNS request. Focus the client requests on the IP address that the DNS returns.
  4. Send client requests from multiple geographic regions. Configure the load test so that each client makes an independent DNS request. Spread the client requests across the set of IP addresses that the DNS returns. Correct Answer

Key Takeaways

The exam tests whether you understand that CloudFront uses DNS to return multiple edge IPs and that realistic load testing requires geographic diversity plus independent DNS resolution; the trap is pinning every client to one returned IP.

CloudFront load testing must simulate real global clients by using multiple geographic regions, independent DNS resolution, and spreading requests across all returned edge IP addresses. The correct design is option D, while single-region or pinned-IP tests understate CloudFront's distributed behavior.

Common mistake: A frequent mistake is choosing option C: sending traffic from multiple regions but using an identical DNS request, which pins all clients to a single CloudFront IP and fails to exercise the distribution's full edge footprint.

Expert Analysis

Why the Answer Is Correct

Option D combines the two dimensions that make a CloudFront load test meaningful: clients in multiple geographic regions and independent DNS resolution per client. Independent DNS requests allow each client to receive the set of edge IP addresses that CloudFront DNS currently returns, and spreading requests across that set avoids concentrating load on a single address. This better approximates real global user traffic and exposes latency and data-transfer behavior across CloudFront's distributed edge footprint.

Why the Other Options Are Wrong

Option A is the weakest because it uses one region and an identical DNS request, effectively pinning all test traffic to one returned IP. Option B adds independent DNS resolution and IP spreading but still tests from only one geographic region, so it cannot represent global latency or regional edge selection. Option C uses multiple regions, which is good, but the identical DNS request still focuses clients on one IP and fails to distribute traffic across the returned addresses.

Community Comment Notes

Bad_Mat selected option D and quoted the same design: "Send client requests from multiple geographic regions" with "each client makes an independent DNS request." That aligns with the distributed, DNS-aware testing approach required here. The comment does not add a conflicting interpretation; it reinforces the need to avoid single-region and single-IP assumptions.

Exam Strategy

When a CloudFront question asks about load testing, eliminate choices that use one geographic region or one pinned IP. Real CloudFront traffic is global and DNS returns multiple edge IPs, so the answer must include both geographic diversity and independent DNS resolution.

Official Reference

https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/load-testing.html

This link opens the official vendor documentation in a new tab.

Exam Strategy

For CloudFront load-testing questions, look for both geographic diversity and independent DNS resolution. If an option sends all clients to the same DNS result or uses only one region, it cannot simulate CloudFront's distributed edge behavior.

Frequently Asked Questions

Why must CloudFront load tests use multiple geographic regions?

CloudFront serves users from many edge locations, so a single-region test measures only one path and cannot reveal global latency or data-transfer behavior.

Why is an identical DNS request wrong for CloudFront load testing?

Identical DNS requests can pin all clients to one returned edge IP, so the test measures a single IP instead of exercising CloudFront's full set of edge addresses.

More SOA-C03 FAQ →

Discussion 1 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 1

  1. Bad_Mat 👍 1 Answered D
    Direct AnswerD. Send client requests from multiple geographic regions. Configure the load test so that each client makes an independent DNS request. Spread the client requests across the set of IP addresses that the DNS returns.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Resolving Private IPv4 Exhaustion in AWS VPCs

S-grade

How Do You Ramp ALB Traffic Gradually During EC2 Cache Warm-Up?

S-grade

Avoiding Permanent Credentials with AWS STS

S-grade

Automate EC2 Reboot with Systems Manager Maintenance Windows

S-grade

Practice All SOA-C03 Questions

Access 100 questions with complete answers and detailed explanations.

View Full SOA-C03 Practice Test →

← Back to SOA-C03 Study Guide