AZ-204 Develop Azure compute solutions Practice Question
You are designing a serverless application using Azure Functions that needs to read from an Azure Storage Blob, process the data, and write to Azure Cosmos DB. Which THREE bindings are required?
⚠ Common exam trap
Candidates often confuse input bindings with output bindings, mistakenly thinking a Cosmos DB input binding is needed to read data, when in fact the data source is Blob Storage and only an output binding to Cosmos DB is required.
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
✓
HTTP trigger
The HTTP trigger is correct because the question describes a serverless application that needs to be invoked to read from Blob Storage, process data, and write to Cosmos DB. An HTTP trigger allows the function to be started via an HTTP request, which is the typical entry point for such event-driven processing. Without a trigger, the function cannot execute; the HTTP trigger provides the necessary invocation mechanism.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
HTTP trigger
Why this is correct
An HTTP trigger allows an Azure Function to be invoked directly by an HTTP request, making it ideal for creating API endpoints, webhooks, or responding to direct user interactions. It provides a unique URL that external clients can call, passing data in the request body or query parameters to initiate the function's execution. This mechanism is fundamental for building responsive, on-demand serverless applications that react to external events.
- ✗
Cosmos DB input binding
Why it's wrong here
A Cosmos DB input binding is specifically designed to retrieve existing documents from an Azure Cosmos DB container and provide them as an input parameter to the function. If the application's requirement is solely to write new data or update existing data in Cosmos DB, an input binding is unnecessary as it implies reading operations. Therefore, for a write-focused scenario, this binding would not be required.
- ✓
Blob input binding
Why this is correct
A Blob input binding enables an Azure Function to read the content of a specified blob from Azure Blob Storage directly into the function's execution context. This binding is crucial when the function needs to process files, images, or other data stored in blobs, making the blob's content readily available as a parameter without requiring manual storage API calls. It simplifies data retrieval from storage for processing.
- ✓
Cosmos DB output binding
Why this is correct
A Cosmos DB output binding facilitates writing data from the Azure Function directly to an Azure Cosmos DB container. This binding abstracts away the complexities of the Cosmos DB SDK, allowing the function to simply return a value or assign to an output parameter, which the binding then automatically serializes and persists as a new document or updates an existing one in the specified database. It streamlines data persistence.
- ✗
Timer trigger
Why it's wrong here
A Timer trigger is used to execute an Azure Function on a recurring, predefined schedule, such as every hour, day, or at specific intervals. While it is a valid trigger type, it is typically employed for batch processing, cleanup tasks, or other scheduled operations, rather than for immediate, on-demand responses to external events like an HTTP request. For an event-driven serverless application responding to external calls, an HTTP trigger is more appropriate.
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
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.