A company runs a website by using an Amazon Elastic Container Service (Amazon ECS) service that is connected to an Application Load Balancer (ALB). The service was in a steady state with tasks…

Question

Options

• AEnsure that a security group associated with the service allows traffic from the ALB.
• BIncrease the ALB health check grace period for the service.
• CIncrease the service minimum healthy percent setting.
• DDecrease the ALB health check interval.

• A
  11% (4)
• B
  83% (29)
• C
  3% (1)
• D
  3% (1)

Explanation

Explanation

Increasing the ALB health check grace period is the right fix here because the new container image likely requires more startup time than the original - the application may need extra seconds to initialize before it can respond to health check requests, and without a sufficient grace period, the ALB marks tasks as unhealthy before they're ready, triggering the stop/restart cycle. Option A is incorrect because security group misconfiguration would have caused failures in the original steady state as well, not just after updating the task definition. Option C is wrong because the minimum healthy percent controls how many tasks must remain healthy during a deployment, but it doesn't address why the health checks are failing in the first place. Option D is incorrect because decreasing the health check interval would actually make the problem worse by checking more frequently before the container has had time to start up properly.

Memory Tip

Think of the health check grace period as a "warm-up window" - just like a new employee needs onboarding time before taking customer calls, a new container needs startup time before handling health checks. When a deployment breaks something that worked before, ask yourself: "Did something change that requires more startup time?"

No community discussion yet for this question.