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.

• ✓

  Orchestration trigger with fan-out/fan-in pattern

  Why this is correct

  The Orchestration trigger with a fan-out/fan-in pattern is the ideal choice for an order processing system. This pattern allows an orchestrator function to concurrently invoke multiple activity functions (e.g., inventory check, payment processing, shipping label generation) using `Task.WhenAll` to await their collective completion. After all parallel tasks finish, the orchestrator aggregates their results before proceeding, ensuring efficient and coordinated execution of complex, multi-step workflows.

• ✗

  Entity trigger

  Why it's wrong here

  An Entity trigger is designed to interact with Durable Entities, which are stateful, actor-like objects that encapsulate data and operations. While excellent for managing shared state reliably and handling concurrent access, Entity triggers are not primarily intended for orchestrating complex, multi-step workflows that involve initiating multiple parallel tasks and then aggregating their results, which is the core requirement of a fan-out/fan-in pattern.

• ✗

  Activity trigger with retry policy

  Why it's wrong here

  An Activity trigger executes a single, atomic unit of work within a Durable Function orchestration. Although a retry policy can be configured to enhance resilience by automatically re-attempting failed operations, an Activity trigger itself does not provide the inherent capability to initiate multiple parallel tasks or to wait for and aggregate results from those concurrent executions, which is fundamental to the fan-out/fan-in pattern.

• ✗

  Timer trigger

  Why it's wrong here

  A Timer trigger initiates a function execution on a predefined schedule (e.g., every hour, daily). While suitable for periodic maintenance or batch processing tasks, it lacks the advanced capabilities of Durable Orchestrations to manage state, handle long-running workflows, or coordinate complex patterns like fan-out/fan-in, which are essential for the dynamic, event-driven, and parallel nature of an order processing system.