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 a Blob trigger function with a retry policy

  Why it's wrong here

  A standard Blob trigger function, even when configured with a retry policy, is fundamentally limited by the maximum execution timeout of its hosting plan. For an Azure Functions Consumption plan, this limit is 15 minutes. A retry policy will only re-execute the function from the beginning after a timeout or failure; it does not extend the duration of a single function invocation, thus failing to address the core problem of a process that exceeds the allowed execution time.

• ✗

  Increase the function timeout to 30 minutes

  Why it's wrong here

  While Azure Functions allows configuring the timeout duration, the maximum execution time for a function running on the Consumption plan is strictly capped at 15 minutes. Attempting to set a timeout value higher than this limit will be ignored or result in an error, as it is an inherent constraint of the Consumption plan's cost-effective, serverless model. To achieve a 30-minute timeout, a more expensive Premium or App Service Plan would be required.

• ✗

  Use an Event Grid trigger function to process the blob

  Why it's wrong here

  An Event Grid trigger function, despite using a different event source, operates under the same execution timeout constraints as other Azure Functions on the Consumption plan. It will still be subject to the default 10-minute or maximum 15-minute execution limit. Event Grid's role is to efficiently deliver events, not to alter the runtime environment or extend the processing duration capabilities of the triggered function itself for long-running tasks.

• ✓

  Use Durable Functions with a blob-triggered client function

  Why this is correct

  Durable Functions are purpose-built for orchestrating long-running, stateful workflows that can inherently exceed the standard Azure Functions timeout limits. A blob-triggered client function can initiate a Durable Orchestration, which then manages the execution of multiple activity functions, persisting its state between asynchronous operations. This allows the overall workflow to run for hours or even days by breaking down the large file processing into smaller, manageable, and independently executable steps.