AZ-400 Configure processes and communications Practice Question
Which TWO practices help improve the efficiency of code reviews? (Choose two.)
⚠ Common exam trap
It's easy for candidates to think more reviewers or requiring all team members to review ensures quality, but in practice, it reduces efficiency and accountability, while small, focused PRs and checklists are proven to improve both speed and accuracy.
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
✓
Keep pull requests small and focused on a single change.
Keeping pull requests small and focused on a single change (Option A) improves code review efficiency because it reduces cognitive load on reviewers, allowing them to understand and evaluate the change quickly without context-switching. Smaller PRs also enable faster feedback loops and easier rollback if issues are found, which aligns with DevOps principles of continuous integration and delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Keep pull requests small and focused on a single change.
Why this is correct
Small, single-purpose pull requests reduce cognitive load for reviewers, allowing them to understand context quickly and catch defects more effectively. They also simplify rollbacks, bisecting regressions, and reducing merge conflicts, which shortens cycle time and accelerates feedback.
- ✗
Include multiple unrelated changes in a single pull request to reduce the number of PRs.
Why it's wrong here
Bundling unrelated changes into one pull request obscures the intent of each change, makes code review significantly harder, and increases the risk of subtle bugs passing through. It also complicates reverting or cherry-picking individual features, since rollback requires untangling all the mixed modifications.
- ✗
Assign as many reviewers as possible to ensure thoroughness.
Why it's wrong here
Assigning too many reviewers can lead to redundant feedback, coordination overhead, and delayed decisions, while diluting accountability as each reviewer assumes another will catch issues. Optimal review efficiency is achieved with a small set of knowledgeable reviewers who have context relevant to the change.
- ✗
Require that all team members review every pull request.
Why it's wrong here
Requiring every team member to review every pull request causes unnecessary delays and wastes time for those without expertise in the affected code area, leading to shallow or rubber-stamp approvals. Review effort should be routed only to relevant stakeholders who can provide meaningful, authoritative feedback.
- ✓
Use a code review checklist to ensure common issues are checked.
Why this is correct
A code review checklist standardizes the review process by ensuring consistent verification of common issues like error handling, security, performance, and style conventions. It helps catch recurring defects early, reduces reviewer bias, and improves code quality across the team by institutionalizing best practices.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Continuous integration
Continuous integration is a DevOps practice where developers frequently merge their code changes into a shared repository, with each merge triggering an automated build and test process to catch integration errors early.
Key term
Code review
A code review is a systematic examination of source code by one or more developers to find defects, improve quality, and enforce coding standards before it is merged into the main codebase.
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.