The below article will help you in preparing for Development Lifecycle and Deployment Designer Certification

Releases can be done in three ways

Simple – Daily

Simple changes like new reports, dashboards, list views, email templates, and user administration, chatter group etc.

Minor – Weekly

Changes that require minor fixes and unit testing with less impact like workflows, validation rules, sharing rules, assignment rules, escalation rules etc.

Major – Monthly

Major changes like App Exchange app deployment, enhancements, Apex class, trigger and VF change etc.

Change Sets:                                        

Permission and Settings Permission Sets Profiles
Standard Object/Field Permissions Yes No
Custom Object/Field Permissions Yes Yes
User Permissions Yes Yes
Page layout assignments No Yes
Record type assignments No Yes
Login IP ranges No Yes
Assigned apps No Yes
Apex class access Yes Yes
Visualforce page access Yes Yes
Assigned Apps No Yes
Add as a component Yes No


Sandbox Type Testing Development Sandbox Template Storage Interval
Developer Unit Testing Yes No 200 MB 1 Day
Developer Pro Unit Testing Yes No 1 GB 1 Day
Partial Copy Integration/UAT No Yes 5 GB 5 Days
Full Copy Regression Staging Yes Same as Prod 29 Days


  • Communicate the users within 30 mins if there is a salesforce downtime and continue to monitor the status of your organization at
  • Agile vs waterfall
  • Sandbox refresh
  • Sandbox release updates


Unit Test

  • Unit Test is done by developers and Apex test classes 

Load Test

  • Test to verify the behavior of the system for varying loads. It can be measured with TPS (transactions per second)

Performance Test

Submit Test plan with below details to Salesforce

  • A description of your tests
  • Record counts of the objects in your tests
  • The test scripts and tool (e.g., LoadRunner) that your tests will use
  • Your estimated testing loads
  • When you plan to conduct the tests
  • Your sandbox organization’s and production organization’s IDs
  • Contact information that can use to reach you during your tests        

Stress testing is not needed for SFDC 

Apex Hammer Process:

  • This process runs your org’s Apex tests in both the current and new release
  • Compares the test results before and after the release

Aloha Apps:

  • An Aloha App is Apex authorized and immune to certain edition limits
  • Very little documentation is available for this one

 Think through the following scenarios:

  1. How will you manage the development work when multiple developers are working for the same project?
  • Individual Developer sandboxes for the developers
  • Use Source Control to merge the changes in a common repository
  • Keep accountability of the changes made by individual developers
  • If there are multiple developers working in the same sandbox, there is a high risk of components being overridden
  1. How would you plan a release if there is an upcoming Salesforce release?
  • Register sandbox for Release preview
  • Plan for Apex Hammer Testing
  • If possible validate your deployment package in Prod, when deploying from a sandbox of different release
  • Review the new features of the upcoming release
  • We can never push the Salesforce release dates
  • If there are any issues/functionalities broken due to Salesforce release, we need to address them – Apex Hammer test is handy here
  • Other approach is to run all the regression tests in Salesforce release updated preview sandbox. It would be great if it’s an automated testing.
  1. Testing in Salesforce
  • Be clear that stress testing is not required for Salesforce as it’s a shared environment
  • Please go through Apex Hammer Testing
  • Regression Testing should be done in Full Copy as it will mimic production
  • Ask yourself the purpose of different sandbox w.r.t Testing, refer to the table above
  1. Tools to deploy to Production from Developer Orgs
  • com Migration Tool
  • Eclipse IDE
  • Change sets can never be used for this scenario
  1. Tool required for Automated deployment
  • com Migration Tool
  • App Exchange product like Copado
  1. What will happen if development and testing happens in the same environment
  • Testers will face errors in results while facing since there is robust development happening
  1. What would happen if an Old Sandbox is not reviewed properly for years and development done by different vendors/developers
  • Multiple triggers on the same object
  • Duplicate logic in Apex classes
  • Normally we fail to recognize the sequence of execution
  1. How to deploy Non-Metadata related components
  • No other way, document all the steps properly and execute in Destination sandbox
  1. How to delete and deploy Metadata components
  • Delete the metadata component first and then deploy the new components
  • Code coverage issues can occur if it is not handled properly
  • Whenever we delete Metadata in Prod which includes Apex Classes, the Apex classes for the entire Org is compiled and Local tests will run
  1. How to choose between Agile and Waterfall Methodology


  • Frequent change in requirements or scope of requirements is not known
  • Advantages of Agile methodology


  • Fixed Budget/timeline with a planned release date
  • Advantages of Waterfall methodology
  1. Apex Class and its related components
  • Dependent components like Custom Setting, Custom label should be deployed first and populated with proper values
  • Then Apex class can be deployed since it is dependent for test class results

Things to Remember:

  1. Necessary to know about Migration tool and IDE, but not too technical.
  2. Understand the Roles and responsibilities of the following terms.
    1. Center of Excellence
    2. Release Management Team
    3. Governance Framework
    4. Change Control Board
    5. Program Sponsor
    6. Technical Architect

I would recommend to relate these roles against your team members which helped me

  1. Source Control
  2. Agile vs Waterfall Methodology

Also, please refer to the following study materials



All the best for your exam!!!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s