Question 340
A ServiceNow administrator finds: An incident priority flow fires for every task type because its trigger table is too broad. The intended correction must preserve access controls, business process consistency and the supported platform configuration. Which administrative change most directly addresses this specific failure?
Explanation
Correct Answer
The decisive detail is: An incident priority flow fires for every task type because its trigger table is too broad. The appropriate control is: Configure the proper Workflow Studio record or service catalog trigger, conditions, scope, and published state for the intended automation. It addresses the risk that a flow with the wrong trigger or ambiguous condition can execute repeatedly, miss requests or modify unrelated records. Check effectiveness with: A controlled transaction starts exactly the intended flow and a counterexample never triggers it.
Incorrect Answers
Workflow exception handling and integration actions: Blindly retrying state-changing actions or ignoring failed spokes can create duplicate requests and false success notifications. That mechanism alone cannot establish Workflow studio flow triggers and conditions for this question.
Workflow studio data pills subflows and action results: An incorrect pill reference or unhandled action failure can send a wrong approval or create incomplete tasks. That may be useful independently, but the missing requirement here is Workflow studio flow triggers and conditions.
Catalog fulfillment workflow stages and approvals: A flow that bypasses approval or misreports a requested-item stage can create unauthorized access or falsely signal completion. The observed issue still requires Workflow studio flow triggers and conditions; the proposed alternative tests another control.