Question 490
A newly created subflow returns no status because its output variable was never assigned before completion. Which TWO complementary steps supply the appropriate administrative response and the evidence needed to verify it? Select TWO.
Explanation
Correct Answers
Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. A subflow is reusable only when its contract and permissions are explicit; copying a flow's trigger assumptions into a shared subflow creates brittle coupling. Verify prerequisites with: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.
Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. A subflow is reusable only when its contract and permissions are explicit; copying a flow's trigger assumptions into a shared subflow creates brittle coupling. The appropriate response is: Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.
Incorrect Answers
A completed reviewed update set previews and commits successfully on test and production with expected configuration functionality. This step may apply to Update set creation completion and ordered promotion but is not one of the complementary requirements in this case. The intended pair is: Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. Together with: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.
Review order guide rules, included items, requested item quantities, variable mappings, eligibility conditions and downstream task generation. This step may apply to Service Catalog order guide and request structure but is not one of the complementary requirements in this case. The intended pair is: Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. Together with: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.
Build a supported Workflow Studio flow with an appropriate record, schedule, or service catalog trigger and narrowly scoped actions; test its conditions before activation. This step may apply to Workflow Studio trigger and action design but is not one of the complementary requirements in this case. The intended pair is: Use a reusable subflow for repeated actions across several flows, defining typed input/output contracts and avoiding hidden references to one original trigger. Together with: Inspect subflow inputs, output mappings, published version, calling flow permissions, and independent test cases. Scenario: A newly created subflow returns no status because its output variable was never assigned before completion.


