A company has a regulatory requirement to deploy changes only during a specific maintenance window that occurs once a month. They have a critical bug that needs to be fixed immediately. What is the best release management approach?

Deploy the fix to a sandbox and ask users to test there

Request an emergency maintenance window from the CAB and deploy the fix as a patch release

Wait for the next maintenance window and deploy the fix as a minor release

Deploy the fix immediately without approval to avoid delay

A company has a small team of five developers and a single production org. They plan to do weekly minor releases and need a sandbox that supports development and testing without the overhead of refreshing a full copy. Which sandbox strategy should they recommend?

No sandbox, deploy directly from production to production

One Full Copy sandbox for all developers to share

One Developer Pro sandbox for the entire team

One Developer sandbox per developer and a Partial Copy sandbox for integration testing

Which governance consideration is most important when planning a release that includes changes to custom objects storing personal data?

Deploying changes as quickly as possible

Minimizing the number of sandboxes used

Avoiding the use of version control

Ensuring compliance with data protection regulations such as GDPR

A company has a policy that all changes must be deployed within 24 hours of approval. However, their release management process requires a full regression test that takes three days. What is the best way to reconcile this conflict?

Reduce the regression test scope to fit within 24 hours

Change the policy to allow a longer deployment window that accommodates the regression testing

Deploy changes immediately after approval and skip regression testing to meet the 24-hour requirement

Run regression testing in parallel with the deployment

Which activity is part of release coordination?

Notifying stakeholders about the release schedule and expected impact

Allowing developers to deploy changes whenever they want

Keeping the release date a secret to avoid pressure

Deploying all changes at once without a schedule

SalesforceCertified Development Lifecycle and Deployment Architect

Domain 2Objective 2

Given a Customer Scenario, Describe and Recommend an Appropriate Release Management Strategy. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 3)

Part of the APPLICATION LIFECYCLE MANAGEMENT domain, which accounts for 17% of the DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT exam.

30questions here

6free pages

7concepts

17%of the exam

Questions 11–15

11expert · medium
A company has a regulatory requirement to deploy changes only during a specific maintenance window that occurs once a month. They have a critical bug that needs to be fixed immediately. What is the best release management approach?
Select an answer first
12application · medium
A company has a small team of five developers and a single production org. They plan to do weekly minor releases and need a sandbox that supports development and testing without the overhead of refreshing a full copy. Which sandbox strategy should they recommend?
Select an answer first
13foundation · easy
Which governance consideration is most important when planning a release that includes changes to custom objects storing personal data?
Select an answer first
14expert · medium
A company has a policy that all changes must be deployed within 24 hours of approval. However, their release management process requires a full regression test that takes three days. What is the best way to reconcile this conflict?
Select an answer first
15foundation · easy
Which activity is part of release coordination?
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.