Why is it important to version build artifacts in a CI/CD pipeline?

To reduce the need for automated testing

To ensure that the exact artifact tested can be deployed to production

To speed up the compilation process

To automatically fix bugs in the source code

A CI pipeline builds a Java application and produces a JAR file. The team wants to trace which source code commit produced a specific artifact. What should be included in the artifact metadata?

The size of the artifact in bytes

The timestamp of when the artifact was downloaded

The name of the developer who triggered the build

The Git commit hash and build number

A team uses GitLab CI/CD. They have a pipeline that deploys to a staging environment. They want to automatically deploy to production only when a merge request is merged into the main branch. What is the best way to configure this?

Trigger the production job on every push to any branch.

Use a rule that triggers the production job only when the pipeline runs on the main branch and the commit is a merge commit.

Schedule the production deployment to run nightly.

Use a manual approval step in the pipeline that requires a click to deploy to production.

What is the primary purpose of a CI/CD pipeline in application deployment?

To automate the process of building, testing, and deploying application changes in a consistent and repeatable manner

To manually track and approve every code change before it is merged into the main branch

To replace the need for version control by storing all code changes in a central database

To provide a graphical interface for developers to write and edit application code

A CI pipeline runs unit tests and integration tests. The team wants to fail the pipeline early if a code change breaks existing functionality. What is the best practice for ordering the test stages?

Run unit tests first, then integration tests, and fail the pipeline if any test fails.

Run integration tests first, then unit tests, and fail only if integration tests fail.

Run unit tests and integration tests in parallel and fail the pipeline only if both fail.

Run unit tests only and skip integration tests to speed up the pipeline.

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

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 6–10

6foundation · easy
Why is it important to version build artifacts in a CI/CD pipeline?
Select an answer first
7application · medium
A CI pipeline builds a Java application and produces a JAR file. The team wants to trace which source code commit produced a specific artifact. What should be included in the artifact metadata?
Select an answer first
8expert · hard
A team uses GitLab CI/CD. They have a pipeline that deploys to a staging environment. They want to automatically deploy to production only when a merge request is merged into the main branch. What is the best way to configure this?
Select an answer first
9foundation · easy
What is the primary purpose of a CI/CD pipeline in application deployment?
Select an answer first
10application · medium
A CI pipeline runs unit tests and integration tests. The team wants to fail the pipeline early if a code change breaks existing functionality. What is the best practice for ordering the test stages?
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.