A team uses Salesforce DX with scratch orgs and unlocked packages. They have a feature branch that modifies an unlocked package's metadata. A developer creates a scratch org from this feature branch to test the changes. What is the correct way to validate the package in the scratch org?

Push the source directly to the scratch org using 'sfdx force:source:push'.

Create a second scratch org from main and install the package there to compare behavior.

Deploy the source using 'sfdx force:source:deploy' to the scratch org.

Convert the source in the feature branch to a package and install it into the scratch org.

A Salesforce team of 20 developers is moving from a waterfall release model (quarterly) to continuous delivery (weekly). They have a large, complex codebase with many interdependencies. They are considering GitFlow vs. trunk-based development. Which factor is most important in deciding between the two?

The complexity of the codebase, since trunk-based development cannot handle complex code.

The number of developers on the team, since GitFlow is only for small teams.

The team's ability to keep main always releasable through feature flags and continuous integration.

The frequency of releases, since GitFlow is only for quarterly releases.

A company releases a Salesforce package to production. They need to be able to roll back to the previous version if a critical issue is found. They use Git. What is the best way to prepare for this?

Create a new branch for each release and delete the previous branch.

Keep a backup of the production org's metadata before deploying.

Tag the release commit on the release branch before deploying.

Rely on the version control history to find the previous commit.

How do unlocked packages relate to source control in Salesforce DX?

Unlocked packages are built from the source in a branch and versioned independently

Unlocked packages cannot be used with source control

Unlocked packages are stored directly in source control

Unlocked packages are the same as scratch orgs

Which branching strategy is most appropriate for maintaining a long-term support (LTS) version of a product while continuing development on the main branch?

Create a separate branch for the LTS version and apply only critical fixes to it

Delete the LTS branch after release

Use the same branch for both LTS and new development

Keep all changes on the main branch and tag the LTS release

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

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

21application · medium
A team uses Salesforce DX with scratch orgs and unlocked packages. They have a feature branch that modifies an unlocked package's metadata. A developer creates a scratch org from this feature branch to test the changes. What is the correct way to validate the package in the scratch org?
Select an answer first
22expert · hard
A Salesforce team of 20 developers is moving from a waterfall release model (quarterly) to continuous delivery (weekly). They have a large, complex codebase with many interdependencies. They are considering GitFlow vs. trunk-based development. Which factor is most important in deciding between the two?
Select an answer first
23application · medium
A company releases a Salesforce package to production. They need to be able to roll back to the previous version if a critical issue is found. They use Git. What is the best way to prepare for this?
Select an answer first
24foundation · easy
How do unlocked packages relate to source control in Salesforce DX?
Select an answer first
25foundation · easy
Which branching strategy is most appropriate for maintaining a long-term support (LTS) version of a product while continuing development on the main branch?
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.