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

Questions 26–30

1. 26application · medium

   A network engineer is about to submit a large pull request that adds a new Ansible role. To make the review process smoother, what should the engineer do before requesting a review?

   • ASkip the description because the code speaks for itself.
   • BSubmit the entire change as one large commit to save time.
   • CRequest a review only after the code is merged to avoid delays.
   • DBreak the change into smaller, logical commits and provide a clear description of the purpose and testing performed.
   Reveal Solution Discussion Select an answer first
2. 27application · medium

   A network automation team uses a central Git repository for all Ansible playbooks. A junior engineer submits a pull request that modifies a shared role used by multiple playbooks. The team wants to catch integration issues early without delaying the merge. What is the most effective approach?

   • AAsk the junior engineer to explain the change in a team meeting before merging, without running any tests.
   • BMerge the pull request and then run a full regression test in production to identify any issues.
   • CHave the junior engineer self-review the change and merge it immediately to keep the repository up to date.
   • DRequire the pull request to include a successful run of the team's CI pipeline that executes the affected playbooks against a staging environment.
   Reveal Solution Discussion Select an answer first
4. 28application · medium

   A small network team has a single senior engineer who writes most of the automation code. The team wants to reduce the risk of a single point of failure and improve code quality. Which practice best addresses this concern?

   • ADocument the code thoroughly but do not change the review process.
   • BRequire all code changes to be reviewed by at least one other team member before merging.
   • CUse a static analysis tool only, without any human review.
   • DHave the senior engineer continue to write and merge code without review to maintain speed.
   Reveal Solution Discussion Select an answer first
5. 29application · medium

   A junior engineer writes a script to automate router backups. During a code review, a senior engineer suggests a more efficient way to handle errors. What is an additional benefit of this review for the junior engineer?

   • AThe junior engineer learns best practices and improves their coding skills.
   • BThe junior engineer can skip future reviews because they have learned enough.
   • CThe review reduces the need for documentation.
   • DThe review guarantees the script will never fail.
   Reveal Solution Discussion Select an answer first
6. 30application · medium

   A network automation team is considering using pair programming as a code review technique. They want to improve code quality and share knowledge between junior and senior engineers. Which statement best describes a benefit of pair programming in this context?

   • AIt eliminates the need for any other code review process
   • BIt provides real-time feedback and continuous knowledge transfer between the two engineers
   • CIt is faster than any other review method because two people work simultaneously
   • DIt guarantees that no defects will be introduced into the codebase
   Reveal Solution Discussion Select an answer first