A company wants to deploy some of its resources in the AWS Cloud. To meet regulatory requirements, the data must remain local and on premises. There must be low latency between AWS and the company res

Question

Options

• AAWS Local Zones
• BAvailability Zones
• CAWS Outposts
• DAWS Wavelength Zones

• A
  7% (3)
• B
  13% (6)
• C
  78% (35)
• D
  2% (1)

Explanation

AWS Outposts Explanation

AWS Outposts (C) is correct because it physically extends AWS infrastructure, services, and tools to your on-premises data center or facility, allowing you to run AWS compute and storage locally while maintaining compliance with data residency requirements - all with low latency connectivity to the broader AWS cloud.

Why the distractors are wrong:

• AWS Local Zones (A) place AWS infrastructure closer to specific geographic areas, but data still resides in AWS-managed facilities, not on your own premises.
• Availability Zones (B) are distinct data center locations within an AWS Region - they are entirely within AWS infrastructure and have no on-premises component.
• AWS Wavelength Zones (D) embed AWS compute and storage within telecommunications providers' 5G networks to reduce latency for mobile applications, but again, data does not remain on your premises.

Memory Tip: Think of Outposts as AWS literally "posting" (shipping) its hardware out to your location - it's the only option where AWS infrastructure physically lives in your building, making it the go-to answer whenever you see the keywords "on premises" + "regulatory/data residency requirements" + "low latency."

No community discussion yet for this question.