AZ-204 Consumption plan timeout Practice Question
Your Azure Functions app (running on the Consumption plan) processes messages from an Azure Storage queue. Occasionally, the function fails due to a timeout after 5 minutes. You need to increase the maximum execution time without changing the plan. What should you do?
⚠ Common exam trap
Candidates might think that the Consumption plan has a fixed 5-minute timeout, but it can be increased to 10 minutes via the functionTimeout setting in host.json. However, if more than 10 minutes is needed, upgrading the plan is necessary.
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
✓
Set the functionTimeout property in host.json to 10 minutes
On the Consumption plan, the `functionTimeout` property in host.json can be set up to 10 minutes (default is 5 minutes). Since the function fails after 5 minutes, increasing `functionTimeout` to 10 minutes resolves the timeout without changing the plan. Option B is incorrect because migrating to Premium or Dedicated plan changes the plan, violating the constraint. Option C is incorrect because Durable Functions do not extend the per-function execution timeout; the individual function still has the same limit. Option D is incorrect because the visibility timeout affects when a message reappears, not the function's execution timeout.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Set the functionTimeout property in host.json to 10 minutes
Why this is correct
The `functionTimeout` property within the `host.json` file is the correct and most direct mechanism to adjust the execution timeout for all functions within an Azure Functions app. On the Consumption plan, this value can be increased from the default 5 minutes up to a maximum of 10 minutes. This modification directly addresses the need to extend a single function's runtime without migrating to a different hosting plan, aligning perfectly with the problem's constraints.
- ✗
Migrate the function app to the Premium or Dedicated plan
Why it's wrong here
Migrating the function app to a Premium or Dedicated plan would indeed provide significantly longer or even unlimited execution timeouts for functions, making it a viable solution for extended processing times. However, the question explicitly states the requirement to extend the timeout *without changing the existing Consumption plan*. Therefore, while technically capable of solving the timeout issue, this option violates a fundamental constraint of the problem statement.
- ✗
Use Durable Functions to split the work
Why it's wrong here
While Durable Functions are excellent for orchestrating complex, long-running workflows by chaining or fanning out activity functions, they do not inherently extend the execution timeout for an *individual* activity function. Each activity function still operates under the standard timeout limits of the hosting plan, typically 5 minutes on Consumption, unless explicitly configured otherwise in `host.json`. Therefore, splitting work helps with overall workflow duration but doesn't bypass the per-function timeout constraint.
- ✗
Increase the visibility timeout of the queue message
Why it's wrong here
Increasing the visibility timeout of a queue message primarily affects how long a message remains invisible to other consumers after it has been dequeued by a function. This mechanism prevents multiple functions from processing the same message concurrently and dictates when a message becomes available for re-processing after a failure. It has no direct impact on the actual execution duration limit imposed on the Azure Function itself by the hosting environment.
Visual reference
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.