AZ-204 Practice Question: Connect to and consume Azure services and third-party services
Which TWO Azure services can be used to implement serverless event-driven architectures?
⚠ Common exam trap
Test-takers frequently confuse Azure Batch or Azure Container Instances as serverless event-driven services because they are 'serverless' in some sense, but they lack the native event-triggering and orchestration capabilities that define serverless event-driven architectures.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Logic Apps
Azure Logic Apps is correct because it provides a fully managed integration platform for orchestrating workflows that respond to events from various sources, such as HTTP requests, Azure services, or third-party apps, using a visual designer and connectors. Azure Functions is correct because it offers event-driven compute capabilities where code executes in response to triggers like HTTP requests, queue messages, or timer events, enabling serverless architectures without managing infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Batch
Why it's wrong here
Azure Batch is designed for running large-scale parallel and high-performance computing (HPC) applications efficiently in the cloud. While it manages compute resources for you, it requires defining and managing pools of virtual machines, which are then used to execute scheduled jobs. This model involves explicit resource provisioning and job scheduling rather than the automatic, event-driven scaling and complete infrastructure abstraction characteristic of serverless computing.
- ✓
Azure Logic Apps
Why this is correct
Azure Logic Apps provide a serverless platform for building automated workflows that integrate applications, data, services, and systems. They operate on a consumption-based billing model, where you only pay for executed actions, and automatically scale based on demand without requiring any server or infrastructure management. Logic Apps are inherently event-driven, triggered by various connectors, making them a prime example of serverless orchestration.
- ✓
Azure Functions
Why this is correct
Azure Functions is a serverless compute service that enables you to run small pieces of code, or "functions," in response to various events without explicitly provisioning or managing infrastructure. It automatically scales based on the incoming event volume and offers a consumption plan where you only pay for the compute resources consumed during execution. This FaaS (Function-as-a-Service) model is a cornerstone of serverless application development.
- ✗
Azure Container Instances
Why it's wrong here
Azure Container Instances (ACI) offers a fast and simple way to run containers in Azure without managing virtual machines or higher-level services. While ACI abstracts away the underlying server infrastructure, you still explicitly provision and manage individual container instances, defining their CPU and memory resources. It lacks the automatic, event-driven scaling and consumption-based billing model that defines true serverless computing, making it more of a container-as-a-service offering.
- ✗
Azure Virtual Machines
Why it's wrong here
Azure Virtual Machines (VMs) fall under the Infrastructure-as-a-Service (IaaS) category, providing complete control over the operating system and software stack. Implementing solutions with VMs requires manual provisioning, configuration, and ongoing management of the underlying servers, including patching, scaling, and maintenance. This hands-on server management and explicit resource allocation directly contradict the fundamental principles of serverless computing, which abstracts away all infrastructure concerns.
Quick reference
Cloud Service Model Comparison
| 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
Related to this question
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 →
JA
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.