Given a Customer Scenario Involving a New Salesforce Release, Recommend the Appropriate Strategy to Mitigate Risk. DEVELOPMENT-LIFECYCLE-AND-DEPLOYMENT-ARCHITECT Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A customer with a heavily customized Salesforce org is planning for the upcoming Summer '25 release. They are concerned about the impact of new features and any deprecations on their existing custom code. What is the most effective first step to identify potential risks before the release becomes generally available?

   • AWait until the release is live in production and then monitor for errors.
   • BSubmit a case to Salesforce Support to request an exemption from the release.
   • CDeploy all customizations to a Developer sandbox and run a full regression test.
   • DReview the pre-release release notes and the list of critical updates in a pre-release sandbox.
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A customer is planning their release strategy for the next 12 months. They have a critical integration that is only available during a specific time of year, and they want to avoid any release during that period. They also want to minimize the number of release-related changes to their org. What is the best strategy to mitigate risk?

   • AOnly test the release that falls during the critical period and skip testing the others.
   • BDeploy all three releases at the same time at the end of the year.
   • CRequest an exemption from Salesforce to skip the release that falls during the critical period.
   • DPlan to test and deploy each of the three annual releases, but schedule the deployment of the release that falls during the critical period to a later date.
   Reveal Solution Discussion Select an answer first
4. 13application · medium

   A company is about to release a new Salesforce feature that changes the layout of the opportunity page and adds a new required field. The sales team is not aware of this change. What is the most important step to ensure a smooth transition?

   • ADeploy the change and monitor for user errors.
   • BRoll back the change if users complain.
   • CCommunicate the change to the sales team and provide training on the new field and layout.
   • DAsk the sales team to submit feedback after the release.
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A customer is concerned about how the upcoming release will affect their custom Apex code and integrations. They have a limited budget and want to focus their testing efforts on the most likely problem areas. What should they do first?

   • AUpgrade to a larger sandbox to accommodate more testing.
   • BRun a full regression test on all custom code and integrations.
   • CConduct a release impact analysis by reviewing release notes and identifying changes that affect Apex and integrations.
   • DContact Salesforce to ask which custom code will be affected.
   Reveal Solution Discussion Select an answer first
6. 15application · medium

   A customer is planning to deploy a set of changes to production using change sets. They want to minimize the risk of user disruption. What is the best practice to follow?

   • ASchedule the deployment during a low-usage maintenance window and communicate the expected downtime to users.
   • BDeploy the changes during peak business hours to ensure immediate feedback.
   • CDeploy the changes immediately after the release goes live, without notifying users.
   • DDeploy the changes without testing in a sandbox to save time.
   Reveal Solution Discussion Select an answer first