
Answer-first summary for fast verification
Answer: In the Cloud Platform Console download the list of the uptime servers' IP addresses and create an inbound firewall rule
The correct answer is B because the issue is likely due to firewall restrictions blocking Google's uptime check servers from reaching the legacy services. According to Google Cloud documentation, if a resource isn't publicly available, its firewall must be configured to permit incoming traffic from uptime-check servers. Option B directly addresses this by downloading the list of uptime server IP addresses and creating an inbound firewall rule. Option A is incorrect as the Stackdriver agent is for logging and metrics, not uptime checks. Options C and D are less suitable because they focus on User-Agent headers, which are for identifying uptime traffic in logs but do not resolve connectivity issues if the firewall blocks the requests entirely. The community discussion strongly supports B, with high upvotes and references to official documentation, while D is debated due to the 'legacy' nature of the services, but B remains the consensus for ensuring connectivity.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Dress4Win has set up a new uptime check in Google Cloud Monitoring for several legacy services, but the dashboard is not showing the services as healthy. What steps should they take to resolve this?
A
Install the Stackdriver agent on all of the legacy web servers.
B
In the Cloud Platform Console download the list of the uptime servers' IP addresses and create an inbound firewall rule
C
Configure their load balancer to pass through the User-Agent HTTP header when the value matches GoogleStackdriverMonitoring-UptimeChecks (https:// cloud.google.com/monitoring)
D
Configure their legacy web servers to allow requests that contain user-Agent HTTP header when the value matches GoogleStackdriverMonitoring- UptimeChecks (https://cloud.google.com/monitoring)
No comments yet.