Google Professional Cloud Network Engineer Question 719
Select 3Google Cloud PlatformYour organization is experiencing unexpected network latency issues while traffic flows through a Cloud VPN tunnel. As part of troubleshooting, you want to review logs to analyze network traffic patterns and identify any potential issues. Which logging options should you enable to gather the most relevant data for this analysis?
- A
Enable VPC Flow Logs on the subnet associated with the Cloud VPN tunnel.
- B
Enable Cloud VPN logs in the Logging settings of the VPN gateway.
- C
Enable Firewall Rules Logging on all firewall rules applied to the VPN traffic.
- D
Enable Cloud DNS logging to track DNS queries passing through the VPN tunnel.
- E
Enable Cloud NAT logging for NAT traffic associated with the VPN.
Show answer and explanation
Correct answers: A, B, C
Explanation
To troubleshoot network latency in a Cloud VPN tunnel, you need to enable logging that provides insights into traffic flows, VPN tunnel status, and firewall rules. VPC Flow Logs, Cloud VPN logs, and Firewall Rules Logging collectively provide the most comprehensive data for diagnosing network issues in this scenario. Cloud DNS and Cloud NAT logging are not directly relevant to this use case.
- A. Correct.
Enabling VPC Flow Logs on the subnet provides detailed information about the network traffic entering and leaving the subnet, which is crucial for analyzing VPN traffic patterns.
- B. Correct.
Enabling Cloud VPN logs allows you to gather specific logs from the VPN gateway, such as tunnel status and error messages, which are essential for troubleshooting VPN issues.
- C. Correct.
Enabling Firewall Rules Logging helps identify whether any firewall rules are blocking or allowing traffic through the VPN tunnel, which may contribute to latency.
- D. Incorrect.
Cloud DNS logging tracks DNS queries but does not provide network traffic or latency-related data relevant to the VPN tunnel. This option is not helpful in this scenario.
- E. Incorrect.
Cloud NAT logging is useful for monitoring NAT-related traffic but is unrelated to the VPN tunnel traffic in this scenario unless NAT is explicitly configured for the VPN.