Answer-first summary for fast verification
Answer: Use EC2 instances in a single Availability Zone.
## Explanation To minimize network latency between EC2 instances while not requiring high availability: - **Option A (Correct)**: Using EC2 instances in a single Availability Zone provides the lowest network latency because all instances are within the same data center facility with direct, high-speed network connections between them. - **Option B**: Using multiple edge locations would increase latency as edge locations are geographically distributed CDN points, not designed for inter-instance communication. - **Option C**: Using the same Availability Zone but in different AWS Regions is contradictory - Availability Zones exist within a single AWS Region, not across multiple regions. - **Option D**: Edge locations are part of Amazon CloudFront (CDN) and not where EC2 instances are deployed. EC2 instances run in Availability Zones within AWS Regions. **Key Points**: - Single Availability Zone = lowest network latency - No high availability requirement = single AZ is acceptable - Multiple AZs or regions would increase latency due to geographical separation - Edge locations are for content delivery, not EC2 instance deployment
Author: Ritesh Yadav
Ultimate access to all questions.
No comments yet.
A company wants to minimize network latency between its Amazon EC2 instances. The EC2 instances do not need to be highly available. Which solution meets these requirements?
A
Use EC2 instances in a single Availability Zone.
B
Use EC2 instances in multiple edge locations.
C
Use EC2 instances in the same Availability Zone but in different AWS Regions.
D
Use EC2 instances in the same edge location and the same AWS Region.