Which AWS Service Provides More Consistent Bandwidth Than the Public Internet?

Why the Answer Is Correct

AWS Direct Connect provides a dedicated, private network connection between an on-premises data center, office, or colocation facility and AWS, bypassing the public internet entirely. Because the traffic does not compete with general internet congestion, Direct Connect is the service AWS documents for increasing bandwidth throughput, reducing network costs, and delivering a more consistent network experience than internet-based connections. The wording of the question maps almost one-to-one onto the AWS Direct Connect value proposition, which is the strongest signal that B is the intended answer. ShaiTay's explanation captures this exactly, describing Direct Connect as something that "establishes a dedicated, private connection between your on-premises data center" and AWS. This also sits under the CLF-C02 network services objective, where Direct Connect is the canonical dedicated-connectivity service.

Why the Other Options Are Wrong

AWS VPN (A) does create an encrypted tunnel to AWS, but that tunnel is carried over the public internet, so bandwidth and latency still vary with internet conditions — the opposite of what the company asked for. Amazon Connect (C) is an omnichannel cloud contact-center service and has nothing to do with network throughput or private connectivity, so it is a pure distractor. Amazon CloudFront (D) is a content delivery network that caches content at edge locations to reduce latency for end users; it improves delivery speed but runs over the public internet and provides no dedicated capacity or throughput guarantee. PT08's reasoning supports this split, noting that Direct Connect "bypasses the public internet, resulting in more consistent network performance and lower latency."

Community Comment Notes

Consensus in the thread is strongly behind B, with 80 votes and multiple detailed explanations; ShaiTay and PT08 both emphasize the dedicated private link and bypass of the public internet, and Tithink explicitly contrasts Direct Connect with CloudFront's CDN caching behavior. Naantje adds the phrasing about reducing network costs and increasing bandwidth throughput that mirrors the AWS documentation. The minority view comes from DigitalSolutionsArchitec, who simply posted "Tis Amazon CloudFront" and chose D, but no technical justification is offered and CloudFront does not provide dedicated bandwidth. Tithink's answer text also references the migration-tools whitepaper URL, confirming the same Direct Connect benefits appear in official AWS material.