- A
Horizontal scaling adds CPU/memory to existing servers; vertical scaling adds more servers.
Why wrong: This is backwards. Horizontal = more instances (scale out). Vertical = bigger instances (scale up).
- B
Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances.
Horizontal: add more VMs/containers (scale out). Vertical: upgrade to a larger VM with more CPU/RAM (scale up). Cloud autoscaling is primarily horizontal.
- C
Horizontal scaling is for databases only; vertical scaling is for web servers.
Why wrong: Both scaling approaches apply to any resource type. Web applications often scale horizontally (multiple app server instances); databases can scale both ways.
- D
Horizontal scaling requires application downtime; vertical scaling is always online.
Why wrong: Horizontal scaling (adding instances) is typically online. Vertical scaling of VMs often requires a restart in traditional environments, though cloud databases can scale vertically without downtime.
Quick Answer
The correct answer is that horizontal scaling adds more instances to distribute load, while vertical scaling increases the size of existing instances. Horizontal scaling, often called scale-out, improves fault tolerance and capacity by spreading work across multiple nodes, such as additional virtual machines or containers, making it highly resilient to failure. Vertical scaling, or scale-up, boosts the resources—CPU, RAM, or storage—of a single instance, but it eventually hits hardware limits and typically requires downtime to upgrade. On the Google Cloud Digital Leader exam, this distinction tests your understanding of how to design for elasticity and availability in cloud architectures; a common trap is confusing “scaling out” with simply adding more power to one machine. Remember the mnemonic: “Horizontal = more horses, Vertical = one bigger horse.”
Cloud Digital Leader Fundamental cloud concepts Practice Question
This GCDL practice question tests your understanding of fundamental cloud concepts. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
What is horizontal scaling, and how does it differ from vertical scaling?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances.
Horizontal scaling (scale-out) adds more instances (e.g., additional virtual machines or containers) to distribute the workload across multiple nodes, improving fault tolerance and capacity. Vertical scaling (scale-up) increases the resources (CPU, RAM, storage) of an existing instance, often hitting hardware limits and requiring downtime. Option B correctly captures this distinction.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Horizontal scaling adds CPU/memory to existing servers; vertical scaling adds more servers.
Why it's wrong here
This is backwards. Horizontal = more instances (scale out). Vertical = bigger instances (scale up).
- ✓
Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances.
Why this is correct
Horizontal: add more VMs/containers (scale out). Vertical: upgrade to a larger VM with more CPU/RAM (scale up). Cloud autoscaling is primarily horizontal.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Horizontal scaling is for databases only; vertical scaling is for web servers.
Why it's wrong here
Both scaling approaches apply to any resource type. Web applications often scale horizontally (multiple app server instances); databases can scale both ways.
- ✗
Horizontal scaling requires application downtime; vertical scaling is always online.
Why it's wrong here
Horizontal scaling (adding instances) is typically online. Vertical scaling of VMs often requires a restart in traditional environments, though cloud databases can scale vertically without downtime.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the common misconception that horizontal scaling means adding resources to a single server (like upgrading RAM), when in fact it means adding more servers to share the load.
Detailed technical explanation
How to think about this question
In cloud environments like AWS or Azure, horizontal scaling leverages auto-scaling groups and load balancers (e.g., AWS ALB) to distribute traffic, while vertical scaling involves resizing an EC2 instance type (e.g., from t3.medium to t3.large), which stops the instance. Horizontal scaling is preferred for stateless applications to achieve elasticity, whereas vertical scaling is simpler but limited by the maximum instance size and often causes a brief outage during the resize.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Fundamental cloud concepts — study guide chapter
Learn the concepts, then practise the questions
- →
Fundamental cloud concepts practice questions
Targeted practice on this topic area only
- →
All GCDL questions
507 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Fundamental cloud concepts practice questions
Practise GCDL questions linked to Fundamental cloud concepts.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this GCDL question test?
Fundamental cloud concepts — This question tests Fundamental cloud concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Horizontal scaling adds more instances to distribute load; vertical scaling increases the size of existing instances. — Horizontal scaling (scale-out) adds more instances (e.g., additional virtual machines or containers) to distribute the workload across multiple nodes, improving fault tolerance and capacity. Vertical scaling (scale-up) increases the resources (CPU, RAM, storage) of an existing instance, often hitting hardware limits and requiring downtime. Option B correctly captures this distinction.
What should I do if I get this GCDL question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.