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

Questions 6–10

1. 6expert · hard

   A network automation team uses a GitLab repository for their Ansible playbooks. They want to enforce that all changes to the production branch are reviewed by at least one senior engineer and that all CI tests pass. However, they also want to allow hotfixes to be merged quickly during an outage. What is the best approach?

   • AConfigure a branch protection rule requiring one senior engineer approval and CI success, but allow temporary override during an incident with a documented exception process.
   • BRequire two senior engineer approvals for all changes, including hotfixes.
   • CDisable branch protection entirely to allow hotfixes anytime.
   • DUse a separate hotfix branch that bypasses review and CI.
   Reveal Solution Discussion Select an answer first
2. 7expert · hard

   A network automation team uses a Git branching strategy where feature branches are merged into a develop branch, and release branches are cut from develop. A developer submits a pull request to merge a feature branch into develop. The CI pipeline passes, but the reviewer notices that the feature branch is several weeks old and has many merge conflicts with the latest develop. What should the reviewer do?

   • AAsk the developer to rebase or merge the latest develop into the feature branch, resolve conflicts, and rerun CI before review continues
   • BApprove the pull request and let the merge tool resolve conflicts automatically
   • CMerge the feature branch into develop and then run CI on develop to catch any issues
   • DReject the pull request and ask the developer to recreate the feature from scratch
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   A team is starting to use code reviews. They want to ensure that reviews are effective and do not become a bottleneck. Which practice should they adopt?

   • AKeep pull requests small and review them within a reasonable time frame.
   • BSkip review for small changes to save time.
   • COnly review code at the end of each month.
   • DHave one person review all code to ensure consistency.
   Reveal Solution Discussion Select an answer first
5. 9expert · hard

   A network automation team is debating whether to adopt a formal code review process. Some team members argue that reviews are too time-consuming and that automated testing is sufficient. The team lead wants to demonstrate the value of code review beyond just finding defects. Which argument best supports the adoption of code review?

   • ACode review guarantees that all defects are found before deployment
   • BCode review eliminates the need for automated testing
   • CCode review promotes shared ownership and reduces the risk of a single point of failure
   • DCode review is faster than automated testing because it does not require configuration
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A network automation team uses GitHub for source control. They want to ensure that every change to a shared library is reviewed by a senior engineer before it is merged. Which mechanism should they use?

   • AGive every developer write access to the main branch and trust them.
   • BAsk all developers to be careful and review each other's changes informally.
   • CUse a pre-commit hook that runs a linter on the code.
   • DConfigure a branch protection rule that requires a review from a designated senior engineer.
   Reveal Solution Discussion Select an answer first