Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Azure Functions for Ephemeral Code Without Server Management
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 startup company is developing an image-processing service in Azure. The application has the following operational requirements:
- The processing code must execute only when triggered by new image uploads (event-driven)
- Individual processing tasks are short-lived, ephemeral, and run for only a few seconds
- Costs must be minimized by automatically scaling to zero when no images are being processed
- Infrastructure management overhead, such as operating system maintenance and patching, must be eliminated
Which Azure compute option best satisfies these requirements?
Explanations
Azure Virtual Machines
Azure Virtual Machines
What Azure Virtual Machines is
Azure Virtual Machines (VMs) is an Infrastructure as a Service (IaaS) offering that provides on-demand, scalable virtualized computing resources with full administrative access to the underlying operating system and file system.
Why it doesn't meet the requirements
- High administrative overhead: Virtual machines require continuous administrative management, including manual or automated operating system patching, security updates, software configuration, and network routing setup.
- Continuous idle costs: A running virtual machine incurs compute and storage charges 24/7 regardless of whether it is actively processing data, unless manually deallocated or managed via complex custom scaling logic.
- Lacks built-in event-driven scale-to-zero: VMs do not inherently scale to zero and resume instantaneously based on application-level event triggers like file uploads without significant custom automation.
Key characteristics and limitations
- Complete OS-level control: Grants full root or administrator access, custom kernel parameters, and dedicated local file systems.
- Manual maintenance requirements: The customer remains responsible for OS maintenance, runtime dependencies, and antivirus software.
- Slower startup latency: Provisioning and booting virtual machines takes minutes compared to sub-second or rapid serverless function invocations.
This answer would be correct if
This option would be the right choice if the application required deep operating system customizations, dedicated legacy software installations, specific SQL Server versions requiring full file system access, or steady 24/7 high-utilization compute.
Additional context
Using IaaS virtual machines for brief, intermittent workloads leads to substantial resource underutilization and higher total cost of ownership (TCO).
Azure Functions
Azure Functions
What Azure Functions is
Azure Functions is a serverless Function-as-a-Service (FaaS) compute solution that enables developers to run event-driven code without managing underlying virtual machine infrastructure, operating systems, or web server configurations.
How it meets the requirements
- Event-driven execution: Azure Functions integrates natively with event triggers (such as blob storage uploads, queues, and HTTP requests) to run code immediately in response to external events.
- Optimized for ephemeral tasks: It is specifically engineered to execute short-lived, stateless, and ephemeral pieces of code rapidly upon invocation.
- Scale-to-zero cost savings: Under consumption-based billing models, instances automatically scale down to zero when idle, meaning the organization only pays for the exact compute execution time and memory consumed during active processing.
- Zero OS management overhead: As a fully managed platform service, Microsoft manages operating system patching, runtime maintenance, hardware provisioning, and cluster scaling.
Key advantages and capabilities
- Integrated Triggers and Bindings: Easily connects to input and output data sources with minimal custom integration code.
- Automatic Elastic Scaling: Seamlessly scales from zero instances to hundreds of concurrent executions during sudden traffic spikes.
- Flexible Deployment Models: Supports deploying raw application code directly or packaging dependencies into custom container images.
- Cost Efficiency for Intermittent Workloads: Drastically cuts operational spending for bursty or unpredictable execution patterns.
Why this is optimal
Compared to hosting long-running virtual machines or dedicated container clusters, Azure Functions removes continuous idle runtime costs and minimizes administrative overhead, making it the ideal choice for intermittent, event-driven compute tasks.
Azure Blob Storage containers
Azure Blob Storage containers
What Azure Blob Storage containers are
Azure Blob Storage containers are logical storage directories within an Azure Storage Account used to organize and store massive amounts of unstructured object data, such as images, videos, audio, and documents.
Why it doesn't meet the requirements
- Not a compute service: Blob containers are purely a data storage construct, not an execution engine or compute resource capable of processing images or running application code.
- Cannot execute logic: While Blob Storage can serve as the storage repository and event source (trigger) that alerts a compute service when an image is uploaded, it cannot perform the computational transformation or processing itself.
Key characteristics and limitations
- Massive object storage: Scalable repository for unstructured data with configurable access tiers (Hot, Cool, Cold, Archive).
- Access management: Supports role-based access control, shared access signatures (SAS), and anonymous public access controls.
- Storage hierarchy: Functions as a container for blobs inside a storage account, similar to a folder system.
This answer would be correct if
This option would be the correct answer if the scenario asked where the uploaded raw image files or resulting processed images should be persisted and stored securely in the cloud.
Additional context
A common beginner mistake is confusing storage "containers" in Azure Blob Storage with compute "containers" (such as Docker containers or Azure Container Instances). Storage containers hold data, whereas compute containers run application code.
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
What Azure Kubernetes Service (AKS) is
Azure Kubernetes Service (AKS) is a fully managed Kubernetes container orchestration service designed to deploy, scale, manage, and coordinate complex multi-container microservice architectures.
Why it doesn't meet the requirements
- High operational complexity: AKS introduces substantial management overhead, requiring administrators to configure Kubernetes manifests, ingress controllers, cluster networking, node pools, and cluster lifecycle upgrades.
- Base infrastructure cost: Even when container pods scale down, maintaining an active AKS cluster typically requires underlying running node VMs that incur continuous baseline infrastructure charges.
- Overkill for simple event-driven tasks: Provisioning an entire container orchestration platform to execute simple, short-lived image processing tasks creates unnecessary architectural and administrative overhead.
Key characteristics and limitations
- Full orchestration capabilities: Provides advanced traffic routing, pod auto-healing, rolling deployments, and fine-grained cluster configuration.
- DevOps team overhead: Requires specialized knowledge of Kubernetes APIs, Helm charts, container networking, and cluster security policies.
- Optimized for complex microservices: Best suited for interconnected microservice architectures running continuous workloads rather than standalone, ephemeral tasks.
This answer would be correct if
AKS would be the ideal choice if the organization needed full control over a large-scale, multi-container microservices ecosystem requiring custom networking topologies, multi-tier service meshes, and specific Kubernetes APIs.
Additional context
While AKS is a powerful enterprise orchestrator, lightweight serverless platforms like Azure Functions or Azure Container Apps are better suited when minimal infrastructure management and automatic scale-to-zero are required.
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 Kubernetes Service
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions Serverless Event-Driven Compute
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Functions vs Virtual Machines vs Containers
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Virtual Machines IaaS Full Control
Compare compute types, including containers, virtual machines, and functions
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Blob Storage Archive Tier
Describe storage account options and storage types
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