A company is adopting DevSecOps and wants to ensure that all code changes are tracked, reviewed, and can be traced to a specific build artifact. They are evaluating version control systems. Which capability is most important for this requirement?

The ability to support multiple users concurrently.

The ability to record every change with a unique identifier and link it to build artifacts.

The ability to create branches and tags for releases.

The ability to store binary files.

A team uses a GitHub repository for a commercial product. They want to ensure that only authorized team members can push to the main branch, and that all changes are reviewed by at least one other person. They also want to prevent accidental exposure of proprietary code. What should they configure?

Set the repository to private, add team members as collaborators, and enable branch protection on main requiring pull request reviews.

Make the repository public and rely on code owners for review.

Use a shared account for all developers to push directly to main.

Disable pull requests and require developers to merge their own branches.

Which characteristic distinguishes a distributed version control system (DVCS) from a centralized version control system (CVCS)?

Only one developer can work on a file at a time

Every developer has a full copy of the repository history locally

The central server is the only place where code is stored

It requires a constant network connection to commit changes

A development team uses GitLab for source control and Jenkins for CI/CD. They want to automatically trigger a build in Jenkins whenever a merge request is merged into the 'main' branch. The build should also run a secret scan on the codebase to prevent accidental exposure of credentials. Which configuration best achieves this?

Configure a Jenkins job that polls the GitLab repository every minute and runs the build and secret scan.

Configure a Jenkins job to run on a schedule and use a Git plugin to fetch the latest code from 'main'.

Use a GitLab webhook to notify Jenkins on merge request merge events, and configure the Jenkins job to run the build and secret scan.

Use the GitLab CI/CD pipeline to run the build and secret scan, and disable Jenkins.

EC-CouncilDevSecOps Essentials

Domain 3Objective 2

Source-Code Management and Build Tools DSE Practice Questions (Page 4)

Part of the DevSecOps Toolchain domain, which makes up ~19% of our current practice bank. EC-Council does not publish an official question count, but from its 120-minute exam (~50–80 total, ~10–15 in this domain), expect 2–3 from this objective — we provide 43 practice questions to prepare you well beyond it. (estimate)

43questions here

9free pages

10concepts

Questions 16–20

16application · medium
A company is adopting DevSecOps and wants to ensure that all code changes are tracked, reviewed, and can be traced to a specific build artifact. They are evaluating version control systems. Which capability is most important for this requirement?
Select an answer first
17application · medium
A developer is working on a feature branch and wants to incorporate the latest changes from the main branch into their branch. They want to maintain a linear history and avoid merge commits. Which Git command should they use?
Select an answer first
18application · medium
A team uses a GitHub repository for a commercial product. They want to ensure that only authorized team members can push to the main branch, and that all changes are reviewed by at least one other person. They also want to prevent accidental exposure of proprietary code. What should they configure?
Select an answer first
19foundation · easy
Which characteristic distinguishes a distributed version control system (DVCS) from a centralized version control system (CVCS)?
Select an answer first
20application · medium
A development team uses GitLab for source control and Jenkins for CI/CD. They want to automatically trigger a build in Jenkins whenever a merge request is merged into the 'main' branch. The build should also run a secret scan on the codebase to prevent accidental exposure of credentials. Which configuration best achieves this?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DSE

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

Source-Code Management and Build Tools DSE Practice Questions (Page 4)

Questions 16–20

A company is adopting DevSecOps and wants to ensure that all code changes are tracked, reviewed, and can be traced to a specific build artifact. They are evaluating version control systems. Which capability is most important for this requirement?

A developer is working on a feature branch and wants to incorporate the latest changes from the main branch into their branch. They want to maintain a linear history and avoid merge commits. Which Git command should they use?

A team uses a GitHub repository for a commercial product. They want to ensure that only authorized team members can push to the main branch, and that all changes are reviewed by at least one other person. They also want to prevent accidental exposure of proprietary code. What should they configure?

Which characteristic distinguishes a distributed version control system (DVCS) from a centralized version control system (CVCS)?

Keep studying — DevSecOps Toolchain