Networking and Content Delivery
RecognitionElastic Load Balancing
Managed load balancing across healthy registered targets for supported application and network traffic.
Key points
- Target health determines whether a registered target receives traffic.
- Deployment strategies can shift or replace target capacity behind a load balancer.
- Developer depth covers application health and release behavior, not load-balancer or network architecture design.
Best-known use cases
- Distribute application traffic across healthy targets.
- Support blue/green or rolling application deployments in existing environments.
What candidates often confuse it with
- A load-balancer health check gates registered-target traffic; a CloudWatch dashboard provides aggregate visibility.
- CloudFront caches at edge locations; Elastic Load Balancing distributes origin/application traffic.
Key takeaway
Recognize Elastic Load Balancing as a traffic and health surface for deployed applications.
Related services
- Amazon EC2
- Amazon Elastic Container Service (Amazon ECS)
- Amazon Route 53
Relevant exam tasks
- D3.4 — Deploy code by using AWS Continuous Integration and Continuous Delivery (CI/CD) services
- 3.4.5 — Deploy an application version by using deployment strategies
- 3.4.11 — Configure deployment strategies (for example, blue/green, canary, rolling) for application releases
- D4.2 — Instrument code for observability
- 4.2.8 — Configure application health checks and readiness probes