Google Professional Cloud Network Engineer Question 724
Select 3Google Cloud PlatformYou have deployed a highly available web application on Google Cloud using a global HTTP(S) load balancer with Google Cloud Armor for security and a Cloud NAT gateway for outbound internet access from private instances. Recently, users reported intermittent connectivity issues when accessing the application. You suspect the issue might be related to networking components. Which monitoring metrics should you prioritize to diagnose the issue?
- A
Google Cloud Armor blocked request count
- B
Cloud NAT connection utilization
- C
Cloud Router learned route count
- D
HTTP(S) load balancer backend latency
- E
Cloud Interconnect packet drop count
Show answer and explanation
Correct answers: A, B, D
Explanation
To diagnose intermittent connectivity issues, it is essential to monitor metrics that directly impact the traffic flow and application performance. Google Cloud Armor blocked request count helps determine if security rules are mistakenly blocking traffic. Cloud NAT connection utilization ensures that NAT resources are not exhausted, preventing outbound traffic. Backend latency for the HTTP(S) load balancer indicates if the backends are responding efficiently. Other metrics, like Cloud Router learned route count or Cloud Interconnect packet drop count, are less relevant to this specific scenario.
- A. Correct.
This metric is critical to determine if Google Cloud Armor is blocking legitimate traffic, which could cause intermittent connectivity issues.
- B. Correct.
Monitoring Cloud NAT connection utilization is important because resource exhaustion could prevent outbound connections, impacting the application.
- C. Incorrect.
While Cloud Router learned route count is useful for understanding dynamic routing, it is unlikely to directly indicate issues with intermittent connectivity for this scenario.
- D. Correct.
Backend latency for the HTTP(S) load balancer is vital to assess whether the application backends are responding slowly, which could result in poor user experience.
- E. Incorrect.
Cloud Interconnect packet drop count is unrelated in this scenario, as the application does not involve a private interconnect link.