13. Describe the Principles and Benefits of a Code Review Process 200-901 Practice Questions (Page 8)

Questions 36–40

1. 36foundation · easy

   How does code review contribute to knowledge sharing within a development team?

   • ABy allowing developers to review each other's code and learn from different approaches
   • BBy automatically documenting every code change without human input
   • CBy requiring all code to be written in a single programming language
   • DBy keeping each developer's code isolated from others
   Reveal Solution Discussion Select an answer first
2. 37application · medium

   A network automation team has a weekly code review meeting where developers present their changes. The team notices that many defects are found during these meetings, but the same types of defects keep appearing in new code. What is the most effective way to leverage the review process to reduce recurring defects?

   • AIncrease the frequency of review meetings to twice a week
   • BAssign a different reviewer to each meeting to get fresh perspectives
   • CAsk developers to review their own code more carefully before the meeting
   • DDocument the recurring defect patterns and add automated checks to the CI pipeline
   Reveal Solution Discussion Select an answer first
4. 38expert · hard

   A network automation team has a code review policy that requires every pull request to be reviewed by at least two team members. The team is small, and during a busy period, pull requests are waiting for days for approval, delaying critical network changes. The team lead wants to maintain quality while reducing delays. Which adjustment best balances these goals?

   • AAllow the author to merge their own pull request after 24 hours if no one has commented
   • BRequire only one reviewer but also require the author to run a linter locally
   • CReduce the required reviewers to one for low-risk changes and keep two for high-risk changes
   • DCancel the review policy and rely on CI tests to catch all issues
   Reveal Solution Discussion Select an answer first
5. 39application · medium

   A network automation team uses GitHub pull requests for code review. A developer submits a pull request that fixes a critical bug in a device configuration script. The reviewer is the only person available and is unfamiliar with the script. What should the reviewer do to follow the code review process effectively?

   • AApprove the pull request immediately because the bug is critical and time is limited
   • BAsk clarifying questions in the pull request and request the developer to add comments explaining the fix
   • CMerge the pull request and test it in production to see if the bug is fixed
   • DReject the pull request because the reviewer does not understand the script
   Reveal Solution Discussion Select an answer first
6. 40expert · hard

   A team has a code review process, but reviews often take several days, causing delays in feature delivery. They want to speed up reviews without sacrificing quality. Which change is most effective?

   • ASet a deadline for reviews but do not change the review process.
   • BLimit the size of pull requests and assign reviewers with relevant expertise.
   • CRequire all team members to review every pull request.
   • DReduce the review checklist to only style checks.
   Reveal Solution Discussion Select an answer first