ExamGecko
Question list
Search
Search

List of questions

Search

Related questions











Question 415 - SOA-C02 discussion

Report
Export

The company's ecommerce website running on EC2 instances behind an ALB intermittently returns HTTP 500 errors. The Auto Scaling group is only using EC2 status checks.

A.

Replace the ALB with a Network Load Balancer.

Answers
A.

Replace the ALB with a Network Load Balancer.

B.

Add Elastic Load Balancing (ELB) health checks to the Auto Scaling group.

Answers
B.

Add Elastic Load Balancing (ELB) health checks to the Auto Scaling group.

C.

Update the target group configuration on the ALB. Enable session affinity (sticky sessions).

Answers
C.

Update the target group configuration on the ALB. Enable session affinity (sticky sessions).

D.

Install the Amazon CloudWatch agent on all the instances. Configure the agent to reboot the instances.

Answers
D.

Install the Amazon CloudWatch agent on all the instances. Configure the agent to reboot the instances.

Suggested answer: B

Explanation:

Using ALB health checks in the Auto Scaling group will provide more accurate health monitoring and replace instances if they are unhealthy.

ALB Health Checks: Configure health checks based on HTTP response codes, which will detect application-level issues causing the HTTP 500 errors and replace instances as needed.

EC2 vs. ALB Health Checks: EC2 status checks only verify instance hardware and OS, not the application's responsiveness. By using ALB health checks, Auto Scaling can remove instances that are failing at the application level, thus preventing users from receiving 500 errors.

Replacing the ALB with a Network Load Balancer does not address HTTP 500 errors, and enabling session affinity does not resolve application health issues. The CloudWatch agent would not provide the required health check functionality for automated instance replacement.

asked 06/11/2024
sujan bolla
38 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first