A team is designing a CI pipeline for a microservices application. They want to catch integration issues early, but they also want to keep the pipeline fast so developers receive quick feedback. Which testing strategy best balances these goals?

Run unit tests and a small set of integration tests in the CI pipeline, and run a full suite of end-to-end tests in a later stage.

Run only unit tests in the CI pipeline and run integration tests manually before each release.

Run no automated tests in the CI pipeline and rely on manual testing after deployment to staging.

Run the full end-to-end test suite in the CI pipeline on every commit to ensure maximum coverage.

How does a version control system typically trigger a CI/CD pipeline?

By requiring a developer to manually copy code files to the CI/CD server

By periodically scanning the repository for changes and running the pipeline only if a new release tag is present

By sending a webhook notification to the CI/CD server when a commit is pushed to a repository

By storing compiled binaries in the repository and having the CI/CD server deploy them directly

What is the primary output of the build stage in a CI/CD pipeline?

A rollback plan for the deployment

A set of automated test results

A deployable artifact such as a compiled binary, JAR file, or container image

A list of production environment variables

A team wants to integrate security scanning into their CI/CD pipeline. They want to catch vulnerabilities in dependencies before the application is deployed. At which stage should this scanning be performed?

During the deployment stage after the application is live

During the build stage after dependencies are installed

During the version control stage before the code is committed

During the monitoring stage after release

How does monitoring integrate into a CI/CD pipeline to provide feedback?

By replacing the testing stage with real-time user monitoring

By automatically writing new features based on user behavior

By collecting metrics and logs from deployed applications and feeding them back into the pipeline for automated rollback or alerts

By storing source code changes in a monitoring database

CiscoCertified Network Associate Automation (CCNA Automation)

Domain 4Objective 4

4. Describe Components for a CI/CD Pipeline in Application Deployments 200-901 Practice Questions (Page 5)

Part of the 4.0 Application Deployment and Security 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–1 from this objective — we provide 50 practice questions to prepare you well beyond it. (estimate)

50questions here

10free pages

10concepts

15%of the exam

Questions 21–25

21application · medium
A team is designing a CI pipeline for a microservices application. They want to catch integration issues early, but they also want to keep the pipeline fast so developers receive quick feedback. Which testing strategy best balances these goals?
Select an answer first
22foundation · easy
How does a version control system typically trigger a CI/CD pipeline?
Select an answer first
23foundation · easy
What is the primary output of the build stage in a CI/CD pipeline?
Select an answer first
24application · medium
A team wants to integrate security scanning into their CI/CD pipeline. They want to catch vulnerabilities in dependencies before the application is deployed. At which stage should this scanning be performed?
Select an answer first
25foundation · easy
How does monitoring integrate into a CI/CD pipeline to provide feedback?
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.