Rapid Elasticity for Seasonal Workloads
An administrator is reviewing a request from users who need to avoid overprovisioning for a seasonal workload. Cloud concept or benefit best matches this requirement?
Quick Answer
Rapid elasticity is the NIST cloud characteristic that directly addresses avoiding overprovisioning for a seasonal workload, because it is specifically the ability to scale capacity outward during periods of high demand and back inward once demand subsides, ideally with minimal or no manual intervention. Overprovisioning happens when an organisation sizes its infrastructure for a peak that only occurs occasionally, leaving expensive capacity sitting idle the rest of the year — elasticity solves exactly that inefficiency by letting the cloud environment expand only when needed and contract afterward, so cost tracks actual usage rather than worst-case planning. This is a different concern from resource pooling, which is about sharing infrastructure across tenants, or measured service, which is about how usage gets billed — elasticity is specifically about the sizing and timing of capacity itself. Seasonal or bursty workload scenarios on this exam are almost always pointing at rapid elasticity as the concept being tested.
⚠ Common exam trap
Many candidates confuse operational tools (like Planner) or security features (like DLP and sensitivity labels) with core cloud architectural benefits, failing to recognize that rapid elasticity is the specific NIST-defined characteristic that directly addresses overprovisioning for variable workloads.
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
✓
Rapid elasticity
Rapid elasticity is a core cloud computing characteristic defined by NIST (SP 800-145) that allows resources to scale out and in automatically based on demand. For a seasonal workload, this means the cloud can provision additional compute or storage capacity during peak periods and release it when demand drops, preventing overprovisioning and optimizing costs.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Data Loss Prevention (DLP)
Why it's wrong here
DLP inspects and blocks sensitive data flows; it has no capacity or scaling function, so it cannot address overprovisioning. Elastic scaling, where resources expand and contract with demand, is the cloud benefit that matches a seasonal workload. DLP would be correct when the requirement is preventing leakage of regulated information.
- ✗
Sensitivity labels
Why it's wrong here
Sensitivity labels classify and protect documents and emails; they do not govern compute capacity, so they cannot prevent overprovisioning. Elastic scaling of resources to match seasonal demand is the benefit required. Sensitivity labels would be correct when the requirement is applying persistent classification and encryption to information.
- ✗
Microsoft Planner
Why it's wrong here
Microsoft Planner is a task and work-management tool; it neither provisions nor scales compute, so it cannot prevent overprovisioning. Elasticity, matching capacity to seasonal demand, is the relevant cloud benefit. Planner would be the right choice when the requirement is organising team tasks and project deliverables.
- ✓
Rapid elasticity
Why this is correct
Rapid elasticity matches the requirement because it lets resources scale out automatically during seasonal peaks and scale back in afterwards, so capacity tracks demand rather than being provisioned for worst-case load. This directly prevents overprovisioning, since you pay only for what the workload actually consumes.
Go deeper
Related to this question
About these practice questions
Courseiva writes every MS-900 question from scratch — 794 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on MS-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A compliance-aware administrator is selecting the right Microsoft 365 capability to add and remove capacity quickly when demand changes. Cloud concept or benefit best matches this requirement?
easy- ✓ A.Rapid elasticity
- B.Microsoft Planner
- C.Data Loss Prevention (DLP)
- D.Sensitivity labels
Why A: Rapid elasticity is a core cloud computing concept defined by NIST (SP 800-145) that allows resources to be provisioned and released automatically in response to demand. In Microsoft 365, this is demonstrated by the ability to add or remove user licenses (e.g., via the Microsoft 365 admin center or PowerShell) on a per-seat basis, scaling capacity up or down almost instantly without manual infrastructure changes.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This MS-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 MS-900 exam.