You support a stateless web-based API that is deployed on a single Compute Engine instance in the europe-west2-a zone. The Service Level Indicator (SLI) for service availability is below the specified

Question

Options

• AChange the specified SLO to match the measured SLI
• BMove the service to higher-specification compute instances with more memory
• CSet up additional service instances in other zones and load balance the traffic between all
• DSet up additional service instances in other zones and use them as a failover in case the primary

• A
  3% (1)
• B
  10% (4)
• C
  80% (32)
• D
  8% (3)

Explanation

The root causes are two-fold: insufficient capacity (high request volume exceeds memory) and a single point of failure (one instance in one zone). Option C - adding instances in multiple zones with load balancing - addresses both problems simultaneously: it distributes the request load so no single instance is overwhelmed, and it eliminates the single point of failure to improve availability. Option A (adjusting the SLO) is not a fix - it just redefines what success means. Option B (larger instance) is vertical scaling that does not eliminate the single point of failure or scale with traffic. Option D (failover instances) only helps when the primary fails, not when the primary is overwhelmed by traffic - the root cause.

No community discussion yet for this question.