nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #22

You have migrated an e-commerce application to Google Cloud Platform (GCP). You want to prepare the application for the upcoming busy season. What should you do first to prepare for the busy season?

The correct answer is A. Load teat the application to profile its performance for scaling. To prepare an e-commerce application for a busy season on GCP, the initial and most critical step is to load test it to understand its performance limits and scaling behavior.

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

Question

You have migrated an e-commerce application to Google Cloud Platform (GCP). You want to prepare the application for the upcoming busy season. What should you do first to prepare for the busy season?

Options

  • ALoad teat the application to profile its performance for scaling.
  • BEnable AutoScaling on the production clusters, in case there is growth.
  • CPre-provision double the compute power used last season, expecting growth.
  • DCreate a runbook on inflating the disaster recovery (DR) environment if there is growth.

How the community answered

(21 responses)
  • A
    76% (16)
  • B
    5% (1)
  • C
    14% (3)
  • D
    5% (1)

Why each option

To prepare an e-commerce application for a busy season on GCP, the initial and most critical step is to load test it to understand its performance limits and scaling behavior.

ALoad teat the application to profile its performance for scaling.Correct

Load testing the application is the foundational first step because it provides crucial data on how the application performs under anticipated high traffic, identifies bottlenecks, and validates the effectiveness of its scaling mechanisms. This profiling is essential before making any scaling decisions or configurations.

BEnable AutoScaling on the production clusters, in case there is growth.

While enabling AutoScaling is important, doing it without prior load testing means you lack data on appropriate scaling triggers and capacities, which could lead to under- or over-provisioning or unexpected performance issues.

CPre-provision double the compute power used last season, expecting growth.

Pre-provisioning double the compute power is a reactive and potentially wasteful approach without empirical data from load testing to justify the specific increase needed.

DCreate a runbook on inflating the disaster recovery (DR) environment if there is growth.

A runbook for DR environment inflation is a good preparedness step but is secondary to ensuring the primary application can handle the load, and doesn't directly address the performance and scaling of the production environment for peak season.

Concept tested: Application load testing and performance profiling

Source: https://cloud.google.com/architecture/patterns/distributed-load-testing-with-serverless-architecture

Topics

#Load testing#Performance profiling#Scalability#Capacity planning

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice