SAA-C03 · Question #628
A company's HTTP application is behind a Network Load Balancer (NLB). The NLB's target group is configured to use an Amazon EC2 Auto Scaling group with multiple EC2 instances that run the web service.
The correct answer is C. Replace the NLB with an Application Load Balancer. Enable HTTP health checks by supplying. NLB does not handle HTTP (layer 7) listerns errors only TCP (layer 4) listeners. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-nlb.html
Question
A company's HTTP application is behind a Network Load Balancer (NLB). The NLB's target group is configured to use an Amazon EC2 Auto Scaling group with multiple EC2 instances that run the web service. The company notices that the NLB is not detecting HTTP errors for the application. These errors require a manual restart of the EC2 instances that run the web service. The company needs to improve the application's availability without writing custom scripts or code. What should a solutions architect do to meet these requirements?
Options
- AEnable HTTP health checks on the NLB. supplying the URL of the company's application.
- BAdd a cron job to the EC2 instances to check the local application's logs once each minute. If
- CReplace the NLB with an Application Load Balancer. Enable HTTP health checks by supplying
- DCreate an Amazon Cloud Watch alarm that monitors the UnhealthyHostCount metric for the NLB.
How the community answered
(33 responses)- A3% (1)
- B6% (2)
- C79% (26)
- D12% (4)
Explanation
NLB does not handle HTTP (layer 7) listerns errors only TCP (layer 4) listeners. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/environments-cfg-nlb.html
Community Discussion
No community discussion yet for this question.