Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Functions Automatic Scale Out and Scale to Zero
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.
A retail company is deploying an event-driven order processing application using serverless compute in Azure. The application experiences unpredictable traffic spikes during flash sales, followed by prolonged periods of zero customer activity.
How does the serverless compute model handle resource scaling to support these workload variations?
Explanations
The platform automatically allocates more compute instances as event demand increases and scales instances down to zero when idle without manual intervention.
The platform automatically allocates more compute instances as event demand increases and scales instances down to zero when idle without manual intervention.
What Automatic Scaling in Serverless Is
Serverless computing is an execution model where the cloud provider dynamically manages the provisioning, scaling, and maintenance of the underlying compute infrastructure. In a serverless platform such as Azure Functions, computing resources are driven entirely by events, incoming HTTP requests, or background queue messages.
How It Meets the Requirement
In this scenario, the retail application experiences unpredictable surges followed by periods of zero activity:
- Scale-out on demand: As incoming events or orders surge, the internal scale controller detects the increased load and rapidly spins up additional host instances to process workloads concurrently.
- Scale-in to zero: When event traffic subsides, the platform automatically deallocates idle compute instances, scaling all the way down to zero so you only pay for actual execution time.
- Zero manual overhead: Developers do not need to configure complex metric threshold rules or manually adjust virtual machine counts.
Key Advantages and Capabilities
- Event-driven elasticity: Compute capacity dynamically matches incoming traffic bursts almost instantaneously.
- Cost efficiency: With dynamic scaling down to zero, billing stops completely when there are no active executions.
- Abstraction of servers: Infrastructure management, capacity planning, and OS patching are completely handled by Azure.
- High availability: Workloads are automatically distributed across available host infrastructure.
Why This Is Optimal
Unlike traditional Infrastructure as a Service (IaaS) or scheduled Platform as a Service (PaaS) scaling where baseline instances must remain constantly running, serverless automatic event-driven scaling ensures zero administrative overhead and true cost-per-execution economics.
The platform maintains a fixed minimum pool of compute instances that run continuously and cannot scale down during inactive periods.
The platform maintains a fixed minimum pool of compute instances that run continuously and cannot scale down during inactive periods.
What Fixed Compute Capacity Is
A fixed instance pool (or dedicated hosting model) maintains a predetermined number of compute instances running continuously to ensure background readiness and eliminate cold start latencies. This is typical of dedicated App Service Plans or reserved capacity environments.
Why It Doesn't Meet the Requirement
- Fails true serverless elasticity: A core characteristic of pure serverless computing (such as the Azure Functions Consumption plan) is the ability to scale down to zero instances when no events are present.
- Higher idle costs: Maintaining continuous dedicated instances creates steady compute costs even during hours of total inactivity.
Key Limitations
- Incurs unnecessary operational expenditure during idle times.
- Requires manual sizing adjustments if traffic spikes exceed the allocated fixed pool capacity.
- Does not leverage automatic consumption-based cost models.
This Answer Would Be Correct If
The scenario required an App Service Dedicated plan or an Azure Functions Premium plan with pre-warmed instances enabled to strictly avoid cold-start latency at the expense of continuous billing.
Additional Context
While fixed or pre-warmed instances can prevent cold starts for latency-critical applications, pure serverless architectures default to scaling down to zero to maximize cost efficiency.
The platform scales vertically by upgrading underlying physical hardware specifications according to a predetermined schedule.
The platform scales vertically by upgrading underlying physical hardware specifications according to a predetermined schedule.
What Vertical Scaling Is
Vertical scaling (scaling up or scaling down) refers to increasing or decreasing the compute power, memory, or disk capacity of an existing individual server or virtual machine, often requiring a service restart and constrained by physical hardware limitations.
Why It Doesn't Meet the Requirement
- Incorrect scaling dimension: Serverless platforms utilize horizontal scaling (scaling out and in), dynamically provisioning or removing discrete instance units rather than resizing underlying physical server hardware.
- Unresponsive to sudden bursts: A predetermined schedule cannot effectively react to spontaneous, unpredictable spikes in event traffic during flash sales.
- Potential service disruption: Vertical scaling typically requires restarting compute instances, causing downtime or dropped connections.
Key Limitations
- Limited by physical hardware boundaries.
- Scheduled scaling does not match unexpected real-time traffic spikes.
- Resizing single instances does not provide infinite elasticity.
This Answer Would Be Correct If
You were adjusting the pricing tier of an Azure SQL Database or an individual Azure Virtual Machine during a scheduled maintenance window.
Additional Context
Cloud autoscale engines and serverless scale controllers rely predominantly on horizontal scaling to dynamically match unpredictable consumer demand without service interruptions.
The platform requires administrators to pre-allocate dedicated virtual machine instances and configure custom metric alert thresholds.
The platform requires administrators to pre-allocate dedicated virtual machine instances and configure custom metric alert thresholds.
What Manual VM Configuration Is
Manual infrastructure provisioning and threshold-based autoscaling are characteristics of traditional Infrastructure as a Service (IaaS) and dedicated hosting tiers. In these models, administrators are responsible for defining VM sizes, setting up availability sets or virtual machine scale sets, and creating specific metric rules (such as CPU or memory percentage thresholds).
Why It Doesn't Meet the Requirement
- Manual management overhead: Serverless computing eliminates the need for administrators to provision virtual machines or tune CPU thresholds.
- Inflexible scaling response: Standard VM-based autoscale rules often rely on periodic metrics aggregation (e.g., 5-minute averages), which cannot react as rapidly to instantaneous bursts of events as native serverless scale controllers.
- No zero-scale by default: Dedicated VMs typically incur ongoing costs even when processing zero requests.
Key Limitations
- Requires ongoing capacity management and monitoring.
- Lacks instantaneous event-driven provisioning.
- Incurs baseline charges regardless of actual request traffic.
This Answer Would Be Correct If
You were deploying an application on Azure Virtual Machines or standard Azure App Service Plans, where infrastructure provisioning and metric rules must be configured manually.
Additional Context
A primary benefit of serverless architecture is shifting infrastructure management responsibilities to the cloud provider, freeing developers to focus purely on business logic.
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
Azure Functions Event-Driven Serverless Compute
Describe serverless
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Serverless Computing
Describe serverless
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Serverless Computing
Describe serverless
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Serverless Consumption Plan
Describe serverless
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions and Azure SignalR Service
Describe serverless
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated