What happens when a target in an AWS target group fails its health check?
Think about how a load balancer keeps your app healthy by avoiding bad servers.
When a target fails health checks, the load balancer temporarily stops sending traffic to it until it becomes healthy again. It does not remove or replace the target automatically.
Which statement correctly describes how target groups are used with an Application Load Balancer (ALB)?
Consider how ALB directs traffic based on rules and groups of servers.
Application Load Balancers use listener rules to route traffic to one or more target groups. Target groups contain the registered targets like EC2 instances or IP addresses.
Given this target group health check configuration:
Health check path: /status
Healthy threshold: 3
Unhealthy threshold: 2
Interval: 10 seconds
Timeout: 5 seconds
What is the minimum time before a target is marked unhealthy after it starts failing health checks?
Calculate using the unhealthy threshold and interval values.
The target must fail 2 consecutive health checks (unhealthy threshold) with checks every 10 seconds (interval). So, 2 x 10 = 20 seconds minimum before marked unhealthy.
You have an ALB and a target group with EC2 instances. Which security group rule is necessary for the EC2 instances to receive traffic from the ALB?
Think about how security groups reference each other for controlled access.
The EC2 instances must allow inbound traffic on the port used by the target group from the ALB's security group to receive traffic securely.
An EC2 instance is deregistered from a target group with a deregistration delay of 300 seconds. What happens to in-flight requests during this delay?
Consider how deregistration delay helps graceful shutdown.
Deregistration delay allows the load balancer to stop sending new requests but keeps the instance available to complete existing requests during the delay period.