Security, Identity, and Compliance
CoreElastic Load Balancing (ELB)
Explicit health-check configuration/troubleshooting and availability boundary.
Key points
- ELB distributes requests only to targets that satisfy the configured health protocol, port, path, response, and thresholds.
Best-known use cases
- D4.1, D4.2, and D5.1: troubleshoot the named target health or request-distribution failure at the load-balancer layer.
What candidates often confuse it with
- ELB target health governs registered targets; Route 53 health governs DNS answers and Auto Scaling supplies replacement capacity.
Key takeaway
Verify healthy capacity and the exact target check before changing outer DNS or scaling controls.
Related services
- AWS Certificate Manager (ACM)
- Amazon EC2 security groups
- Egress-only internet gateways
Relevant exam tasks
- D4.1 — Task 4.1: Implement and manage security and compliance tools and policies.
- 4.1.1 — Implement IAM features (for example, password policies, multi-factor authentication [MFA], roles, federated identity, resource policies, policy conditions).
- D4.2 — Task 4.2: Implement strategies to protect data and infrastructure.
- 4.2.1 — Implement and enforce a data classification scheme.
- D5.1 — Task 5.1: Implement and optimize networking features and connectivity.
- 5.1.1 — Configure a VPC (for example, subnets, route tables, network ACLs, security groups, NAT gateways, internet gateway, egress-only internet gateway).