A developer wants Copilot CLI to create an implementation plan for a failing checkout workflow. The prompt includes the intended input issue, expected changed files, and success criteria. Review the terminal session. Which change should the developer make first? Select one answer.
cd ~
copilot
# Prompt:
# Use issue #184 as the input.
# Output a patch for the checkout retry workflow and a test update.
# Success criteria:
# - npm test passes
# - validate-agent-contract.yml passes
# - no unrelated files are changedChoose an answer
Tap an option to check your answer.
Correct answer: Start Copilot CLI inside the trusted repository.
Why this is the answer
The developer should start Copilot CLI inside the trusted repository. Copilot CLI needs to be run within the context of the repository it is intended to operate on to access relevant files, issues, and workflows. Running it from the home directory (cd ~) means it lacks the necessary repository context to understand issue 184, identify the checkout retry workflow, or generate a patch and test updates. Running gh issue view after approving file access is not the first step; Copilot CLI needs the repository context first. Adding success criteria to issue comments is a good practice but doesn't resolve the immediate problem of Copilot CLI lacking repository context. Creating a workflowdispatch run before editing is premature; the plan needs to be generated and implemented first.
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