Match each Azure service to its primary purpose.
Drag a concept onto its matching description — or click a concept then click the description.
NoSQL globally distributed database
Serverless compute for event-driven apps
Workflow automation and integration
Enterprise message broker with queues and topics
Event routing service for pub/sub
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: Run event-driven code without managing servers
The correct matches are: Azure Functions for serverless event-driven code, Azure App Service for hosting web apps/APIs, Azure Logic Apps for workflow automation, and Azure Cosmos DB for globally distributed NoSQL database. Common confusions involve swapping the purposes of Azure Functions and Azure App Service.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Azure Functions: Run event-driven code without managing servers
Why this is correct
Azure Functions is a premier serverless compute service designed for executing small, event-driven pieces of code, often referred to as 'functions.' It automatically scales based on demand and only charges for compute resources consumed during execution, eliminating the need for developers to provision or manage underlying servers. This makes it ideal for tasks like processing messages, reacting to database changes, or running scheduled jobs.
Azure App Service: Host web applications, REST APIs, and mobile backends
Why this is correct
Azure App Service provides a fully managed Platform-as-a-Service (PaaS) environment specifically engineered for hosting traditional web applications, RESTful APIs, and mobile application backends. It offers robust capabilities for continuous deployment, built-in auto-scaling, and high availability without requiring developers to manage the underlying operating system or infrastructure. This service supports multiple languages and frameworks, simplifying the deployment and management of always-on web solutions.
Azure Logic Apps: Automate workflows and integrations between services
Why this is correct
Azure Logic Apps is a cloud-based service that enables the creation and automation of scalable workflows and business processes through a visual designer. It facilitates seamless integration between various cloud services, on-premises systems, and SaaS applications using a vast collection of pre-built connectors. This service is particularly effective for orchestrating complex integrations, data transformations, and long-running processes without writing extensive code.
Azure Cosmos DB: Globally distributed NoSQL database with low latency
Why this is correct
Azure Cosmos DB is a globally distributed, multi-model NoSQL database service that guarantees single-digit millisecond latency at the 99th percentile and offers elastic scalability. It provides high availability, automatic indexing, and supports multiple APIs, including SQL, MongoDB, Cassandra, Gremlin, and Table. This fully managed service is designed for applications requiring high throughput and low-latency access to data anywhere in the world.
Azure Functions: Host web applications, REST APIs, and mobile backends
Why it's wrong here
This statement incorrectly describes Azure Functions. While Azure Functions can expose HTTP endpoints, its primary purpose is not to host traditional, continuously running web applications or REST APIs, but rather to execute short-lived, event-triggered code snippets. Dedicated hosting for web applications, REST APIs, and mobile backends with features like continuous deployment and always-on availability is the domain of Azure App Service.
Azure App Service: Run event-driven code without managing servers
Why it's wrong here
This statement incorrectly attributes the primary purpose of Azure Functions to Azure App Service. Azure App Service is a Platform-as-a-Service (PaaS) designed for hosting persistent web applications and APIs that are typically 'always on,' not for running transient, event-driven code. The serverless, event-driven execution model, where code runs only in response to specific triggers without explicit server management, is the core offering of Azure Functions.
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
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. 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.