A CI/CD pipeline deploys to dev, test, and production environments. The team wants to ensure that the same artifact that passed testing is deployed to production. What is the best practice?

Deploy directly from source code in each environment.

Rebuild the artifact in each environment to ensure it is fresh.

Use a different artifact for production that is built separately.

Store the artifact once and reference the same artifact version in each environment deployment.

A team is building a CI/CD pipeline for a .NET application. They want to ensure that the exact binary tested in the CI stage is the one deployed to production. They also want to keep a history of all builds so they can roll back to any previous version. What should they do?

Store the compiled binary in a shared network folder and overwrite it with each new build.

Store the source code in the artifact repository and compile it during deployment.

Upload the compiled binary to an artifact repository with a unique version number and use that artifact in both testing and deployment.

Recompile the source code in each environment and use the resulting binary for deployment.

Why do CI/CD pipelines typically use separate environments like dev, test, staging, and production?

To reduce the cost of cloud infrastructure

To eliminate the need for automated testing

To isolate changes and validate them progressively before reaching production

To allow developers to bypass version control

A company uses a CI/CD pipeline that is triggered by commits to a Git repository. They want to prevent unauthorized code from being deployed to production. They also want to ensure that all changes are reviewed before they are built. Which combination of controls should they implement?

Trigger the pipeline on all branches and deploy to production from any branch.

Require pull request reviews and branch protection rules on the main branch, and configure the pipeline to trigger only on the main branch.

Allow developers to push directly to the main branch and rely on the pipeline to run tests.

Use a shared account for all developers to commit to the repository.

A team is deploying an application through a CI/CD pipeline. They have separate development, staging, and production environments. They want to ensure that the same artifact is deployed to each environment, but with environment-specific configuration. Which approach should they use?

Build a separate artifact for each environment with the environment-specific configuration embedded.

Use the same configuration for all environments and only change the artifact.

Store environment-specific configuration in the source code repository and build the artifact in each environment.

Build one artifact and apply environment-specific configuration during the deployment step for each environment.

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 9)

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 41–45

41application · medium
A CI/CD pipeline deploys to dev, test, and production environments. The team wants to ensure that the same artifact that passed testing is deployed to production. What is the best practice?
Select an answer first
42application · medium
A team is building a CI/CD pipeline for a .NET application. They want to ensure that the exact binary tested in the CI stage is the one deployed to production. They also want to keep a history of all builds so they can roll back to any previous version. What should they do?
Select an answer first
43foundation · easy
Why do CI/CD pipelines typically use separate environments like dev, test, staging, and production?
Select an answer first
44expert · hard
A company uses a CI/CD pipeline that is triggered by commits to a Git repository. They want to prevent unauthorized code from being deployed to production. They also want to ensure that all changes are reviewed before they are built. Which combination of controls should they implement?
Select an answer first
45application · medium
A team is deploying an application through a CI/CD pipeline. They have separate development, staging, and production environments. They want to ensure that the same artifact is deployed to each environment, but with environment-specific configuration. Which approach should they use?
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.