Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Autoscale Adjusts VM Instances by Demand
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 organization hosts a customer portal on Microsoft Azure that experiences heavy traffic during regular business hours and minimal activity during nights and weekends. Under the consumption-based cloud pricing model, the organization wants to minimize costs by dynamically adjusting the number of running virtual machine instances to match user demand in real time.
Which resource optimization technique should the organization implement?
Explanations
Autoscale
Autoscale
What Autoscale Is
Autoscale is a built-in cloud management capability within Azure Monitor that automatically dynamically allocates and de-allocates compute resources—such as virtual machine instances in Azure Virtual Machine Scale Sets or Azure App Service plans—based on real-time application demand, system metrics, or defined schedules.
How It Meets the Requirements
- Dynamic Resource Allocation: Autoscale monitors performance telemetry like Percentage CPU, memory usage, or incoming queue depth and adds instances (scaling out) when load rises.
- Cost Minimization: When traffic subsides overnight and during weekends, autoscale removes instances (scaling in), aligning directly with the consumption-based model where you only pay for active compute instances when they are needed.
- Automated Rules: Organizations can configure threshold rules (such as scaling out if CPU exceeds 70% and scaling in when CPU drops below 20%) alongside minimum and maximum capacity boundaries.
Key Advantages and Capabilities
- Horizontal Scalability: Scales horizontally (in and out) across multiple identical virtual machines without needing hardware reconfigurations.
- Predictive Scaling: Supports predictive autoscale using machine learning to forecast cyclical traffic patterns and scale out ahead of demand.
- Threshold Protection: Enforces instance limits with defined minimum and maximum instances, preventing unexpected runaway costs.
- Operational Automation: Triggers webhook alerts, runbooks, or email notifications whenever a scaling event is initiated.
Why This Is Optimal
Autoscale directly optimizes spending in a variable workload environment. Rather than paying 24/7 for peak capacity or manually intervening each morning and evening, autoscale ensures the exact amount of infrastructure is provisioned dynamically to satisfy performance SLAs at the lowest possible cost.
Azure Reservations
Azure Reservations
What Azure Reservations Are
Azure Reservations (Reserved Instances) are a commitment-based purchasing option that provides significant cost savings (up to 72%) compared to standard pay-as-you-go rates in exchange for committing to consistent resource usage for a one-year or three-year term.
Why It Doesn't Meet the Requirement
- Static Usage Model: Reservations apply discounts to steady-state baseline usage rather than dynamically provisioning or de-provisioning VM instances in response to fluctuating hour-by-hour traffic.
- Continuous Billing: Purchasing reservations for peak capacity means paying for that fixed commitment even during idle overnight and weekend periods, failing to eliminate wasted spend on fluctuating workloads.
- No Automatic Scaling: Reservations do not monitor workload metrics like CPU usage or automate instance counts.
Key Characteristics and Limitations
- Requires a 1-year or 3-year upfront or monthly commitment for specific VM SKUs and regions.
- Ideal for stable, predictable workloads that run 24 hours a day, 7 days a week.
- Does not perform automated instance lifecycle management.
This Answer Would Be Correct If
The organization had a predictable, steady-state baseline workload running continuously 24/7 and wanted to commit to a 1-year or 3-year term to achieve discounted compute rates.
Additional Context
Organizations often combine reservations with autoscale by covering their minimum baseline instance count with reserved capacity and using pay-as-you-go autoscale for variable traffic bursts.
Vertical Scaling
Vertical Scaling
What Vertical Scaling Is
Vertical scaling (also known as scaling up or scaling down) refers to changing the physical capacity of an individual resource instance by upgrading or downgrading its size, such as giving an existing virtual machine more CPU cores, RAM, or faster disk performance.
Why It Doesn't Meet the Requirement
- Instance Count Remains Constant: Vertical scaling alters the size of an existing instance rather than dynamically adding or removing instances horizontally based on traffic flow.
- Service Interruption: In Azure, scaling a virtual machine up or down typically requires a restart of the VM, which introduces downtime that is inappropriate for handling real-time daytime traffic surges.
- Hardware Ceilings: Vertical scaling is constrained by hardware capacity limits within specific Azure regions and cannot seamlessly scale out across dozens of elastic nodes.
Key Characteristics and Limitations
- Increases or decreases CPU, memory, and network throughput on a single system.
- Frequently requires a machine reboot to apply configuration changes.
- Lacks native automated metric-driven rules for elastic handling of variable web traffic.
This Answer Would Be Correct If
A legacy monolithic database or single application instance required higher memory and CPU specifications on a permanent or semi-permanent basis without distributed architecture support.
Additional Context
Modern cloud-native applications are designed to be horizontally scalable and stateless, allowing autoscale to seamlessly spin up identical nodes rather than resizing single monolithic machines.
Azure Hybrid Benefit
Azure Hybrid Benefit
What Azure Hybrid Benefit Is
Azure Hybrid Benefit is a licensing program that enables organizations with existing on-premises software licenses (such as Windows Server and SQL Server covered by active Software Assurance) to apply those licenses to Azure workloads, thereby waiving the software licensing cost component on cloud VMs.
Why It Doesn't Meet the Requirement
- Licensing Focus Only: Azure Hybrid Benefit is strictly a licensing discount mechanism; it does not monitor traffic, track load, or manage resource capacity.
- No Dynamic Provisioning: It cannot start, stop, scale in, or scale out virtual machines dynamically in response to varying business hours or weekend usage drops.
- Independent of Demand: The discount applies statically to any eligible deployed instance regardless of real-time application utilization.
Key Characteristics and Limitations
- Reduces compute costs by repurposing qualifying on-premises licenses in the cloud.
- Applies specifically to OS licensing (Windows Server, Red Hat, SUSE) and database licensing (Azure SQL, SQL Server on VMs).
- Does not perform capacity planning or automated elasticity management.
This Answer Would Be Correct If
The organization already owned on-premises Windows Server or SQL Server licenses with active Software Assurance and wanted to reduce licensing fees when migrating or running VMs in Azure.
Additional Context
While Azure Hybrid Benefit optimizes license rates, operational optimization techniques like autoscale manage consumption volumes to minimize total billable hours.
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
Consumption-Based Model
Describe the consumption-based model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Consumption-Based Model
Describe the consumption-based model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
CapEx vs OpEx
Describe the consumption-based model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Consumption-Based Model
Describe the consumption-based model
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Billing Meters
Describe the consumption-based model
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated