Answer-first summary for fast verification
Answer: Validate the health of the backend service. Enable logging for the backend service and identify the error response in Cloud Logging. Review the statusDetails log field.
To effectively identify the cause of intermittent HTTP 4xx or 5xx error response codes from a global external Application Load Balancer, it's crucial to validate the health of the backend service and enable logging for the backend service. This allows for the identification of error responses in Cloud Logging, specifically by reviewing the statusDetails log field. This approach directly addresses the need to diagnose the root cause of the errors without unnecessary modifications to the infrastructure or security policies. Option C is the correct choice as it focuses on enabling logging and reviewing the detailed error information provided in the statusDetails field, which is essential for troubleshooting the issue.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your organization has exposed several services via a global external Application Load Balancer. During testing, responses occasionally return HTTP 4xx or 5xx error codes. You have enabled and examined the health check logs but still need to determine the root cause of the errors. What is your next step?
A
Access a VM in the VPC through SSH to access the backend VM directly. If the request is successful from the VM, increase the quantity of backends.
B
Delete the load balancer and backend services. Create a new Passthrough Network Load Balancer. Configure a failover group of VMs for the backend.
C
Validate the health of the backend service. Enable logging for the backend service and identify the error response in Cloud Logging. Review the statusDetails log field.
D
Validate the health of the backend service. Disable any Cloud Armor policies on the backend service, and identify any error response in Cloud Logging. Review the statusDetails log field.
No comments yet.