A team uses a CI/CD pipeline that runs unit tests on every push to the repository. They want to ensure that TDD is effectively integrated. Which practice best supports this?

Running tests only on the main branch after merging

Running the full test suite automatically on every commit and blocking merges on failures

Running tests in a separate environment that mirrors production

Running tests only when a developer manually triggers the pipeline

A developer is testing a function that sends a configuration to a device via REST API and parses the JSON response. The function should return the status code from the response. To test this without a live API, what is the best approach?

Mock the HTTP client to return a predefined JSON response with a status code

Skip testing the function because the API is external

Use a real API endpoint in a sandbox environment

Write a test that checks the function's code for correct JSON parsing

Which of the following is a recognized benefit of adopting test-driven development?

It encourages simpler, more modular designs

It speeds up the initial development of large features

It eliminates the need for code reviews

It guarantees zero defects in production

A team is debating whether to adopt TDD for a new network automation project. They are concerned about the extra time required to write tests first. What is the strongest argument in favor of TDD?

TDD guarantees that code is 100% bug-free

TDD eliminates the need for manual testing

TDD reduces the number of defects by ensuring code is tested as it is written

A network automation team has a legacy codebase with no tests. They want to adopt TDD for new features but are concerned about the cost of maintaining a large test suite. They also want to improve code quality. Which approach best balances these concerns?

Rewrite the entire legacy codebase using TDD from scratch

Use a coverage tool to identify untested code and write tests for all of it immediately

Write tests for new features using TDD and gradually add tests for critical legacy modules

Only write tests for new features and ignore legacy code

CiscoCertified Network Associate Automation (CCNA Automation)

Domain 1Objective 3

3. Describe the Concepts of Test-Driven Development 200-901 Practice Questions (Page 2)

Part of the 1.0 Software Development and Design domain, which accounts for 15% of the 200-901 exam. Cisco does not publish an official question count, but from its 120-minute exam (~50–80 total, ~8–12 in this domain), expect 1–2 from this objective — we provide 48 practice questions to prepare you well beyond it. (estimate)

48questions here

10free pages

8concepts

15%of the exam

Questions 6–10

6application · easy
A team uses a CI/CD pipeline that runs unit tests on every push to the repository. They want to ensure that TDD is effectively integrated. Which practice best supports this?
Select an answer first
7application · medium
A developer is testing a function that sends a configuration to a device via REST API and parses the JSON response. The function should return the status code from the response. To test this without a live API, what is the best approach?
Select an answer first
8foundation · easy
Which of the following is a recognized benefit of adopting test-driven development?
Select an answer first
9application · medium
A team is debating whether to adopt TDD for a new network automation project. They are concerned about the extra time required to write tests first. What is the strongest argument in favor of TDD?
Select an answer first
10expert · hard
A network automation team has a legacy codebase with no tests. They want to adopt TDD for new features but are concerned about the cost of maintaining a large test suite. They also want to improve code quality. Which approach best balances these concerns?
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.