A repository has a workflow that should stop agent execution unless the linked issue has the agent-approved label. A maintainer says the agent did not start even though the workflow was triggered manually. You inspect the latest workflow run. Which option best explains the behaviour? Select one answer.
Workflow: approved-agent-execution
Event: workflow_dispatch
Actor: dev-user
Run gh issue view 184 --json labels --jq '.labels[].name'
needs-review
agent-plan-posted
Run grep -qx 'agent-approved'
Error: Process completed with exit code 1.
Job result: failure
Next job: start-agent
start-agent conclusion: skippedChoose an answer
Tap an option to check your answer.
Correct answer: The approval gate blocked the agent start job.
Why this is the answer
The workflow's grep -qx 'agent-approved' command checks for the exact presence of the 'agent-approved' label. The output shows needs-review and agent-plan-posted, but not agent-approved. Since the grep command failed (exit code 1), the job concluded as failure. This failure in the current job directly caused the subsequent start-agent job to be skipped, as indicated by start-agent conclusion: skipped. This setup acts as an approval gate, preventing the agent from starting without the required label. The issue being closed is not indicated. The workflowdispatch event means pullrequest context is irrelevant. Lack of contents write permission would typically manifest as a different error, not a grep failure and subsequent job skip.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed