A developer resumes an agent-assisted fix from yesterday. The previous Copilot CLI session produced a local summary, but the issue has new maintainer comments and the base branch has moved. The developer is still on yesterday’s local branch. What should the developer do first? Select one answer.
cd ~/work/orders-api
git branch --show-current
copilot/fix-timeout-187
git status --short
M src/retryPolicy.ts
git log --oneline -1
9c34aa2 agent draft: retry policy update
copilot
# Prompt:
# Continue from the previous summary and finish the fix for issue #187.Choose an answer
Tap an option to check your answer.
Correct answer: Fetch current repository state and re-read issue context.
Why this is the answer
The developer should first fetch the current repository state and re-read the issue context. Since the base branch has moved and there are new maintainer comments, the local branch is outdated. Fetching updates the local repository with changes from the remote, and re-reading the issue context ensures Copilot has the most current information, including new comments, to provide relevant assistance. Committing the modified file before fetching would create a merge conflict later. Asking Copilot to trust the previous summary would ignore the new information and potentially lead to an incorrect fix. Pushing the branch and opening a draft pull request is premature, as the fix is not yet complete or updated with the latest context.
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