Overview

About the Salesforce Development Lifecycle and Deployment Architect CredentialThe Salesforce Certified Development Lifecycle and Deployment Architect credential recognizes professionals who apply DevOps practices, lifecycle management, and governance strategies to Salesforce implementations. It assesses the ability to design and manage processes that support scalable and efficient development, testing, and deployment.Who This Credential Is ForThis certification is intended for individuals who:Work with DevOps processes, governance models, and deployment strategies on the Salesforce PlatformAnalyze business and technical requirements to recommend delivery frameworksCommunicate architectural decisions and trade-offs to business and IT stakeholdersCommon job titles include:Technical LeadRelease ManagerDelivery LeadEnvironment ManagerTest ManagerTechnical ArchitectOperations ManagerCandidate BackgroundTypical candidates have:2-3 years of Salesforce experience1-2 years working on Salesforce DevOps and application lifecycle managementExperience engaging with governance committees or managing deployment processesFamiliarity with agile, waterfall, and hybrid delivery methodologiesA degree in Computer Science or a related field (or equivalent experience)What You Should KnowCertified Development Lifecycle and Deployment Architects are expected to:Evaluate and recommend development methodologies based on team and project needsDesign DevOps and release management strategies aligned with business goalsUse source control systems, branching models, and continuous integration tools effectivelyApply environment management strategies, including data handling and security during releasesUnderstand and describe the use of Metadata API, Tooling API, and third-party toolsApply testing strategies, including automation and planning across releasesContribute to governance processes and recommend backup and recovery strategiesAreas Where Candidates May Need SupportCandidates might require assistance with:Environment setup and configurationWriting test code or automating testsConfiguring continuous integration and delivery pipelinesEstablishing governance processes across multiple orgsNot Required for This RoleCandidates are not expected to:Write ANT or CLI deployment scriptsSet up source control environments or CI tools from scratchExam DetailsNumber of questions: 60 multiple-choice/multiple-selectTime limit: 105 minutesPassing score: 65%Version: Based on Spring '23 releaseRegistration fee: $400 USD (plus applicable taxes)Retake fee: $200 USD (plus applicable taxes)Delivery: Online or onsite via proctored examMaterials allowed: None (closed book)Prerequisites: NoneExam OutlineThe Salesforce Development Lifecycle and Deployment Architect Exam measures a candidate's knowledge and skills related to the following objectives.Application Lifecycle Management: 8%Given the project risk and customer requirements, explain how to assess the benefits and risks of the different development methodologies and recommend the appropriate governance strategies based on the customer maturity.Planning: 13%Given a complex customer scenario, assess application lifecycle management maturity and identify the people, technology, and processes required.Understand customer environment risks and articulate appropriate mitigation strategies.Given a customer scenario, analyze and recommend the appropriate governance framework.Given a customer scenario involving a new Salesforce release (Summer, Winter, Spring), recommend the appropriate strategy to mitigate risks.System Design: 15%Explain the advantages of using agile tools to support an agile development process.Given a customer landscape and their requirements, evaluate business, technical, and architectural considerations that support the defined org strategy.Given a customer scenario, define an environment (sandbox) strategy that utilizes the correct sandbox types (for example, multiple project streams, training requirements, staging, production, and hotfixes).Given a scenario, compare, contrast, and recommend the components and tools of a successful deployment strategy.Building: 14%Given a customer scenario, explain how to use source control branching/versioning/merging, and recommend appropriate strategies.Describe the appropriate approaches to building test data strategy and unit test to ensure successful code (positive, negative, permission-based, large data volume).Given a customer scenario, describe the appropriate development model (org-based vs package-based) and development environment (scratch org vs sandboxes).Describe the methods to ensure the delivery of quality code, such as coding standards, pull requests, code review, and static code analysis.Deploying: 14%Given a scenario, describe the capabilities, limitations, and considerations when using the Metadata and Tooling APIs for deployment.Given a scenario, describe approaches to handle pre and post-deployment steps, including items not supported via the APIs.Given a scenario, describe approaches to manage and deploy technical reference data.Testing: 13%Given a customer scenario, describe and recommend an appropriate testing methodology.Given a customer testing strategy, describe the appropriate test execution methodology and coverage requirements.Given a customer scenario, describe and recommend a unified test data strategy that utilizes representative data in a secure manner throughout the development lifecycle.Releasing: 13%Given a scenario, analyze and explain the use cases and considerations when using managed, unmanaged, and unlocked packages.Apply map sandbox strategy to a specific release plan, taking into consideration multiple project streams, training requirements, staging, and hotfixes.Given a customer scenario, describe and recommend an appropriate release management strategy.Operating: 10%Given a detailed customer environment scenario including a specific request, explain the implications of incorporating the request directly in a production environment.Given a customer scenario where changes are made directly in production, explain the implications on the development lifecycle and steps to integrate changes into application lifecycle management.Given a multi-org customer scenario, compare and contrast approaches for managing common release artifacts.

Skills

Reviews