New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SOA-C03 Exam - Topic 4 Question 8 Discussion

Actual exam question for Amazon's SOA-C03 exam
Question #: 8
Topic #: 4
[All SOA-C03 Questions]

A company's ecommerce application is running on Amazon EC2 instances that are behind an Application Load Balancer (ALB). The instances are in an Auto Scaling group. Customers report that the website is occasionally down. When the website is down, it returns an HTTP 500 (server error) status code to customer browsers.

The Auto Scaling group's health check is configured for EC2 status checks, and the instances appear healthy.

Which solution will resolve the problem?

Show Suggested Answer Hide Answer
Suggested Answer: B

In this scenario, the EC2 instances pass their EC2 status checks, indicating that the operating system is responsive. However, the application hosted on the instance is failing intermittently, returning HTTP 500 errors. This demonstrates a discrepancy between the instance-level health and the application-level health.

According to AWS CloudOps best practices under Monitoring, Logging, Analysis, Remediation and Performance Optimization (SOA-C03 Domain 1), Auto Scaling groups should incorporate Elastic Load Balancing (ELB) health checks instead of relying solely on EC2 status checks. The ELB health check probes the application endpoint (for example, HTTP or HTTPS target group health checks), ensuring that the application itself is functioning correctly.

When an instance fails an ELB health check, Amazon EC2 Auto Scaling will automatically mark the instance as unhealthy and replace it with a new one, ensuring continuous availability and performance optimization.

Extract from AWS CloudOps (SOA-C03) Study Guide -- Domain 1:

''Implement monitoring and health checks using ALB and EC2 Auto Scaling integration. Application Load Balancer health checks allow Auto Scaling to terminate and replace instances that fail application-level health checks, ensuring consistent application performance.''

Extract from AWS Auto Scaling Documentation:

''When you enable the ELB health check type for your Auto Scaling group, Amazon EC2 Auto Scaling considers both EC2 status checks and Elastic Load Balancing health checks to determine instance health. If an instance fails the ELB health check, it is automatically replaced.''

Therefore, the correct answer is B, as it ensures proper application-level monitoring and remediation using ALB-integrated ELB health checks---a core CloudOps operational practice for proactive incident response and availability assurance.

References (AWS CloudOps Verified Source Extracts):

AWS Certified CloudOps Engineer -- Associate (SOA-C03) Exam Guide: Domain 1 -- Monitoring, Logging, and Remediation.

AWS Auto Scaling User Guide: Health checks for Auto Scaling instances (Elastic Load Balancing integration).

AWS Well-Architected Framework -- Operational Excellence and Reliability Pillars.

AWS Elastic Load Balancing Developer Guide -- Target group health checks and monitoring.


Contribute your Thoughts:

0/2000 characters
Tawanna
3 days ago
C looks promising. Enabling session affinity could help maintain user sessions during failovers.
upvoted 0 times
...
Elenore
8 days ago
I'm not sure about D. Rebooting instances automatically might not be the best solution, as it could cause more issues.
upvoted 0 times
...
Audry
13 days ago
Option B seems like the way to go. Adding ELB health checks will help the Auto Scaling group identify unhealthy instances more accurately.
upvoted 0 times
...
Hyun
18 days ago
I recall that installing the CloudWatch agent could provide more insights, but rebooting instances seems like a last resort.
upvoted 0 times
...
Yolando
23 days ago
I'm not entirely sure, but I feel like enabling session affinity could help if the problem is related to user sessions.
upvoted 0 times
...
Skye
28 days ago
I think we practiced a similar question where we had to decide between health checks and load balancer settings. Adding ELB health checks might help identify the issue better.
upvoted 0 times
...
Raymon
1 month ago
I remember we discussed how HTTP 500 errors usually indicate an issue with the application itself, not just the infrastructure.
upvoted 0 times
...
Isabelle
1 month ago
I'm not sure about installing the CloudWatch agent and rebooting the instances. That seems like a bit of a heavy-handed approach when the instances are already reporting as healthy.
upvoted 0 times
...
Hubert
1 month ago
I'm pretty confident that option C is the way to go. Enabling session affinity could help ensure that customers stay connected to the same instance, which might resolve the intermittent downtime.
upvoted 0 times
...
Lauran
2 months ago
Okay, I'm leaning towards option B. Adding ELB health checks could help us identify any issues with the instances that the current status checks are missing.
upvoted 0 times
...
Kanisha
2 months ago
Hmm, I think the key here is that the instances are reporting as healthy, but the customers are still seeing errors. Maybe we need to look at the health checks more closely.
upvoted 0 times
...
Beckie
2 months ago
I'm a bit confused by this question. I'm not sure if the issue is with the load balancer or the instances themselves.
upvoted 0 times
...

Save Cancel