Drag a concept onto its matching description — or click a concept then click the description.
IaaS with full OS control
PaaS for web and API apps
Serverless event-driven compute
Managed job scheduling for parallel workloads
Match each Azure compute service to its execution model.
Drag a concept onto its matching description — or click a concept then click the description.
IaaS with full OS control
PaaS for web and API apps
Serverless event-driven compute
Managed job scheduling for parallel workloads
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Azure Functions: Serverless, event-driven compute that runs code in response to triggers
Azure compute services offer different execution models: Azure Functions (serverless, event-driven), Azure Logic Apps (serverless workflow), Azure Kubernetes Service (container orchestration). Common confusions involve associating serverless with containers or PaaS with orchestration.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Azure Functions: Serverless, event-driven compute that runs code in response to triggers
Why this is correct
Azure Functions provides a serverless execution model where developers can run small pieces of code, called "functions," in response to various events or triggers without managing the underlying infrastructure. It automatically scales out or in based on demand, and users only pay for the compute resources consumed during execution. This event-driven nature makes it ideal for tasks like processing messages, reacting to database changes, or executing scheduled jobs.
Azure Logic Apps: Serverless, workflow automation using pre-built connectors and triggers
Why this is correct
Azure Logic Apps offers a serverless platform for building automated workflows and integrating disparate systems using a visual designer. It leverages a vast collection of pre-built connectors to interact with hundreds of services, both within Azure and externally, orchestrating complex business processes in response to defined triggers. This service focuses on low-code/no-code integration and automation, abstracting away underlying infrastructure management.
Azure Kubernetes Service: Container orchestration for managing and scaling clusters of containerized applications
Why this is correct
Azure Kubernetes Service (AKS) is a managed container orchestration service that simplifies the deployment, management, and scaling of containerized applications using Kubernetes. It handles the operational overhead of running Kubernetes clusters, such as health monitoring and maintenance, allowing developers to focus on their applications. AKS provides a robust platform for microservices architectures, enabling efficient resource utilization and high availability for container workloads.
Azure Container Instances: Serverless, event-driven compute that runs code in response to triggers
Why it's wrong here
This description is incorrect for Azure Container Instances (ACI). While ACI provides a serverless way to run individual containers quickly without managing virtual machines or orchestration, it is not inherently event-driven in the same manner as Azure Functions. ACI instances typically run a specified container image to completion or continuously, rather than executing code snippets in direct response to specific external triggers.
Azure App Service: Container orchestration for managing and scaling clusters of containerized applications
Why it's wrong here
This statement incorrectly describes Azure App Service. Azure App Service is a Platform-as-a-Service (PaaS) offering designed for hosting web applications, REST APIs, and mobile backends, supporting various languages and deployment methods, including containers. However, it is not a container orchestration service for managing clusters of containers; that functionality is provided by services like Azure Kubernetes Service. App Service focuses on simplifying web application deployment and scaling.
Quick reference
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Learn chapter
Azure Functions Development
Key term
Durable Functions
Durable Functions is an extension of Azure Functions that lets you write stateful workflows in code, managing complex sequences of tasks, retries, and delays automatically.
Key term
Azure Functions Bindings
Azure Functions Bindings are declarative connections that link your serverless function code to Azure services or external resources, handling input and output data automatically without writing extra networking or authentication code.
About these practice questions
One of 881 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.