Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
How Serverless Eliminates Cost for 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.
A retail company is designing an ad-hoc reporting workload with intermittent and unpredictable query activity throughout the week. The workload experiences prolonged periods of inactivity where no queries are processed, and the team wants to minimize both compute costs and infrastructure management overhead.
Which operational characteristic of serverless computing provides the greatest cost benefit for this workload?
Explanations
Automatic scaling to zero and per-second billing based only on active compute usage
Automatic scaling to zero and per-second billing based only on active compute usage
What Serverless Dynamic Billing Is
Serverless computing is a cloud execution model where the cloud provider dynamically manages the allocation, provisioning, and scaling of compute resources. Resources scale automatically to meet workload demand and can scale down completely to zero during periods of inactivity.
How It Meets the Cost and Operational Requirements
- Scales to Zero During Inactivity: When no queries are running, serverless resources automatically pause or reduce compute consumption to zero, ensuring the company does not pay for idle compute capacity.
- Per-Second Billing: Serverless compute models bill consumption based on the precise duration (per second) and amount of CPU and memory consumed during query execution.
- No Infrastructure Overhead: The development team does not need to manually configure VM sizes, create virtual machine scale sets, or handle operating system patches.
Key Advantages of Serverless Computing
- Pay-for-Use Pricing: Eliminates wasted spend by billing strictly for resources utilized during active task execution.
- Reduced Operational Overhead: Cloud providers manage the underlying hardware, virtualization layer, and automated capacity provisioning.
- Elastic Scalability: Instantly absorbs sudden bursts in ad-hoc queries without requiring pre-allocated headroom.
- Event-Driven Architecture: Easily executes code and queries in response to specific system triggers or user requests.
Why This Is Optimal
For intermittent workloads with unpredictable gaps in activity, provisioned models charge continuously regardless of utilization. Serverless ensures total cost efficiency by avoiding continuous base charges when the system is idle.
Dedicated virtual machine instances that maintain constant CPU allocations
Dedicated virtual machine instances that maintain constant CPU allocations
What Dedicated Virtual Machine Instances Are
Dedicated virtual machines (VMs) represent an Infrastructure as a Service (IaaS) model where an organization provisions specific virtualized hardware instances with static allocations of CPU, memory, and storage.
Why It Doesn't Meet the Requirement
- Incurs Idle Compute Costs: A dedicated VM charges for compute every hour it remains running, even when zero queries or users are active.
- High Administrative Overhead: Administrators are responsible for configuring operating systems, installing patches, managing network security, and manually sizing instances.
- Lack of Native Scale-to-Zero: Traditional VMs do not automatically suspend compute charges during brief pauses in user queries.
Key Characteristics and Limitations
- Delivers full control over the underlying operating system and software environment.
- Requires active maintenance, updates, and capacity forecasting by the customer.
- Leads to low resource utilization and wasted budget for intermittent workloads.
This Answer Would Be Correct If
The workload required deep operating system customizations, custom software kernel drivers, or constant, non-stop processing where dedicated hardware isolation is mandated.
Additional Context
Dedicated compute instances represent the opposite end of the cloud spectrum from serverless solutions in terms of operational responsibility and billing granularity.
Fixed long-term resource reservations with upfront multi-year payment discounts
Fixed long-term resource reservations with upfront multi-year payment discounts
What Fixed Long-Term Reservations Are
Reserved instances and long-term capacity commitments are purchasing options where organizations commit to paying for a fixed amount of cloud compute over a 1-year or 3-year term in exchange for significant hourly rate discounts.
Why It Doesn't Meet the Requirement
- Continuous Billing for Inactivity: Reserved capacity incurs ongoing costs 24/7 throughout the commitment period, regardless of whether the database processes queries or sits idle.
- Requires Predictable Demand: Upfront reservations are designed for steady-state workloads with continuous usage, making them inefficient for intermittent, sporadic workloads.
- Manual Capacity Planning: The team must still estimate capacity needs in advance rather than allowing the platform to scale dynamically.
Key Characteristics and Limitations
- Provides substantial discounts for continuous baseline workloads.
- Requires financial commitments for multi-year durations.
- Does not automatically eliminate idle compute expenses during prolonged periods of inactivity.
This Answer Would Be Correct If
The company had a predictable, steady-state workload operating 24 hours a day, 7 days a week, and wanted to minimize hourly compute costs through long-term financial commitments.
Additional Context
Reserved instances belong to traditional provisioned hosting models rather than serverless architectures.
Provisioned baseline capacity that prevents cold start delays during query execution
Provisioned baseline capacity that prevents cold start delays during query execution
What Provisioned Baseline Capacity Is
Provisioned baseline capacity is a hosting configuration where a minimum threshold of compute resources (such as CPU and memory) remains permanently allocated and running to guarantee immediate responsiveness and avoid cold start latency.
Why It Doesn't Meet the Requirement
- Continuous Minimum Bill: Maintaining a fixed baseline ensures that the organization continuously pays for allocated resources even when no queries are being executed.
- Counteracts Scale-to-Zero: While keeping resources warm eliminates latency delays, it forfeits the primary cost-saving mechanism of serverless during extended idle periods.
- Not Ideal for Cost-First Strategies: If the primary objective is minimizing spend during periods of inactivity, paying for always-on baseline capacity is counterproductive.
Key Characteristics and Limitations
- Keeps compute instances pre-warmed to prevent execution startup delays.
- Establishes a permanent floor for resource billing regardless of active query demand.
- Balances performance needs against pure consumption-based pricing models.
This Answer Would Be Correct If
The organization had strict service level agreements (SLAs) requiring zero cold start latency for every initial ad-hoc query and was willing to maintain a continuous minimum compute charge.
Additional Context
Cold starts are a known operational consideration in serverless environments, but eliminating them via permanently provisioned compute increases baseline operational expenses.
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
Azure Functions Scale to Zero
Describe serverless
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions Trigger
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