Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Dynamic Autoscaling Handles CPU Spikes and Idle Periods
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An e-commerce company experiences unpredictable traffic surges during flash sales and very low traffic during overnight hours. The organization wants its cloud architecture to automatically add compute instances when CPU usage exceeds 80% and automatically remove unneeded instances when demand subsides, ensuring optimal performance while minimizing unnecessary hosting costs.
Which cloud computing concept and capability directly addresses these requirements?
Explanations
Fault tolerance using availability zones
Fault tolerance using availability zones
What Availability Zones Are
Fault tolerance is the ability of a system to continue functioning without interruption when individual hardware or software components fail. Azure Availability Zones are physically distinct, isolated datacenter locations within an Azure region, equipped with independent power, cooling, and networking infrastructure.
Why It Doesn't Meet the Requirement
- Does not scale resources dynamically: Distributing virtual machines across availability zones protects against datacenter hardware failures but does not add instances when CPU load surges.
- Does not reduce instance count automatically: Availability zones provide physical separation for running workloads; they do not monitor metric thresholds to terminate idle compute instances.
- Focuses on hardware isolation: The primary objective is resilience against power or network outages within a single physical facility, not elastic capacity management.
Key Characteristics and Limitations
- Physical datacenter separation: Provides fault isolation within the same geographical region.
- Low latency: Connected by high-performance private fiber-optic networks for fast intra-region communication.
- Static deployment: Requires defining where instances run; it does not automatically scale instance quantities based on traffic metrics without an attached autoscale mechanism.
This Answer Would Be Correct If
The organization needed to ensure that a hardware failure or power outage in one local datacenter would not disrupt application availability.
Additional Context
Availability zones are commonly combined with Virtual Machine Scale Sets to create zone-redundant, autoscaling workloads, but the fault-tolerant zone placement itself does not perform the elastic scaling.
Predictability using manual provisioning
Predictability using manual provisioning
What Manual Provisioning Is
Manual provisioning refers to the practice where system administrators explicitly configure, deploy, size, and deallocate compute instances by hand using tools like the Azure portal, Azure CLI, or infrastructure-as-code scripts.
Why It Doesn't Meet the Requirement
- Lacks automated responsiveness: Flash sales and traffic spikes occur suddenly; manual provisioning requires human intervention to identify the high CPU load and launch new resources, leading to performance degradation or downtime during unexpected surges.
- Inefficient deallocation: Administrators must remember to manually scale down or deallocate resources during off-peak hours, increasing the risk of paying for idle infrastructure.
- Does not leverage cloud elasticity: Manual scaling uses cloud infrastructure in a static, traditional manner rather than taking advantage of dynamic cloud-native agility.
Key Characteristics and Limitations
- Static capacity planning: Fixes the number of instances until an administrator manually changes the configuration.
- Operational overhead: Demands continuous human monitoring and manual execution of administrative commands.
- Human latency: Introduces significant delays between demand changes and infrastructure adjustments.
This Answer Would Be Correct If
An application had perfectly predictable, unchanging resource requirements that never varied and required absolute administrator control over every deployment event without automated rules.
Additional Context
While manual scaling is supported across Azure compute resources, relying on it for unpredictable workloads contradicts core cloud agility principles and leads to either performance bottlenecks or unnecessary operational expense.
High availability using geo-redundancy
High availability using geo-redundancy
What Geo-Redundancy Is
High availability ensures that an application remains operational and accessible to users for a defined percentage of time, often achieved through redundancy. Geo-redundancy replicates applications and data across geographically separated Azure regions to safeguard operations against regional outages or natural disasters.
Why It Doesn't Meet the Requirement
- No dynamic resource scaling: Deploying applications in multiple geographic regions does not automatically expand compute capacity when CPU load spikes on existing instances.
- No automated scale-in cost savings: Maintaining redundant secondary regions increases overall infrastructure footprint and base cost rather than scaling down when idle.
- Solves resilience, not elasticity: Geo-redundancy focuses on uptime, disaster recovery, and fault isolation rather than adjusting instance counts based on performance telemetry.
Key Characteristics and Limitations
- Region-level failover: Directs user traffic to alternative regions using global traffic routing tools if the primary region encounters downtime.
- Data replication: Synchronizes state and storage assets asynchronously or synchronously across regions.
- Cost overhead: Running continuous duplicate infrastructure across secondary regions increases fixed compute and storage costs.
This Answer Would Be Correct If
A business required zero downtime during a catastrophic regional datacenter failure and needed automated failover of user traffic to a secondary geographic location.
Additional Context
While high availability is essential for cloud architecture, it works alongside elasticity rather than replacing it. An architecture can be both highly available across regions and elastic within each region.
Elasticity using dynamic autoscaling
Elasticity using dynamic autoscaling
What Elasticity and Autoscaling Are
Elasticity is the fundamental cloud computing principle that describes a system's ability to automatically adjust resource provisioning in real time to match fluctuating workload demands. In Microsoft Azure, this concept is implemented through dynamic autoscaling, which automatically adds (scales out) or removes (scales in) compute resources such as virtual machine instances based on performance metrics, message queue depths, or scheduled rules.
How It Meets the Scenario Requirements
- Dynamic workload adjustment: When demand spikes during flash sales and CPU utilization crosses the 80% threshold, the autoscale engine triggers a scale-out action to allocate more compute instances, maintaining responsiveness.
- Cost minimization during idle periods: When traffic subsides overnight, the autoscale engine triggers a scale-in action to deallocate surplus instances, preventing ongoing billing for unused capacity.
- Automation: Adjustments occur without manual administrator intervention by leveraging preconfigured metric thresholds and schedule profiles.
Key Advantages and Capabilities
- Automatic resource optimization: Dynamically right-sizes provisioned infrastructure to meet current user demand.
- Cost efficiency: Prevents over-provisioning during low-traffic periods, aligning cloud expenses directly with real-time utilization.
- Configurable boundaries: Allows administrators to establish minimum and maximum instance counts to control spend and enforce reliability baselines.
- Metric-based triggers: Supports triggers based on metrics like Percentage CPU, memory usage, disk throughput, or queue lengths.
Why This Is Optimal
Elasticity paired with autoscaling is specifically designed for workloads with variable, unpredictable traffic patterns. It provides the exact balance between high performance during peak traffic and cost optimization during lulls, making it superior to static over-provisioning or manual adjustments.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Platform as a Service (PaaS)
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Infrastructure as a Service (IaaS)
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Availability Zones
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Cloud Consumption-Based Model
Define cloud computing
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model
Define cloud computing
IntermediateAZ-204 Developing Solutions for Microsoft Azure Exam
Azure Blob System Properties vs User-Defined Metadata
Set and retrieve properties and metadata
Last updated Validated