AZ-204 Develop Azure compute solutions Practice Question

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.