A reviewer is investigating why a Copilot-created draft pull request failed after the agent claimed it fixed an API client generation bug. The workflow uploaded an artifact named agent-root-cause-evidence. The reviewer wants to inspect the failed run, download the artifact, and compare the agent plan with the generated output before asking Copilot for another iteration. Which conclusion is best supported by this command sequence? Select one answer.
gh pr view 318 --json headRefName,statusCheckRollup,author
gh run list --branch copilot/fix-api-client --workflow validate-agent-output --limit 3
gh run view 742913 --log-failed
gh run download 742913 --name agent-root-cause-evidence --dir ./evidence
cat ./evidence/implementation-plan.md
jq '.generatedEndpoints[] | select(.status=="failed")' ./evidence/api-client-trace.jsonChoose an answer
Tap an option to check your answer.
Correct answer: The reviewer is correlating logs, plan, and trace evidence.
Why this is the answer
The command sequence shows the reviewer systematically gathering information to understand the agent's failure. They view the pull request status, list runs on the relevant branch, and then view the logs of the failed run (gh run view 742913 --log-failed). Crucially, they download a specific artifact (agent-root-cause-evidence) and then inspect its contents: implementation-plan.md and api-client-trace.json. This process of examining the failed run's logs, the agent's plan, and the trace evidence directly supports the conclusion that the reviewer is correlating these different pieces of information to diagnose the issue. The other options are incorrect because the commands don't indicate bypassing checks, the artifact's existence doesn't prove readiness, and workflows can be rerun from the UI.
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