Your organization recently exposed a set of services through a global external Application Load Balancer. After conducting some testing, you observed that responses would intermittently yield a non-HTTP 200 response. You need to identify the error. What should you do? (Choose 2 answers)
Suggested Answer: C, E
Get Premium Professional Cloud Network Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
To troubleshoot the intermittent non-HTTP 200 responses, you should enable and review health check logs and log the backend service's responses in Cloud Logging. Reviewing the statusDetails field helps identify the cause of the error. Enabling logging on the load balancer and backend service provides visibility into the issue.
29 comments · newest first
WH
Whitney
11 months ago
Can we really trust the logs to give us the full picture?
BI
Billy
11 months ago
E looks good too, logging is key for troubleshooting.
LE
Leontine
11 months ago
Wait, why would you delete the load balancer? Seems extreme.
VA
Vanesa
11 months ago
Totally agree, health checks are crucial!
BR
Breana
12 months ago
I think C and D are the best options here.
DA
Davida
12 months ago
I vaguely recall a practice question where we had to troubleshoot load balancer issues. I think focusing on health checks and logs is key, so maybe C and E are the right choices here.
EA
Earnestine
1 year ago
I think enabling logging is crucial for identifying issues. Options D and E both mention logging, but I wonder if one is better than the other for this scenario.
MU
Muriel
1 year ago
I'm a bit unsure about the best approach here. I feel like accessing the VM directly, as mentioned in option B, could help, but it seems like a roundabout way to troubleshoot.
HU
Hubert
1 year ago
I remember we discussed the importance of health checks in our last study session. I think options C and D might be relevant since they both involve checking logs and health status.
AU
Augustine
1 year ago
I'm a bit unsure about the network load balancer option. I'll need to research that a bit more to see if it's really the best solution.
TU
Tu
1 year ago
I'm feeling pretty confident about this one. Validating the backend service health and reviewing the logs should help me identify the root cause.
KA
Kaitlyn
1 year ago
Okay, I think the key here is to focus on troubleshooting the issue. Enabling logging and reviewing the error responses seems like a good place to start.
RY
Ryan
1 year ago
Hmm, I'm a bit confused by the different load balancer options. I'll need to make sure I understand the differences before deciding.
YO
Yolande
1 year ago
This looks like a tricky one. I'll need to carefully read through the options and think about the best approach.
TR
Trinidad
2 years ago
Haha, option D is like throwing the baby out with the bathwater. Why not just fix the issue instead of starting from scratch?
TE
Terina
2 years ago
Haha, option D is like throwing the baby out with the bathwater. Why not just fix the issue instead of starting from scratch?
CR
Crissy
2 years ago
B) Enable and review the health check logs. Review the error responses in Cloud Logging.
MI
Micheal
2 years ago
A) Access a VM in the VPC through SSH, and try to access a backend VM directly. If the request is successful from the VM, increase the quantity of backends.
XU
Xuan
2 years ago
I agree, but we should also consider option C for a more thorough investigation.
AL
Almeta
2 years ago
I agree, B and C are the best choices. Deleting and recreating the load balancer seems like overkill for this problem.
PA
Patria
2 years ago
Accessing a backend VM directly and increasing the quantity of backends can help identify the root cause of the error.
RO
Rory
2 years ago
Deleting the load balancer and backend services seems extreme. It's better to troubleshoot the issue first.
LA
Layla
2 years ago
I agree, reviewing the health check logs and validating the backend service's health are important steps.
GE
Gertude
2 years ago
I think B and C are the best choices.
DO
Dominga
2 years ago
I think we should try option A first.
BU
Bulah
2 years ago
Option B and C seem like the way to go. Checking the health check logs and the load balancer logs should help identify the issue.
AR
Arminda
2 years ago
Let's access a VM in the VPC through SSH and try to access a backend VM directly to see if increasing the quantity of backends helps.
JE
Jennifer
2 years ago
I think validating the health of the backend service and enabling logging on the load balancer is important to identify the error.
HE
Heidy
2 years ago
I agree, reviewing the health check logs and error responses in Cloud Logging is a good start.