The Salesforce architect exams are some of the most rewarding and interesting exams to get. I really enjoy them because they offer a rare chance to dive very deep into a specific area of the platform. These can expand your capabilities within Salesforce, and provide you valuable understanding as you progress your career towards Technical Architect. This is the study guide for the Development Lifecycle and Deployment Designer certification exam.
Each of these exams has a study guide (like all other certifications), as well as a resource guide which has linked articles, Trailhead modules, documentation and more. To get the most out of those guides, I have written down some important areas to study and understand. If you understand the concepts below, you’ll do well on your exam.
Development Lifecycle and Deployment Designer
The Salesforce Development Lifecycle and Deployment Designer exam focuses on your understanding of development methodologies (agile, waterfall, etc.), the different stages of the development lifecycle, and deployment strategies. This includes continuous integration, version control, and sprint planning.
Which sandboxes should you use for which types of activities? How do you manage multiple work streams? You will be presented with sample scenarios, and asked which environment setup you would recommend. So think through best practices here. If a company is developing several features, how do you plan the releases? Which environments deploy into one another? How would you handle bugs found in an integration or UAT sandbox?
Which tools can you use to move metadata between orgs? You should understand the different tools available, and why you would recommend one over another. When should you recommend change sets vs. Force.com IDE? What is the Metadata API, and what are the use cases and considerations?
For some organizations, continuous integration is a requirement. So understanding the tools and drawbacks is an important piece. This article talks about the techniques.
You will be presented with many questions on the different development methodologies, and which you would recommend given a scenario. When is an agile methodology best suited? When is a waterfall methodology preferred? Think through some scenarios, and the deciding factors (i.e. defined end date, defined budget, team size, etc.)
How do you establish a governance model? What is important to consider? This trailhead maps out some key considerations.
How do you ensure adequate testing is completed in the different environments? Which sandbox(es) should handle performance and integration testing? Where should UAT be completed? How should you handle bug fixes?