A SysOps administrator must load test a new Amazon CloudFront distribution to assess data transfer and latency performance. Which solution will meet this requirement?

Sending requests from a single geographic region only tests one CloudFront edge location, which does not represent the global distribution of traffic and skews latency results to one region.

A single geographic region still fails to exercise multiple edge locations, and depending on the cache configuration described, it may not accurately reflect data transfer performance across CloudFront's distributed infrastructure.

While using multiple geographic regions is correct, the cache or client configuration described in option C (likely reusing the same URLs without cache-busting) would result in cached responses being served, obscuring true origin-fetch latency and data transfer metrics.

CloudFront serves content from edge locations closest to the requesting client, so sending requests from multiple geographic regions ensures that different edge locations are exercised, providing accurate latency and data transfer measurements. Additionally, configuring each client to use a unique cache-busting parameter or object prevents cache hits from masking true origin fetch performance, giving a complete picture of end-to-end latency. This approach aligns with AWS best practices for load testing CloudFront distributions to assess real-world performance.