The answer is that vertical scaling increases a single resource’s capacity, while horizontal scaling adds more instances. This distinction is correct because vertical scaling, often called scaling up, involves upgrading an existing virtual machine with more RAM, CPU, or disk space to handle greater demand, whereas horizontal scaling, or scaling out, distributes the workload by deploying additional identical instances, such as adding more VMs through Azure Virtual Machine Scale Sets. On the Microsoft Azure Fundamentals AZ-900 exam, this concept tests your understanding of elasticity and resource management in cloud computing, often appearing in scenario-based questions where you must choose the most cost-effective or fault-tolerant approach. A common trap is confusing scaling up with scaling out—remember that vertical is like upgrading to a bigger truck, while horizontal is adding more trucks to the fleet. For a quick memory tip, think “up for upgrade, out for more.”
AZ-900 Describe cloud concepts Practice Question
This AZ-900 practice question tests your understanding of describe 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 the difference between vertical scaling and horizontal scaling?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Vertical scaling increases a single resource's capacity; horizontal scaling adds more instances
Vertical scaling (scaling up) increases the capacity of a single resource, such as adding more RAM, CPU, or disk space to a virtual machine. Horizontal scaling (scaling out) adds more instances of a resource, distributing the load across multiple machines. This distinction is fundamental in cloud computing, where Azure Virtual Machine Scale Sets exemplify horizontal scaling by automatically adding VM instances, while resizing a VM to a larger SKU represents vertical scaling.
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.
✗
Vertical scaling adds more instances; horizontal scaling increases instance size
Why it's wrong here
This is reversed — vertical = bigger single instance; horizontal = more instances.
✓
Vertical scaling increases a single resource's capacity; horizontal scaling adds more instances
Why this is correct
Vertical: add CPU/RAM to one VM. Horizontal: add more VM instances behind a load balancer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Both vertical and horizontal scaling achieve the same result through different means
Why it's wrong here
While both handle increased load, they have different fault tolerance and cost implications.
✗
Vertical scaling is for storage; horizontal scaling is for compute
Why it's wrong here
Both scaling directions apply to compute resources, not categorized by resource type.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the terms 'scale up' (vertical) and 'scale out' (horizontal), leading them to reverse the definitions or assume both methods are functionally equivalent, when in fact they address different scalability constraints and architectural patterns.
Detailed technical explanation
How to think about this question
Under the hood, vertical scaling is limited by the maximum capacity of a single resource (e.g., a VM's max vCPU count), while horizontal scaling leverages load balancers (like Azure Load Balancer) to distribute traffic across multiple instances, enabling near-linear scalability. In real-world scenarios, a stateless web application benefits from horizontal scaling because it can add more web servers behind a load balancer, whereas a legacy monolithic database often relies on vertical scaling due to stateful constraints. Subtle behavior: horizontal scaling requires stateless design or distributed session management (e.g., Azure Redis Cache) to avoid data inconsistency across instances.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-900 question in full detail.
Describe cloud concepts — This question tests Describe cloud concepts — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Vertical scaling increases a single resource's capacity; horizontal scaling adds more instances — Vertical scaling (scaling up) increases the capacity of a single resource, such as adding more RAM, CPU, or disk space to a virtual machine. Horizontal scaling (scaling out) adds more instances of a resource, distributing the load across multiple machines. This distinction is fundamental in cloud computing, where Azure Virtual Machine Scale Sets exemplify horizontal scaling by automatically adding VM instances, while resizing a VM to a larger SKU represents vertical scaling.
What should I do if I get this AZ-900 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 →
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.
This AZ-900 practice question is part of Courseiva's free Microsoft 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 AZ-900 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.