A utility must send one approved planned-outage notice to a fixed set of accounts. An engineer, not the agent, decides whether that outage is safe to schedule. Which design fits the notice?
Select an answer to reveal the explanation.
Short Explanation
The weather radio reads the script, and the meteorologist is the one who calls the storm. You use an agent flow to send the approved notice to the fixed accounts after an engineer has marked the outage safe. The flow does not make that safety call.
Full Explanation
The notice is a fixed payload to a fixed set of accounts, which is an agent flow: take the approved text and the account list and send them. The safety decision stays with the engineer, so the flow should start only after that mark exists and should contain no step that decides the outage is safe. An agent flow that both decides the outage is safe and then sends the notice pulls a judgment into a fixed path. A prompt action that judges safety from the account list and drafts a new notice each time uses a model for two jobs the utility has already separated, and it throws away the approved wording. A custom model that approves the outage and chooses which accounts should be told replaces both the engineer and the fixed list. Exam caveat: the engineer's mark can be an input the flow requires. That input does not turn the safety decision into a flow step. Operational check: inspect the flow and confirm its inputs are the approved notice and the account list, and that it has no action that sets, clears, or otherwise changes the safety flag.