A small team of five developers works on a proprietary codebase. They need a version control system that allows them to work offline and commit locally without depending on a central server. They also want to use a cloud-based platform for code review and collaboration. Which approach best meets their needs?

Use a centralized version control system like Subversion with a cloud-hosted repository.

Use a cloud-based IDE with built-in version control and no local repository.

Use a distributed VCS like Mercurial but host the repository on a local file server only.

Use Git, a distributed VCS, with a cloud-hosted platform like GitHub or GitLab for remote collaboration.

A company uses a private Git repository to store its code. The security team wants to ensure that only authorized developers can access the repository and that all access is logged. Which combination of repository hosting features should be enabled?

Use a VPN to restrict access to the repository.

Make the repository public and rely on the hosting platform's security.

Enable two-factor authentication for all users and use SSH keys for authentication.

Use a repository hosting platform that supports role-based access control (RBAC) and audit logging.

What is the primary benefit of using feature branches in a Git workflow?

Isolating development work so changes can be reviewed and integrated separately

Automatically deploying code to production

Preventing any merge conflicts from occurring

Eliminating the need for code reviews

How does integrating SCM with a build tool enable continuous integration?

By storing build artifacts in the SCM repository

By automatically triggering a build when code is pushed to the repository

By preventing any code changes from being committed

By manually requiring developers to run builds on their local machines

Which practice helps protect source code and build pipelines from unauthorized changes?

Disabling all logging in the build pipeline

Sharing the same credentials among all developers

Implementing branch protection rules that require code reviews before merging

Allowing any team member to directly push to the main branch

EC-CouncilDevSecOps Essentials

Domain 3Objective 2

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

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 21–25

21application · medium
A small team of five developers works on a proprietary codebase. They need a version control system that allows them to work offline and commit locally without depending on a central server. They also want to use a cloud-based platform for code review and collaboration. Which approach best meets their needs?
Select an answer first
22application · medium
A company uses a private Git repository to store its code. The security team wants to ensure that only authorized developers can access the repository and that all access is logged. Which combination of repository hosting features should be enabled?
Select an answer first
23foundation · easy
What is the primary benefit of using feature branches in a Git workflow?
Select an answer first
24foundation · easy
How does integrating SCM with a build tool enable continuous integration?
Select an answer first
25foundation · easy
Which practice helps protect source code and build pipelines from unauthorized changes?
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.