
Explore the Salesforce platform development lifecycle and deployment architect certification, covering DevOps, CI/CD, application lifecycle management at enterprise scale, governance, stakeholder communication, and seven domains to master.
Master governance, lifecycle management, and continuous integration strategies for Salesforce architectures, covering planning, system design, building, deploying, testing, releasing, and operating across multi-org environments.
Explore how waterfall and agile frameworks shape Salesforce project planning and delivery, from requirements to iterative releases. Understand Scrum roles, the definition of done, and Lean principles for efficient deployments.
Explore the four Salesforce sandbox types: developer, developer pro, partial copy, and full sandbox, and how templates, storage limits, and refresh intervals enable safe development and testing.
Understand how Salesforce sandboxes use unique org IDs, different servers, and altered user data to protect production. Learn to verify sandbox instances, manage email deliverability, and monitor health with status.salesforce.com.
Configure full sandboxes with selective data (field history tracking, chatter data) and secure access (deactivate unused users, sandbox domain login, MFA with per-sandbox permission sets).
Enable source tracking in developer and developer pro sandboxes to let Salesforce DX tooling detect new or modified metadata and improve conflict resolution, via production org or per sandbox.
Learn how Salesforce data resides in first-party data centers, Hyperforce with AWS, GCP, and Azure, and government cloud, with encryption in transit and at rest, cloud-native scalability, security, and compliance.
Learn to manage sandbox storage by cleaning data or upgrading; metadata types don’t count toward storage, while dev sandboxes double to 400 MB and dev pro to 2 GB.
Explore how preview versus non-preview sandboxes affect Salesforce upgrade timing, enabling early access to features about six weeks before production and aligned release planning.
Manage sandbox usage within your Salesforce license by understanding the compliance timeline, where over allocation locks sandboxes and triggers eventual permanent deletion.
Learn how to create, refresh, and clone Salesforce sandboxes efficiently by understanding sandbox types, timing factors, and best practices like templates and post-copy automation.
Discover how Salesforce DataMask protects sensitive data in sandboxes by obfuscating PII and financial details. Follow practices for configurations, data filters, and bypassing workflows and triggers to ensure efficient masking.
Explore Salesforce data masking in sandboxes, learning when to use random data, library values, pattern-based masking, and delete data to protect sensitive data while supporting testing.
Install the DataMask managed package in production and assign permissions. Configure org-level settings, masking rules, filters, schedules, and custom libraries.
Understand scratch orgs, disposable Salesforce environments managed by Dev Hub, enabling fast development and CI/CD automation via CLI or GUI, with daily limits and regional hosting.
Master unlocked packages and second-generation managed packages to streamline metadata across multiple orgs with a source-driven, version-controlled DevOps workflow.
Manage scratch orgs from the dev hub and enable org shape to mirror production, sandbox, or packaging orgs, tracking active orgs and scratch org info history.
Explore version control basics with centralized and distributed systems, including Git and GitHub, and learn core concepts like commits, branches, merges, and pull requests.
Learn how to create a repository, manage branches, and open a pull request to collaborate with GitHub, preserving version history and safely merging feature changes into the main branch.
Explore how GitHub workflows drive collaborative development, using branches, commits, pull requests, reviews, testing, and merging into main, while understanding Git history, SHA-1 and SHA-256, trees, blobs, and diffs.
Use git revert to safely undo a specific commit by creating a new reversal commit that preserves history and avoids rewriting history, especially on shared branches like main or develop.
Explore the single master branch approach for Salesforce version control, merging feature branches into one master for UAT and production, highlighting simplicity alongside potential coordination and release bottlenecks.
Adopt a one-branch-per-environment approach with a feature branch per user story, using UAT and master branches for automated, predictable deployments via Copado CI/CD.
Adopt two feature branches per feature with environment branches, using feature_X from master and feature_X from UAT to enable frequent, automated releases with declarative workflows and fewer merge conflicts.
Learn how metadata defines your Salesforce org and how the metadata API moves configurations between environments using deploy/retrieve calls or source-tracking commands, aided by VS Code and the Salesforce CLI.
Master deploying and retrieving Salesforce metadata using zip packages, package.xml manifests, and component folders to move configurations between orgs; leverage Salesforce Inspector for streamlined CI/CD and version control workflows.
Learn to use the Salesforce Tooling API for fine-grained metadata access, precise deployments, and CI pipeline feedback, with field definition, entity definition, Apex class/trigger/page/component members, and code coverage tooling.
Explore how Salesforce Tooling API objects—system fields, programming objects, setup objects, tooling objects, and operational objects—work together to manage metadata, Apex classes, and deployments.
Explore unit testing in Salesforce, write apex tests, and learn why early testing saves time. Create reliable test data with brute force, factories, setup methods, and csv files.
Create a central test factory class in Apex to generate accounts, contacts, opportunities, and users, with doInsert flags for flexible, reusable test data.
Use the atTestSetup annotation to create reusable test data in Salesforce Apex, with data reset between tests to ensure isolation and clean, independent test runs.
Master unit testing patterns by implementing positive, negative, and permission-based tests that validate correct outputs, handle invalid input gracefully, and enforce access controls in enterprise applications.
This Salesforce Architect - DevOps & Deployment (CI/CD, Release) course is designed specifically to help you prepare for the Salesforce Development Lifecycle and Deployment Architect certification.
You will gain hands-on experience with Salesforce DevOps, CI/CD pipelines, release management, and lifecycle governance using real-world, exam-aligned scenarios.
About the Exam
Read on for details about the Salesforce Platform Development Lifecycle and Deployment Architect Exam.
Content: 60 multiple-choice/multiple-select questions
Time allotted to complete the exam: 105 minutes
Passing score: 65%
Version: Exam questions align to the Spring '23 release
Registration fee: US$400, plus applicable taxes as required per local law
Retake fee: $200, plus applicable taxes as required per local law
Delivery options: Proctored exam delivered onsite at a testing center or in an online proctored environment; click here for information on scheduling an exam.
References: No hard copy or online materials may be referenced during the exam.
Prerequisite: None
Exam Outline:
The Salesforce Platform 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.