Google Professional Cloud Network Engineer Question 772
Single answerGoogle Cloud PlatformYour company has deployed a global web application on Google Cloud that serves traffic using a multi-region architecture. Users are reporting intermittent delays and timeouts when accessing the application. You need to identify whether packet loss or high latency is occurring within Google's network or between Google and your users. Which action should you take using the Performance Dashboard?
- A
Use the 'Google Network Regions to Google Network Regions' view to identify potential packet loss or latency within Google's backbone network.
- B
Use the 'Google Network to Internet' view to analyze packet loss and latency between Google's network and your users' ISPs.
- C
Use the 'Network Telemetry' section of the Performance Dashboard to directly view application-level logs for debugging packet loss.
- D
Use the 'Troubleshooting' tab in the Performance Dashboard to simulate end-user traffic and measure packet loss and latency.
Show answer and explanation
Correct answer: B
Explanation
The 'Google Network to Internet' view in the Performance Dashboard is specifically designed to help identify packet loss and latency issues between Google's network and external networks, including users' ISPs. Since the problem involves delays reported by your users, analyzing this view is the most appropriate action to take. Other options either focus on internal network diagnostics or reference non-existent features of the Performance Dashboard.
- A. Incorrect.
This option is incorrect because the 'Google Network Regions to Google Network Regions' view is used to analyze traffic between Google's internal regions, not traffic involving end users. While useful for internal diagnostics, it does not address the issue of delays reported by external users.
- B. Correct.
This is the correct option because the 'Google Network to Internet' view in the Performance Dashboard allows you to analyze metrics such as packet loss and latency between Google's network and the Internet, which includes your users' ISPs. This is essential for diagnosing external connectivity issues.
- C. Incorrect.
This option is incorrect because the Performance Dashboard does not include a 'Network Telemetry' section for application-level logs. Application-level logs are typically analyzed using tools like Cloud Logging, which is separate from the Performance Dashboard.
- D. Incorrect.
This option is incorrect because the Performance Dashboard does not include a 'Troubleshooting' tab for simulating user traffic. Simulating user traffic would require tools like Traffic Director or custom scripts.