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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Amazon SCS-C02 Exam - Topic 8 Question 28 Discussion

Actual exam question for Amazon's SCS-C02 exam
Question #: 28
Topic #: 8
[All SCS-C02 Questions]

A Network Load Balancer (NLB) target instance is not entering the InService state. A security engineer determines that health checks are failing.

Which factors could cause the health check failures? (Select THREE.)

Show Suggested Answer Hide Answer
Suggested Answer: A, C, D

by julien at Sep 16, 2024, 09:43 AM

Limited Time Offer

25%

Off

Get Premium SCS-C02 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Stephen
3 months ago
B is not a factor, the security group doesn't need to be attached to the NLB.
upvoted 0 times
...
Ernie
4 months ago
Surprised that E isn't more commonly known!
upvoted 0 times
...
Elly
4 months ago
I thought the security group had to be attached to the NLB too?
upvoted 0 times
...
Sanjuana
4 months ago
Definitely A and D are common issues!
upvoted 0 times
...
Celestina
4 months ago
The target instance's security group might be blocking NLB traffic.
upvoted 0 times
...
Daisy
4 months ago
I feel like option C is a bit misleading. The NLB's security group doesn't really need to be attached to the target instance, right? It’s more about the instance's security group allowing traffic.
upvoted 0 times
...
Kimberlie
5 months ago
I practiced a similar question where security groups were a big factor. I wonder if option E could be a problem if the IP addresses aren't set correctly.
upvoted 0 times
...
Shaunna
5 months ago
I'm not entirely sure, but I think the network ACLs might also play a role. Maybe option D is relevant here since they control traffic as well.
upvoted 0 times
...
Elvera
5 months ago
I remember something about security groups needing to allow traffic from the NLB, so I think option A could definitely be a reason for the health check failures.
upvoted 0 times
...
Jacinta
5 months ago
This is a good one! I feel confident I can tackle this. I'll methodically go through the options and select the three most likely causes of the health check failures.
upvoted 0 times
...
Aretha
5 months ago
Hmm, I'm a bit unsure about this one. I'll need to double-check the relationship between the NLB, the target instance, and the security groups and network ACLs. Gotta make sure I understand all the moving parts here.
upvoted 0 times
...
Felix
5 months ago
This seems like a straightforward security-related question. I'll start by carefully reviewing the security group and network ACL configurations for both the NLB and the target instance.
upvoted 0 times
...
Merri
5 months ago
Okay, let's think this through step-by-step. The key is to identify all the potential points of failure in the communication between the NLB and the target instance. I'll make sure to cover the security group, network ACL, and IP address settings.
upvoted 0 times
...
Sylvie
5 months ago
I'm a bit confused by the wording of these options. I'll need to re-read the question and definitions carefully to make sure I understand the nuances of each choice.
upvoted 0 times
...
Dong
1 year ago
Hold up, is the target instance wearing a tuxedo to the health check party? E is the one to watch out for, for sure.
upvoted 0 times
Carlton
1 year ago
C: I agree, E could be the reason why the health checks are failing.
upvoted 0 times
...
Lemuel
1 year ago
B: Yeah, E mentions using IP addresses, which might be the problem.
upvoted 0 times
...
Naomi
1 year ago
A: Definitely not, but it seems like E could be causing the issue.
upvoted 0 times
...
...
Teresita
1 year ago
I think another factor could be the target instance's subnet network ACL not allowing traffic from the NLB.
upvoted 0 times
...
Daniel
1 year ago
This is a classic 'security gone wrong' scenario. A, D, and E for sure. Bet the engineer is scratching their head on this one!
upvoted 0 times
...
Chantell
1 year ago
I agree with Olene. It could also be because the NLB's security group is not attached to the target instance.
upvoted 0 times
...
Olene
1 year ago
Easy peasy, A, D, and E. You've gotta make sure the security and network settings are all lined up for the NLB to do its job.
upvoted 0 times
Stevie
1 year ago
True, using IP addresses in the security group settings is necessary for the NLB to function properly.
upvoted 0 times
...
Remedios
1 year ago
Don't forget about the subnet network ACL, that could also be causing the issue.
upvoted 0 times
...
Iola
1 year ago
I agree, making sure the security group allows traffic from the NLB is crucial.
upvoted 0 times
...
Karan
1 year ago
Definitely, A, D, and E are important factors to consider for the health check failures.
upvoted 0 times
...
...
Olene
1 year ago
I think the health check failures could be caused by the target instance's security group not allowing traffic from the NLB.
upvoted 0 times
...
Alita
1 year ago
Hmm, I'd say A, D, and E as well. The target instance needs to be wide open to the NLB for those health checks to pass.
upvoted 0 times
...
Ellen
1 year ago
A, D, and E seem like the most likely culprits here. Can't have the security group or network ACL blocking the NLB traffic.
upvoted 0 times
Emile
1 year ago
E) The target instance's security group is not using IP addresses to allow traffic from the NLB.
upvoted 0 times
...
Deonna
1 year ago
D) The target instance's subnet network ACL does not allow traffic from the NLB.
upvoted 0 times
...
Leonora
1 year ago
A) The target instance's security group does not allow traffic from the NLB.
upvoted 0 times
...
...

Save Cancel