Where Should EC2 Instances Sit for Separate Power and Networking?
A company wants its Amazon EC2 instances to be in different locations but share the same geographic area. The company also wants to use multiple power grids and independent networking connectivity for the EC2 instances. Which solution meets these requirements?
Community Votes
100% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
It tests the definition of an Availability Zone versus an edge location, and the trap is assuming any AWS "location" can host EC2 instances.
This CLF-C02 question tests whether you can separate EC2 placement into distinct locations inside one geographic area while keeping independent power and network paths. The correct design is multiple Availability Zones in the same AWS Region, because each AZ is a physically separate location with its own power, cooling, and networking.
The most common wrong pick is edge locations, because they are also described as separate AWS locations — but edge locations serve content delivery (CloudFront), not general-purpose EC2 instance hosting.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The requirement has three parts: different locations, one shared geographic area, and independent power plus networking. Multiple Availability Zones in a single AWS Region satisfy all three at once. An AZ is a distinct, isolated location inside a Region, with its own power, cooling, and network connectivity, and EC2 instances can be launched into whichever AZ you choose. Because the AZs sit inside one Region, they remain in the same geographic area, exactly matching the wording of the scenario. Pairing instances across AZs is also the standard AWS resilience pattern for surviving a single-AZ outage.
Why the Other Options Are Wrong
Edge locations are points of presence used by services such as Amazon CloudFront to cache content close to users; they are not a general EC2 placement target. Amazon Connect is a cloud contact-center service, not a location type, so "Amazon Connect locations" cannot host EC2 instances. AWS Artifact is a self-service portal for compliance reports and agreements, again with nothing to do with where compute runs. Only Availability Zones describe physically separated facilities within one AWS Region.
Community Comment Notes
ShaiTay and HappyG both land on B without hesitation. AravindrajG gives the clearest reasoning, noting that "Different locations indicates AZ" while "same geographic area indicates Single AWS Region," and adds that independent networking maps to each AZ using its own subnets. That breakdown matches the official AWS definition of Regions and Availability Zones and confirms why the other location types in the options cannot apply.
exam_strategy placeholder:
Official Reference
Exam Strategy
When a question mentions "different locations but the same geographic area," translate that immediately into multiple Availability Zones inside one Region. Then eliminate any option naming a service that is not a placement target, such as edge locations, Amazon Connect, or AWS Artifact.
Frequently Asked Questions
Why can't edge locations host the company's EC2 instances?
Edge locations are CloudFront points of presence for caching content near users, not general compute placement targets. Only Availability Zones inside a Region host EC2 instances.
Do Availability Zones in one Region share power and networking?
No. Each AZ has independent power, cooling, and network connectivity, which is why spreading EC2 instances across AZs satisfies the independent infrastructure requirement.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →