The answer is that the function app must have a storage account connection string configured, as this is a foundational requirement for Durable Functions to manage state, checkpoints, and replay history. This is critical because the orchestrator function must be deterministic—it replays execution history multiple times to recover state after a process restart or to handle async operations, and non-deterministic code like random numbers or current time would break this reliable execution model. On the Microsoft Azure Developer Associate AZ-204 exam, this concept tests your understanding of how Durable Functions ensure fault tolerance in fan-out/fan-in patterns, often appearing as a trap where candidates overlook the storage dependency or assume any code is safe inside an orchestrator. A common memory tip is to remember that "deterministic equals durable"—if your orchestrator code could produce different results on replay, it fails the core replayability test.
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE considerations are important when designing an Azure Function that uses Durable Functions for fan-out/fan-in pattern?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The orchestrator function must be deterministic.
The orchestrator function in Durable Functions must be deterministic because it replays execution history multiple times to recover state after a process restart or to handle async operations. Non-deterministic code (e.g., random numbers, current time) would produce different results on replay, breaking the reliable execution model that Durable Functions relies on for fan-out/fan-in patterns.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
The orchestrator function must be deterministic.
Why this is correct
Non-deterministic code can cause issues during replay.
Related concept
Read the scenario before looking for a memorised answer.
✓
The orchestrator function should not perform any I/O operations directly.
Why this is correct
I/O should be done in activity functions to maintain determinism.
Related concept
Read the scenario before looking for a memorised answer.
✗
Orchestration history is stored in memory to reduce latency.
Why it's wrong here
History is stored in Azure Storage (tables).
✗
The orchestrator function should be triggered by an HTTP trigger directly.
Why it's wrong here
Orchestrator functions are usually triggered by a starter function or client.
✓
The function app must have a storage account connection string configured.
Why this is correct
Durable Functions use Azure Storage for state management.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the orchestrator's role with a regular function, thinking it can perform I/O directly or be triggered by HTTP, when in fact it must be stateless and deterministic, relying on activity functions for all I/O.
Detailed technical explanation
How to think about this question
Under the hood, Durable Functions uses the Event Sourcing pattern: each orchestration event (e.g., activity completion, timer expiry) is appended to a history table in Azure Storage. During replay, the orchestrator re-executes from the beginning, but the Durable Task Framework skips any already-completed activities by reading the stored history, ensuring deterministic re-execution. In a real-world fan-out scenario (e.g., processing 10,000 orders), this replay mechanism allows the orchestrator to survive VM crashes without losing progress, but only if the orchestrator code is free of side effects like direct I/O.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The orchestrator function must be deterministic. — The orchestrator function in Durable Functions must be deterministic because it replays execution history multiple times to recover state after a process restart or to handle async operations. Non-deterministic code (e.g., random numbers, current time) would produce different results on replay, breaking the reliable execution model that Durable Functions relies on for fan-out/fan-in patterns.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.