ANS-C01 Network Management and Operations Practice Question
A company is using AWS Global Accelerator to improve performance for a global application. The application uses an Application Load Balancer (ALB) in each region. The network team wants to ensure that traffic is distributed evenly across regions and that failover happens quickly. Which THREE steps should the team take? (Select THREE.)
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure multiple endpoint groups, one per region, and set traffic dials to distribute load
Options A, B, and C are correct. A: Multiple endpoint groups with traffic dials allow distributing traffic across regions based on desired percentages. B: Enabling health checks with a low threshold for failure detection ensures fast failover by quickly marking unhealthy endpoints. C: Setting traffic dials for each endpoint group allows fine-tuning the distribution of traffic. Option D is incorrect because client IP address preservation is not related to traffic distribution or failover; it affects source IP visibility. Option E is incorrect because Route 53 weighted routing is unnecessary; Global Accelerator can handle distribution via endpoint groups and traffic dials.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Configure multiple endpoint groups, one per region, and set traffic dials to distribute load
Why this is correct
Traffic dials control the percentage of traffic to each region.
- ✓
Enable health checks on each endpoint and set a low threshold for failure detection
Why this is correct
Health checks enable fast failover.
- ✓
Set the traffic dial for each endpoint group to a value that reflects the desired distribution
Why this is correct
Traffic dials directly control distribution.
- ✗
Enable client IP address preservation on the Global Accelerator
Why it's wrong here
Client IP preservation does not affect traffic distribution.
- ✗
Use Route 53 weighted routing in front of Global Accelerator
Why it's wrong here
Global Accelerator uses its own routing; Route 53 not needed.
Go deeper
Related to this question
About these practice questions
This ANS-C01 question is part of Courseiva's 1,621-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on ANS-C01
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses AWS Global Accelerator to improve performance for a global application. The application is deployed in two AWS regions behind Network Load Balancers. Users in Asia report high latency even though the accelerator should route them to the nearest endpoint. What is the most likely reason?
medium- ✓ A.The endpoint in the closer region is marked unhealthy
- B.Traffic Dial is set to 100% for the distant region
- C.The accelerator is configured with on-premises endpoints
- D.Client affinity is set to source IP
Why A: If the endpoint in the closer region is marked unhealthy, Global Accelerator will automatically route traffic to the next nearest healthy endpoint, which may be in a distant region, causing high latency. Option B is incorrect because if Traffic Dial were set to 100% for the distant region, traffic would be intentionally routed there, so users would not expect routing to the nearest endpoint. Option C is incorrect because on-premises endpoints are not typical for Global Accelerator, and even if used, they would not cause high latency specifically for Asian users if the closer region has healthy endpoints. Option D is incorrect because client affinity affects stickiness, not overall latency; it would not cause all Asian users to experience high latency.
Variation 2. A company is using AWS Global Accelerator to improve performance for a web application hosted in two AWS Regions. The application uses an Application Load Balancer (ALB) in each region. The company wants to ensure that traffic is directed to the closest healthy endpoint. Which routing configuration should be used?
easy- ✓ A.Global Accelerator endpoint groups with health checks and traffic dials
- B.Global Accelerator with weighted endpoint groups
- C.Route 53 latency-based routing with health checks
- D.Route 53 geolocation routing with Global Accelerator
Why A: Global Accelerator uses anycast IPs to route traffic to the closest healthy endpoint based on latency and health checks. Endpoint groups contain regional endpoints (e.g., ALBs), and health checks ensure only healthy endpoints receive traffic. Traffic dials allow controlling the proportion of traffic sent to each region but are optional. Option B is incorrect because Global Accelerator does not use weighted routing; it uses latency-based routing. Option C is incorrect because Route 53 latency-based routing is a separate service and not the routing configuration for Global Accelerator; Global Accelerator itself handles proximity. Option D is incorrect because Route 53 geolocation routing is not used with Global Accelerator; Global Accelerator automatically routes to the nearest healthy endpoint without geolocation.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ANS-C01 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ANS-C01 exam.