試験AI-103-JPN トピック1 問題26 スレッド

Explanation:
type: ask_question
condition: approval == " approved "
The approval step must use type: ask_question because the workflow must pause and wait for a human response before the refund execution proceeds. Microsoft Foundry workflows support human-in-the-loop patterns where the workflow asks the user a question and awaits input before continuing; this pattern is explicitly intended for approval requests and clarifying questions. The workflow guidance also identifies workflows as declarative sequences that orchestrate agents and business logic, including branching logic and human-in-the-loop steps.
The refund execution step must use condition: approval == " approved " so that the second invocation of PaymentAgent runs only when the approval response matches the required approval value. Using true would always execute the refund, bypassing the approval control. Using propose_refund.output != null would only confirm that the first agent step produced output; it would not prove that a human approved the refund.
data_transformation is also incorrect for the approval node because it sets or parses values rather than pausing for user input. Reference topics: Microsoft Foundry workflows, human-in-the-loop workflow pattern, YAML workflow editing, agent orchestration, conditional execution, and workflow approval gates.