Cyber Monday 2024! 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

Google Exam Professional Cloud Network Engineer Topic 2 Question 97 Discussion

Actual exam question for Google's Professional Cloud Network Engineer exam
Question #: 97
Topic #: 2
[All Professional Cloud Network Engineer Questions]

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)

Show Suggested Answer Hide Answer
Suggested Answer: C, E

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.


by Sherell at Oct 22, 2024, 01:39 AM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Network Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Trinidad
1 months ago
Haha, option D is like throwing the baby out with the bathwater. Why not just fix the issue instead of starting from scratch?
upvoted 0 times
Terina
19 days ago
Haha, option D is like throwing the baby out with the bathwater. Why not just fix the issue instead of starting from scratch?
upvoted 0 times
...
Crissy
23 days ago
B) Enable and review the health check logs. Review the error responses in Cloud Logging.
upvoted 0 times
...
Micheal
24 days 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.
upvoted 0 times
...
...
Xuan
1 months ago
I agree, but we should also consider option C for a more thorough investigation.
upvoted 0 times
...
Almeta
2 months ago
I agree, B and C are the best choices. Deleting and recreating the load balancer seems like overkill for this problem.
upvoted 0 times
Patria
7 days ago
Accessing a backend VM directly and increasing the quantity of backends can help identify the root cause of the error.
upvoted 0 times
...
Rory
9 days ago
Deleting the load balancer and backend services seems extreme. It's better to troubleshoot the issue first.
upvoted 0 times
...
Layla
30 days ago
I agree, reviewing the health check logs and validating the backend service's health are important steps.
upvoted 0 times
...
Gertude
1 months ago
I think B and C are the best choices.
upvoted 0 times
...
...
Dominga
2 months ago
I think we should try option A first.
upvoted 0 times
...
Bulah
2 months 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.
upvoted 0 times
Arminda
21 days 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.
upvoted 0 times
...
Jennifer
24 days ago
I think validating the health of the backend service and enabling logging on the load balancer is important to identify the error.
upvoted 0 times
...
Heidy
1 months ago
I agree, reviewing the health check logs and error responses in Cloud Logging is a good start.
upvoted 0 times
...
...

Save Cancel