A company wants to treat its CI/CD pipeline configuration as a first-class code artifact, subject to code review, versioning, and audit. They currently configure their Jenkins jobs through the web UI, which has led to configuration drift and unreviewed changes. Which approach best addresses this?

Export the Jenkins job configuration XML files and store them in a shared folder.

Document the manual configuration steps in a wiki page and require administrators to follow them.

Use Jenkins Job DSL or a Jenkinsfile stored in the application repository to define the pipeline as code.

Use a backup plugin to periodically save the Jenkins home directory.

A security audit requires that all changes to the CI/CD pipeline configuration be reviewed and approved by a senior engineer before they take effect. The team uses a pipeline-as-code approach. Which control should they implement?

Store the pipeline configuration in a shared drive with write access for all developers.

Require pull request reviews and branch protection on the repository that stores the pipeline configuration.

Use a post-commit hook that sends an email to the senior engineer after changes are pushed.

Allow all developers to push directly to the main branch of the pipeline repository.

A team uses a monorepo containing multiple independent services. They want to run the CI pipeline only for the services that changed in a push, to reduce build times and resource usage. They are using GitLab CI. Which approach should they use?

Use a single job that builds all services and skips tests for unchanged services.

Run all jobs on every push and rely on caching to speed up the pipeline.

Use the 'rules:changes' keyword in each service's job to conditionally run the job only when files in that service's directory change.

Manually trigger the pipeline for the service that changed.

What is the primary role of an artifact repository in a CI/CD pipeline?

To store and version build outputs so they can be retrieved for deployment

To store the source code of the application

To run automated tests on the application

To monitor the production environment for issues

What is the purpose of triggering a CI/CD pipeline on every push to a shared repository?

To detect integration issues early by building and testing each change

To ensure that only the latest commit is ever deployed to production

To automatically fix any code errors without developer intervention

To reduce the number of commits developers make

EC-CouncilCertified DevSecOps Engineer

Domain 1Objective 2

CI/CD Pipeline ECDE Practice Questions (Page 9)

Part of the DevOps and DevSecOps Foundations domain, which makes up ~22% of our current practice bank.

48questions here

10free pages

8concepts

Questions 41–45

41application · medium
A company wants to treat its CI/CD pipeline configuration as a first-class code artifact, subject to code review, versioning, and audit. They currently configure their Jenkins jobs through the web UI, which has led to configuration drift and unreviewed changes. Which approach best addresses this?
Select an answer first
42application · medium
A security audit requires that all changes to the CI/CD pipeline configuration be reviewed and approved by a senior engineer before they take effect. The team uses a pipeline-as-code approach. Which control should they implement?
Select an answer first
43expert · hard
A team uses a monorepo containing multiple independent services. They want to run the CI pipeline only for the services that changed in a push, to reduce build times and resource usage. They are using GitLab CI. Which approach should they use?
Select an answer first
44foundation · easy
What is the primary role of an artifact repository in a CI/CD pipeline?
Select an answer first
45foundation · easy
What is the purpose of triggering a CI/CD pipeline on every push to a shared repository?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to ECDE

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 EC-Council. “ECDE” is a trademark of its owner, used for identification only.