nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #56

You are the on-call Site Reliability Engineer for a microservice that is deployed to a Google Kubernetes Engine (GKE) Autopilot cluster. Your company runs an online store that publishes order…

The correct answer is C. Increase the number of Pod replicas. To handle an increased volume of Pub/Sub messages caused by a sales event and speed up stock updates, you should increase the number of Pod replicas for the microservice consuming the messages.

Submitted by kavita_s· Apr 18, 2026Applying site reliability engineering principles to a service

Question

You are the on-call Site Reliability Engineer for a microservice that is deployed to a Google Kubernetes Engine (GKE) Autopilot cluster. Your company runs an online store that publishes order messages to Pub/Sub, and a microservice receives these messages and updates stock information in the warehousing system. A sales event caused an increase in orders, and the stock information is not being updated quickly enough. This is causing a large number of orders to be accepted for products that are out of stock. You check the metrics for the microservice and compare them to typical levels: You need to ensure that the warehouse system accurately reflects product inventory at the time orders are placed and minimize the impact on customers. What should you do?

Exhibit

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER question #56 exhibit

Options

  • ADecrease the acknowledgment deadline on the subscription.
  • BAdd a virtual queue to the online store that allows typical traffic levels.
  • CIncrease the number of Pod replicas.
  • DIncrease the Pod CPU and memory limits.

How the community answered

(44 responses)
  • A
    2% (1)
  • B
    16% (7)
  • C
    75% (33)
  • D
    7% (3)

Why each option

To handle an increased volume of Pub/Sub messages caused by a sales event and speed up stock updates, you should increase the number of Pod replicas for the microservice consuming the messages.

ADecrease the acknowledgment deadline on the subscription.

Decreasing the acknowledgment deadline on the subscription would cause messages to be redelivered more quickly if not acknowledged, potentially overwhelming the microservice further.

BAdd a virtual queue to the online store that allows typical traffic levels.

Adding a virtual queue to the online store would only delay the problem by limiting new orders, rather than solving the underlying bottleneck of the microservice's inability to process existing messages fast enough.

CIncrease the number of Pod replicas.Correct

An increase in orders indicates a higher volume of messages being published to Pub/Sub, leading to a backlog if the consuming microservice cannot process them fast enough. Increasing the number of Pod replicas (scaling out) allows the GKE Autopilot cluster to run more instances of the microservice concurrently, distributing the message processing workload and significantly increasing throughput to keep up with the demand and update stock information more quickly.

DIncrease the Pod CPU and memory limits.

Increasing the Pod CPU and memory limits (scaling up) would only help if individual pods are resource-constrained and bottlenecked on processing single messages; for an increase in overall message volume, scaling out with more replicas is generally the more effective and appropriate solution.

Concept tested: GKE Autopilot scaling and Pub/Sub consumer patterns

Source: https://cloud.google.com/kubernetes-engine/docs/concepts/horizontalpodautoscaler

Topics

#GKE Autopilot#Pub/Sub Message Processing#Horizontal Scaling#Service Performance

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice