Cloud Digital Leader Practice Question: A software team is using Google Cloud and wants…

Answer analysis

Option-by-option breakdown

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

• ✗

  Scaling up adds more servers to handle increased load; scaling out makes each server more powerful by adding CPU and RAM

  Why it's wrong here

  The statement reverses the meanings of the two scaling patterns. Vertical scaling (scaling up) increases the compute capacity—CPU, memory, or storage—of a single server instance, while horizontal scaling (scaling out) adds additional server instances and distributes workload across them, typically through a load balancer. Because it swaps the definitions, this option misidentifies the fundamental mechanics of each approach and cannot be considered a valid description.

• ✓

  Vertical scaling (scaling up) increases the resources of an individual server (more CPU, RAM), while horizontal scaling (scaling out) adds more servers to distribute load — horizontal scaling is generally preferred in cloud environments for its flexibility and lack of a ceiling

  Why this is correct

  This correctly defines both approaches and notes the cloud preference for horizontal scaling. Cloud autoscaling is built on horizontal scale — adding identical instances behind a load balancer. Vertical scaling is limited by maximum available machine sizes and often requires downtime for resize.

• ✗

  Both scaling up and scaling out describe the same approach — adding more cloud resources to handle increased demand

  Why it's wrong here

  Scaling up and scaling out are fundamentally different architectural strategies, not the same approach. Scaling up alters the resource allocation of one existing server, which has an upper bound set by the largest available machine size and often requires downtime to apply the change; scaling out increases total capacity by adding more servers, providing elasticity, fault tolerance, and a virtually unlimited ceiling if the application is stateless and can be placed behind a load balancer. Treating them as identical ignores these distinct trade-offs and operational implications.

• ✗

  Scaling up is only possible in cloud environments; on-premises systems can only scale out

  Why it's wrong here

  This option incorrectly ties scaling mode to infrastructure location. On-premises data centers can vertically scale by upgrading a single server's CPU, RAM, or disks, and they can horizontally scale by provisioning additional physical servers and balancing traffic among them; the same is true in cloud environments. The real distinction is architectural: vertical scaling changes the size of one machine, while horizontal scaling changes the number of machines. Cloud environments simply make horizontal scaling easier through automation and managed services.

Go deeper

Related to this question