You want to monitor the uptime of an external HTTP endpoint from multiple locations around the world. Which TWO steps should you take? (Choose two.)
Choosing several geographic locations makes the uptime check probe the endpoint from distinct regions, so an outage or regional network fault is distinguished from a localised failure. This directly satisfies the requirement to monitor availability from multiple locations around the world.
Why this answer
Option D is correct because a Cloud Monitoring uptime check is the native resource designed to probe an HTTP(S) endpoint from Google-managed probers and report up/down status and latency. Option C is correct because an uptime check lets you select multiple geographic regions (e.g., us-west1, europe-west1, asia-east1) so the endpoint is tested from several locations worldwide, which is exactly the requirement. Option A is not appropriate because a log-based metric derives values from log entries and does not itself perform external HTTP probing from multiple regions.
Option B is not appropriate because a Pub/Sub notification channel only delivers alerts; it does not create the monitoring check or provide multi-region probing. Option E is not appropriate because VPC flow logs capture IP traffic metadata within a VPC and cannot monitor an external HTTP endpoint's uptime.
Exam trap
ACE often tests the trap of confusing uptime checks with logging or notification mechanisms, leading candidates to select log-based metrics or Pub/Sub channels instead of the core uptime check configuration.