What is the primary purpose of maintaining an audit trail in source control for compliance?

To reduce the number of branches

To track who made changes, when, and why

Which branching practice is most effective for enforcing code review before changes are merged into the main branch?

Use pull requests with required approvals

Allow direct commits to the main branch

Merge all branches automatically

Delete the main branch after each release

A Salesforce team has two product lines (Sales and Service) sharing a common codebase. They release on different schedules: Sales releases monthly, Service releases quarterly. They want to minimize conflicts and support independent release cycles. What is the best branching strategy?

Use long-lived feature branches for each product line and merge to main only at release time.

Use a shared main branch with short-lived feature branches, and use release branches for each product line's release.

Use separate main branches for each product line and merge to a shared release branch.

Use a single main branch and release both product lines together.

A financial services company requires that every change to their Salesforce production org be reviewed by a senior developer and that the reviewer's approval be recorded. They use Git with Salesforce DX. What is the best way to enforce this requirement?

Use a pull request workflow where a senior developer must approve the merge to the main branch.

Use a shared branch where all developers commit, and have the senior developer review the final release.

Allow developers to merge to main directly, but require them to add a comment with the reviewer's name.

Require developers to email their changes to the senior developer for approval before committing.

A company releases a Salesforce package to production. After the release, they discover a critical bug that must be fixed immediately. They have a release branch for the current version. What is the best way to fix the bug and release it?

Create a new branch from main, fix the bug, and deploy that branch.

Fix the bug directly on main and deploy main to production.

Create a hotfix branch from the release tag, fix the bug, merge it back to the release branch, and tag the new commit.

Fix the bug on the release branch and deploy it, without tagging the new commit.

SalesforceCertified Development Lifecycle and Deployment Architect

Domain 1Objective 6

merging Can Be Used and Recommend Appropriate Strategies. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 3)

Part of the ENVIRONMENTS domain, which accounts for 15% of the DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT exam.

28questions here

6free pages

7concepts

15%of the exam

Questions 11–15

11foundation · easy
What is the primary purpose of maintaining an audit trail in source control for compliance?
Select an answer first
12foundation · easy
Which branching practice is most effective for enforcing code review before changes are merged into the main branch?
Select an answer first
13expert · hard
A Salesforce team has two product lines (Sales and Service) sharing a common codebase. They release on different schedules: Sales releases monthly, Service releases quarterly. They want to minimize conflicts and support independent release cycles. What is the best branching strategy?
Select an answer first
14application · medium
A financial services company requires that every change to their Salesforce production org be reviewed by a senior developer and that the reviewer's approval be recorded. They use Git with Salesforce DX. What is the best way to enforce this requirement?
Select an answer first
15application · medium
A company releases a Salesforce package to production. After the release, they discover a critical bug that must be fixed immediately. They have a release branch for the current version. What is the best way to fix the bug and release it?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT

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 Salesforce. “DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT” is a trademark of its owner, used for identification only.