Courseiva

AZ-204 Practice Question: Connect to and consume Azure services and third-party services

Which TWO services can be used to implement serverless event-driven architectures in Azure? (Choose 2)

⚠ Common exam trap

A common mix-up: candidates confuse Azure App Service (PaaS) with serverless computing, but App Service runs continuously and requires manual scaling, whereas serverless services like Azure Functions and Logic Apps scale automatically and charge only for execution time.

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 (B) is correct because it is a fully managed, serverless workflow service that provides hundreds of connectors and triggers, enabling event-driven integration and orchestration without provisioning servers. Azure Functions (E) is correct because it is a serverless compute service that runs code in response to events via triggers and bindings (e.g., HTTP, timers, Blob Storage, Event Grid, Service Bus), which is the core of event-driven architectures. Azure Batch (A) is a job-scheduling service for large-scale parallel/HPC workloads on pools of VMs, not a serverless event-driven platform. Azure Kubernetes Service (C) is a managed Kubernetes container orchestration service requiring cluster nodes, so it is not serverless. Azure App Service (D) is a managed platform for hosting web apps and APIs on dedicated plans, not a serverless event-driven service.

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 a service designed for running large-scale parallel and high-performance computing (HPC) applications efficiently in the cloud. It provisions and manages a pool of virtual machines, schedules jobs, and handles task execution across these compute nodes. While it can process large datasets, its primary purpose is for scheduled or on-demand execution of discrete, compute-intensive tasks, rather than reacting instantaneously to real-time events in a serverless, event-driven architecture.

  • ✓

    Azure Logic Apps

    Why this is correct

    Azure Logic Apps is a cloud-based serverless platform for building automated workflows that integrate applications, data, services, and systems. It excels at orchestrating complex business processes through a visual designer, allowing developers to define triggers (like HTTP requests, new files in storage, or messages on a service bus) and subsequent actions. Its consumption-based pricing and event-driven nature make it a prime candidate for implementing serverless event-driven solutions, particularly for integration scenarios.

  • ✗

    Azure Kubernetes Service

    Why it's wrong here

    Azure Kubernetes Service (AKS) is a managed container orchestration service that simplifies deploying, managing, and scaling containerized applications using Kubernetes. While AKS offers significant flexibility and scalability for microservices, it requires managing the underlying Kubernetes cluster, including node pools and scaling configurations, which deviates from the "serverless" paradigm where the platform fully abstracts infrastructure management. It is not inherently an event-driven compute service but rather a platform for hosting such services.

  • ✗

    Azure App Service

    Why it's wrong here

    Azure App Service is a fully managed platform for building, deploying, and scaling web apps, mobile backends, and RESTful APIs. While it can host applications that consume events, App Service itself is fundamentally a Platform-as-a-Service (PaaS) for always-on web hosting, requiring explicit scaling and resource allocation. It does not provide the inherent event-driven, "scale to zero" characteristics or the direct event trigger integrations that define serverless event-driven services.

  • ✓

    Azure Functions

    Why this is correct

    Azure Functions is a serverless compute service that enables developers to run small pieces of code, or "functions," in response to a wide range of events without explicitly provisioning or managing infrastructure. It supports various triggers, such as HTTP requests, timers, messages from Azure Storage queues, Service Bus topics, or Event Hubs, making it ideal for executing discrete, event-driven logic. Functions automatically scale based on demand and are billed based on execution time and resource consumption, embodying the core principles of serverless event processing.

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

Go deeper

Related to this question

About these practice questions

This AZ-204 question is part of Courseiva's 883-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 →

How Courseiva writes practice questions · Editorial policy

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.