AZ-204 Develop Azure compute solutions Practice Question
You have implemented a long-running order processing workflow using Azure Durable Functions. The orchestration may run for hours and involves multiple activity functions. You need to monitor the status of all running orchestrations and receive alerts when an orchestration fails. Which approach provides the most comprehensive and real-time monitoring?
⚠ Common exam trap
Candidates often assume Azure Monitor is the primary monitoring tool, but for Durable Functions, Application Insights is the recommended and most comprehensive solution because it natively captures orchestration-specific telemetry without custom instrumentation.
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
✓
Enable Application Insights for the Functions app and use its telemetry to monitor orchestration execution and set alerts.
Application Insights provides comprehensive, real-time monitoring for Durable Functions by automatically capturing orchestration lifecycle events, including failures, retries, and durations. It enables proactive alerting on failure metrics (e.g., 'orchestration-failed') without polling, and offers rich diagnostic tools like distributed tracing and custom querying. This is the most integrated and feature-rich approach for monitoring long-running orchestrations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the Durable Functions HTTP API to poll the status of each orchestration.
Why it's wrong here
Using the Durable Functions HTTP API to poll the status of each orchestration is inefficient and impractical for monitoring a large number of long-running workflows. While the API allows querying the status of a *specific* orchestration instance by its ID, it does not provide a consolidated view of all running orchestrations, nor does it offer built-in mechanisms for proactive failure alerts across the entire workflow fleet. Manually polling each instance would require prior knowledge of all active instance IDs and would not scale effectively for comprehensive operational oversight.
- ✗
Use Azure Monitor to create alerts on custom metrics published by the Durable Functions.
Why it's wrong here
While Azure Monitor allows publishing and alerting on custom metrics, these metrics are inherently aggregated and do not provide the detailed, instance-level telemetry required for effective monitoring and troubleshooting of individual Durable Function orchestrations. For a long-running workflow, pinpointing a failure necessitates understanding the specific orchestration instance, its execution history, inputs, and error details, which aggregated metrics cannot provide. This approach lacks the granular context needed to diagnose and resolve issues efficiently.
- ✓
Enable Application Insights for the Functions app and use its telemetry to monitor orchestration execution and set alerts.
Why this is correct
Enabling Application Insights for the Functions app is the correct approach because it automatically captures comprehensive telemetry for Durable Functions, including orchestration lifecycle events (e.g., started, completed, failed, suspended, resumed) and activity function executions. This rich, structured data, accessible via Kusto Query Language (KQL), allows for detailed monitoring of individual orchestration instances, identification of bottlenecks, and the creation of precise alerts on failed orchestrations with full contextual information, enabling rapid diagnosis and resolution.
- ✗
Use Azure Logic Apps to periodically check the orchestration status and send alerts.
Why it's wrong here
Using Azure Logic Apps to periodically check the orchestration status is an inefficient and suboptimal monitoring solution. Logic Apps are primarily workflow orchestrators themselves, not dedicated monitoring platforms, and polling would introduce unnecessary latency and resource consumption. This method would only provide high-level status checks and would lack the real-time, detailed telemetry, distributed tracing, and deep contextual insights that are crucial for effectively monitoring and troubleshooting complex, long-running Durable Functions workflows.
Go deeper
Related to this question
Learn chapter
Durable Orchestrators and Activity Functions
Key term
Application Insights
Application Insights is an Azure monitoring service that helps developers detect, diagnose, and understand issues in live web applications by collecting telemetry data like requests, exceptions, and performance counters.
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 — 883 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.