AZ-204 Develop Azure compute solutions Practice Question
You are planning to migrate an on-premises application to Azure App Service. The application consists of a web frontend and a background worker that processes messages from a queue. Which TWO Azure services should you use to implement this solution?
⚠ Common exam trap
A common mix-up: candidates confuse Azure Functions with Azure Logic Apps, but Logic Apps is a workflow orchestration service (not a compute service) and cannot run arbitrary code like a background worker processing queue messages.
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 Functions
Azure Functions (C) is correct because it provides a serverless compute service that can be triggered by queue messages, making it ideal for the background worker that processes messages from a queue. Azure App Service (D) is correct because it hosts the web frontend, providing a fully managed platform for web applications with built-in scaling and load balancing.
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 Kubernetes Service
Why it's wrong here
Azure Kubernetes Service (AKS) manages containerised workloads via orchestration, but the scenario specifies a single web frontend and a background worker processing queue messages—a fixed, two-component architecture that does not require the container scheduling, scaling, or cluster management that AKS provides. It is tempting because AKS is a powerful platform for microservices and distributed systems, and would be correct if the application needed to run multiple containerised services with dynamic scaling or complex service discovery.
- ✗
Azure Batch
Why it's wrong here
Azure Batch is a specialized service designed for running large-scale parallel and high-performance computing (HPC) applications efficiently in the cloud. It excels at executing many independent, compute-intensive tasks, such as rendering, simulations, or data processing, across a pool of virtual machines. This service is not suitable for a continuous background worker processing individual queue messages, as its operational model is optimized for discrete, large-scale job execution rather than event-driven, always-on processing.
- ✓
Azure Functions
Why this is correct
Azure Functions is a serverless compute service that allows you to run event-driven code without provisioning or managing infrastructure. It is an excellent choice for a background worker processing queue messages, as it can be directly triggered by new messages in an Azure Storage Queue or Service Bus Queue. This enables automatic scaling and cost-efficiency, as you only pay for the compute resources consumed when your function is actively processing messages.
- ✓
Azure App Service
Why this is correct
Azure App Service is a fully managed Platform-as-a-Service (PaaS) offering for hosting web applications, REST APIs, and mobile backends. It provides a robust environment with built-in features for scaling, patching, and continuous deployment, making it ideal for hosting the web frontend of an application. Its comprehensive support for various programming languages and frameworks simplifies the migration and ongoing management of web-facing components.
- ✗
Azure Logic Apps
Why it's wrong here
Azure Logic Apps is a cloud-based service for automating workflows and integrating systems and services with a visual designer. While it can interact with queues, its primary strength lies in orchestrating complex, stateful business processes and integrations across disparate systems, often involving multiple steps and connectors. For a simple, code-driven background worker solely processing queue messages, Azure Functions offers a more lightweight, cost-effective, and compute-focused solution without the overhead of a workflow engine.
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
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.
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.
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 →
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.