PCDOE Implementing service monitoring strategies Practice Question

A team is using Cloud Monitoring to track the performance of a microservices application. They set up an uptime check for each service, but they notice that some checks are failing intermittently without actual service degradation. What is the most likely cause?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The timeout setting is too short for the service's typical latency.

The most likely cause is that the timeout setting is too short, causing false positives when the service response time temporarily exceeds the timeout. Other options are less plausible: uptime checks typically run from multiple regions; load balancer 503 errors would indicate a real issue; quota exceed would prevent checks from running.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The services are behind a load balancer that occasionally returns 503 during scaling.
Why it's wrong here
A 503 response indicates an actual scaling issue, not a false positive.
✓
The timeout setting is too short for the service's typical latency.
Why this is correct
A short timeout can cause the check to fail even when the service is healthy, especially during transient latency spikes.
✗
Uptime checks are deployed in a single region, causing false positives.
Why it's wrong here
If only one region, false negatives are more likely, not false positives.
✗
The project's quota for uptime checks has been exceeded.
Why it's wrong here
If quota is exceeded, checks would not run at all, not fail intermittently.

Go deeper

PCDOE Implementing service monitoring strategies Practice Question

Why each option matters

Option-by-option breakdown

Related to this question