AZ-400 Configure processes and communications Practice Question
Your organization uses GitHub Copilot for pull request summaries. However, some developers report that the summaries are inaccurate. What should you do to improve the quality of Copilot-generated pull request summaries?
⚠ Common exam trap
The trap here is that candidates may overestimate the role of commit messages (Option A) in Copilot's PR summary generation, when in fact the model primarily uses the PR title and description, not the commit history, to produce the summary.
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
✓
Ask developers to write clear, structured PR titles and descriptions.
GitHub Copilot for pull request summaries relies on the PR title and description as primary input to generate accurate summaries. Clear, structured titles and descriptions provide better context for the AI model, reducing ambiguity and improving summary quality. Detailed commit messages (Option A) are not directly used by Copilot for PR summaries, as it focuses on the PR-level metadata.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Encourage developers to write more detailed commit messages.
Why it's wrong here
Copilot for PR summaries primarily analyzes the pull request's title, description, and code diff, not the commit messages. Therefore, encouraging more verbose commit messages has no direct effect on the generated PR summary, as the model does not rely on commit history for that task.
- ✓
Ask developers to write clear, structured PR titles and descriptions.
Why this is correct
Copilot's PR summary generation directly leverages the pull request title and description as key context. Clear, structured descriptions—such as separate sections for motivation, changes, and testing—help the model produce more accurate, well-organized summaries, so better input directly yields better output.
- ✗
Disable Copilot for pull requests and use manual summaries.
Why it's wrong here
Disabling Copilot and summarizing manually does not improve summary quality because the same PR context is still the basis, and manual summaries are subject to inconsistency and human bias. It also sacrifices the speed and consistency of automated generation without addressing the root cause of poor input.
- ✗
Provide a link to a documentation wiki in the PR description.
Why it's wrong here
Copilot for PR summaries operates entirely on the text and diff within the pull request itself; it cannot fetch or read content from external URLs. Adding a wiki link therefore introduces no additional context for the model, leaving the summary quality unchanged.
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 696 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.