nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #33

You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that…

The correct answer is A. Reroute the user traffic from the affected region to other regions that don't report issues. To quickly resolve an outage affecting all users in a specific region for a multi-regional GKE application, the immediate SRE action is to reroute traffic to healthy regions.

Submitted by eva_at· Apr 18, 2026Managing a service incident

Question

You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?

Options

  • AReroute the user traffic from the affected region to other regions that don't report issues.
  • BUse Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.
  • CAdd an extra node pool that consists of high memory and high CPU machine type instances to
  • DUse Stackdriver Logging to filter on the clusters in the affected region, and inspect error

How the community answered

(45 responses)
  • A
    84% (38)
  • B
    4% (2)
  • C
    9% (4)
  • D
    2% (1)

Why each option

To quickly resolve an outage affecting all users in a specific region for a multi-regional GKE application, the immediate SRE action is to reroute traffic to healthy regions.

AReroute the user traffic from the affected region to other regions that don't report issues.Correct

In a multi-regional deployment, when an entire region is experiencing a connectivity outage, the fastest way to restore service for users is to reroute their traffic to other healthy regions. This aligns with SRE's emphasis on minimizing user impact and restoring service as quickly as possible during an incident, providing immediate mitigation while root cause analysis can proceed in parallel.

BUse Stackdriver Monitoring to check for a spike in CPU or memory usage for the affected region.

Checking monitoring for CPU/memory spikes is a diagnostic step, not an immediate mitigation for a complete regional connectivity outage, and would delay restoring service to users.

CAdd an extra node pool that consists of high memory and high CPU machine type instances to

Adding an extra node pool is a scaling action, not an immediate incident response, and it assumes the problem is resource saturation, which is unlikely to cause a complete connectivity loss for an entire region.

DUse Stackdriver Logging to filter on the clusters in the affected region, and inspect error

Inspecting error logs is a diagnostic step for root cause analysis, which is important but secondary to immediate service restoration, and would not directly restore connectivity for affected users.

Concept tested: SRE incident response (immediate mitigation)

Source: https://sre.google/sre-book/on-call-handbook/#addressing-incidents

Topics

#Incident Response#Service Restoration#Multi-region Architecture#Site Reliability Engineering

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice