AZ-400 Practice Question: Design and implement a source control strategy
Your organization uses GitHub Copilot for pull request summaries. A developer notices that the AI-generated summary is inaccurate. Which step should the developer take to improve the quality of future summaries?
⚠ Common exam trap
A common mix-up: candidates confuse reactive fixes (editing after generation) with proactive improvements (providing better input), leading them to choose option C instead of recognizing that the quality of AI-generated output is fundamentally driven by the quality of the input context.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Provide a detailed pull request description
Providing a detailed pull request description gives GitHub Copilot more context and structured input, which directly improves the accuracy of AI-generated summaries. Copilot's PR summary feature relies on the diff and any existing description to infer intent; a richer description reduces ambiguity and enhances the quality of the generated output.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Disable Copilot for pull requests
Why it's wrong here
Disabling Copilot for pull requests removes the AI summarization capability entirely, but it does not address the root cause of inaccuracies (e.g., ambiguous PR descriptions or insufficient diff context); the feature itself is not the problem, so summary quality remains unchanged while losing a useful automation.
- ✓
Provide a detailed pull request description
Why this is correct
A detailed pull request description provides structured context—such as motivation, scope, and testing—that Copilot uses alongside the diff to generate summaries; richer, clearer input directly improves the relevance and factual accuracy of the AI-generated output.
- ✗
Edit the description after generation
Why it's wrong here
Editing the description after generation corrects only the immediate summary instance, but does not affect Copilot's future behavior or the underlying input quality; without improving the PR description, similar inaccuracies are likely to recur on subsequent summaries.
- ✗
Ignore the inaccuracy
Why it's wrong here
Ignoring the inaccuracy leaves misleading or incomplete summary text in the pull request record, which can mislead reviewers and future readers, and it provides no corrective signal or better context to help Copilot produce more accurate output going forward.
Go deeper
Related to this question
Learn chapter
Managing Build Quality and Package Dependencies
Key term
Pull request
A pull request is a way for a developer to propose changes to a codebase and ask other team members to review and merge them into the main project.
Key term
GitHub
GitHub is a cloud-based platform for storing, tracking, and collaborating on code using Git version control.
About these practice questions
One of 823 original AZ-400 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.