A network automation team has just merged a large Ansible playbook change that introduced a syntax error, breaking the production deployment pipeline. The team wants to prevent this from recurring. They have a Git-based workflow and a CI system. Which action best addresses the root cause?

Assign a single senior engineer to review all playbook changes directly on the main branch

Run a syntax check only in the production environment after deployment

Require a pull request with at least one reviewer and run a syntax check in CI before merge

Add a post-merge hook that notifies the team when a playbook fails to parse

A network automation engineer submits a pull request that modifies a shared Jinja2 template used by multiple device configuration scripts. The reviewer notices the change is large and mixes a bug fix with an unrelated style refactor. What should the reviewer do to best support an effective code review process?

Reject the entire pull request and ask the author to resubmit with no changes at all

Request that the author split the change into separate pull requests for the bug fix and the refactor

Review only the bug fix portion and ignore the refactor because it is style-related

Approve the change quickly because the author is experienced and the refactor is cosmetic

A network automation team is considering whether to invest in a code review process for their infrastructure-as-code repository. The repository contains Ansible playbooks and Terraform configurations. Management is skeptical because the code is not a traditional software product. Which benefit is most compelling in this context?

Reduced need for documentation because the code is self-explanatory

Elimination of the need for testing infrastructure changes

Improved performance of the network devices through better code

Early detection of configuration errors that could cause network outages

A network automation team is starting to use code reviews for their Ansible roles. The team is small and everyone is busy. They want to adopt a process that is effective without causing excessive delays. Which practice best aligns with the principles of code review?

Keep pull requests small and review them within a defined service-level agreement (SLA)

Only review changes that are larger than 500 lines of code

Review all changes in a single weekly meeting to minimize interruptions

Allow any team member to merge their own code after a self-review

CiscoCertified Network Associate Automation (CCNA Automation)

Domain 5Objective 13

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

Part of the 5.0 Infrastructure and Automation domain, which accounts for 20% of the 200-901 exam. Cisco does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–16 in this domain), expect 1–1 from this objective — we provide 46 practice questions to prepare you well beyond it. (estimate)

46questions here

10free pages

4concepts

20%of the exam

Questions 31–35

31application · medium
A network automation team has just merged a large Ansible playbook change that introduced a syntax error, breaking the production deployment pipeline. The team wants to prevent this from recurring. They have a Git-based workflow and a CI system. Which action best addresses the root cause?
Select an answer first
32application · medium
A network automation engineer submits a pull request that modifies a shared Jinja2 template used by multiple device configuration scripts. The reviewer notices the change is large and mixes a bug fix with an unrelated style refactor. What should the reviewer do to best support an effective code review process?
Select an answer first
33expert · hard
A network automation team is considering whether to invest in a code review process for their infrastructure-as-code repository. The repository contains Ansible playbooks and Terraform configurations. Management is skeptical because the code is not a traditional software product. Which benefit is most compelling in this context?
Select an answer first
34foundation · easy
Which tool or technique is commonly used to automate the detection of potential code issues without executing the program?
Select an answer first
35application · medium
A network automation team is starting to use code reviews for their Ansible roles. The team is small and everyone is busy. They want to adopt a process that is effective without causing excessive delays. Which practice best aligns with the principles of code review?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 200-901

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “200-901” is a trademark of its owner, used for identification only.

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

Questions 31–35

A network automation team has just merged a large Ansible playbook change that introduced a syntax error, breaking the production deployment pipeline. The team wants to prevent this from recurring. They have a Git-based workflow and a CI system. Which action best addresses the root cause?

Which tool or technique is commonly used to automate the detection of potential code issues without executing the program?

A network automation team is starting to use code reviews for their Ansible roles. The team is small and everyone is busy. They want to adopt a process that is effective without causing excessive delays. Which practice best aligns with the principles of code review?

Keep studying — 5.0 Infrastructure and Automation