AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions
Your Azure Functions app uses Durable Functions to orchestrate a workflow. The orchestration sometimes fails with a 'FunctionRuntimeException' due to a timeout. You need to increase the maximum orchestration time. What should you modify?
⚠ Common exam trap
It's easy for candidates to confuse 'functionTimeout' (for individual function execution) with 'maxOrchestrationTimeout' (for Durable Functions orchestration duration), leading them to incorrectly modify the wrong setting in host.json.
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 'maxOrchestrationTimeout' in the host.json file
D is correct because in Durable Functions, the maximum orchestration time is controlled by the 'maxOrchestrationTimeout' setting in the host.json file. This setting specifies the maximum duration an orchestration instance can run before it times out, and increasing it directly addresses the 'FunctionRuntimeException' due to timeout. The default value is 7 days, but you can extend it as needed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add an app setting 'AzureFunctionsJobHost__functionTimeout'
Why it's wrong here
Adding an app setting 'AzureFunctionsJobHost__functionTimeout' is not the correct mechanism for controlling the overall duration of a Durable Function orchestration. While environment variables can override host.json settings using the double-underscore notation, 'functionTimeout' specifically governs the execution time of individual function calls (activity, orchestrator, or entity functions), not the cumulative lifetime of an entire orchestration instance. Therefore, this setting would only affect individual steps, not the orchestration's end-to-end timeout.
- ✗
Change the Azure Storage account to a Premium account
Why it's wrong here
Changing the Azure Storage account to a Premium tier primarily impacts the performance characteristics of the underlying storage, such as latency and IOPS. While Durable Functions rely on Azure Storage for state persistence and message queues, upgrading the storage tier will improve the speed and reliability of these operations. However, it does not directly influence or extend the logical timeout duration configured for a Durable Function orchestration's execution, which is a runtime configuration setting.
- ✗
Increase the 'functionTimeout' in host.json
Why it's wrong here
Increasing the 'functionTimeout' in host.json only extends the maximum execution time for individual function executions within the app, including each replay of an orchestrator function. This setting ensures that no single activity, orchestrator, or entity function hangs indefinitely during its execution. It does not, however, control the total elapsed time an entire Durable Function orchestration instance can run from its initial start to its final completion across multiple replays and asynchronous waits.
- ✓
Set 'maxOrchestrationTimeout' in the host.json file
Why this is correct
Setting 'maxOrchestrationTimeout' in the host.json file is the correct approach because this specific configuration property, located within the 'durableTask' section, directly controls the maximum allowable wall-clock duration for a Durable Function orchestration instance. If an orchestration exceeds this configured timeout, the Durable Task Framework will automatically terminate it, preventing indefinitely running instances and ensuring proper resource management and application stability.
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
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.