The Short Answer
The Salesforce Certified Platform Development Lifecycle and Deployment Architect exam has 60 scored multiple-choice questions plus up to 5 unscored, a 105-minute time limit, a 65% passing score, a US$400 registration fee (US$200 to retake) and no prerequisite. Its questions align to the Spring '23 release (checked in October 2026 against the official exam guide).
It's one of the four certifications that grant System Architect. The weight is spread unusually evenly across eight sections, from Application Lifecycle Management at 8% to System Design at 15%, so you can't pass on one strong topic. Expect scenarios about a customer's environments, branches, packages, tests and releases, where the right answer is the strategy that fits their maturity and risk.
Exam Details at a Glance
| Detail | Platform Development Lifecycle and Deployment Architect |
|---|---|
| Questions | 60 scored multiple-choice, plus up to 5 unscored |
| Time limit | 105 minutes |
| Passing score | 65% |
| Registration fee | US$400 (JPY 60,000), plus applicable taxes |
| Retake fee | US$200 (JPY 30,000), plus applicable taxes |
| Prerequisite | None |
| Release alignment | Spring '23 |
| Delivery | Proctored, online or at a testing center |
| References allowed | None |
| Maintenance | The certification's maintenance badge on Trailhead, once a year |
Source: the exam guide for every row, checked in October 2026.
65% of 60 is 39 correct answers, so you can miss 21. 105 minutes for up to 65 questions is about 1.6 minutes each. That's enough if you read each scenario once for the constraint that matters (a regulated industry, several project streams, a hotfix in flight, changes made directly in production) and don't re-read it three times. For fees and retake rules across every Salesforce exam, see Salesforce certification cost and retake fees.
Who the Exam Is For
The exam guide describes a candidate with 2 to 3 years of Salesforce Platform experience, plus 1 to 2 years each on Salesforce DevOps, application lifecycle management and governance committees, and working knowledge of agile, waterfall and hybrid delivery. Typical roles are Technical Lead, Delivery Lead, Release Manager, Environment Manager, Ops Manager, Test Manager and Technical Architect.
The candidate is expected to design environment and test strategies (including data and security), describe the capabilities and constraints of the Metadata and Tooling APIs, explain source control, branching and continuous integration, plan testing across Salesforce releases, take part in governance, and design a backup and restore strategy.
Just as useful is what the guide says you aren't expected to do: write ANT or CLI migration scripts, set up the source control environment, or set up continuous integration tools. This is an architect exam. You need to know which tool, model or strategy fits a situation and why, not the exact command syntax.
Where It Sits on the Architect Path
There's no exam called "System Architect". The System Architect credential page says it's granted once you hold four certifications:
- Platform Developer
- Platform Development Lifecycle and Deployment Architect
- Platform Identity and Access Management Architect
- Platform Integration Architect
We couldn't find a dedicated Trailhead credential page for this certification in October 2026 (the URL pattern other architect credentials use returns a 404), so this guide relies on the exam guide and the System Architect page. If you're also working toward Application Architect, our Sharing and Visibility Architect guide and Platform Data Architect guide cover two of its exams.
The Eight Exam Sections and What They Test
All weights and objectives come from the official outline.
| Section | Weight | About this many questions (of 60) |
|---|---|---|
| Application Lifecycle Management | 8% | 5 |
| Planning | 13% | 8 |
| System Design | 15% | 9 |
| Building | 14% | 8 |
| Deploying | 14% | 8 |
| Testing | 13% | 8 |
| Releasing | 13% | 8 |
| Operating | 10% | 6 |
Application Lifecycle Management (8%) and Planning (13%)
ALM has a single objective: weigh the benefits and risks of different development methodologies against project risk and customer requirements, and recommend governance that fits the customer's maturity. Planning goes further: assess ALM maturity (people, technology and processes), identify environment risks and how to mitigate them, recommend a governance framework, and plan for the three seasonal Salesforce releases (Spring, Summer, Winter).
Watch for: answers that are "best practice" but wrong for the customer. A small team new to source control doesn't need the governance model of a 40-developer program. Match the recommendation to the maturity the scenario describes.
System Design (15%)
The biggest section: agile tooling, the org strategy, the sandbox strategy and the components of a deployment strategy. Know the sandbox types cold. Salesforce's sandbox types page lists:
| Sandbox | Refresh interval | Data storage | What's copied |
|---|---|---|---|
| Developer | 1 day | 200 MB | Metadata only |
| Developer Pro | 1 day | 1 GB | Metadata only |
| Partial Copy | 5 days | 5 GB | Metadata and sample data (template required) |
| Full | 29 days | Same as production | Metadata and all data |
Watch for: a Full sandbox suggested for every stage. Its 29-day refresh interval makes it a poor fit for a hotfix path that needs a fresh copy, and a good fit for staging and performance testing with production-sized data.
Building (14%)
Branching, versioning and merging strategies; test data and unit tests (positive, negative, permission-based and large data volume); the org-based versus package-based development model and scratch orgs versus sandboxes; and quality gates such as coding standards, pull requests, code review and static code analysis.
Watch for: the development model. In the package-based model, version control is the source of truth and packages are versioned, while the org-based model treats an org (usually production) as the target that changes accumulate in.
Deploying (14%)
The capabilities and limits of the Metadata and Tooling APIs, pre- and post-deployment steps (including anything the APIs can't deploy), and how to move technical reference data, meaning configuration stored as records.
Watch for: two things. Salesforce keeps a list of unsupported metadata types that can't be retrieved or deployed with Metadata API, so changes to them are made by hand in each org. That's what the manual pre- and post-deployment steps in a runbook are for. And when configuration lives in records, custom metadata types are "deployable, packageable, and upgradeable", which custom object records aren't.
Testing (13%)
The right testing methodology, test execution and coverage requirements, and a unified test data strategy that uses representative data securely across the lifecycle. Know the deployment test levels in the sf project deploy start reference: RunLocalTests is the default for production deployments that include Apex, RunSpecifiedTests requires 75% coverage for each class and trigger in the deployment, and NoTestRun only applies to development environments.
Releasing (13%)
Use cases for managed, unmanaged and unlocked packages, mapping the sandbox strategy to a release plan (project streams, training, staging, hotfixes), and recommending a release management strategy.
Watch for: the package type. Salesforce says unlocked packages suit internal business apps and are the right type for most use cases unless you distribute on AppExchange, in which case you use second-generation managed packages.
Operating (10%)
What it means to make a requested change directly in production, how to bring production changes back into the lifecycle, and how to manage common release artifacts across several orgs.
Watch for: "just change it in production". The right answer nearly always records the change in source control afterwards (or retrieves it), so the next deployment doesn't overwrite it.
What Has Changed Since Spring '23
The outline is aligned to Spring '23, and DevOps tooling has moved a lot since then. Learn the current names and behavior so a modern scenario doesn't catch you out, and so what you learn still holds on the job.
- Lifecycle Center (formerly DevOps Center). Salesforce Help's Lifecycle Center overview says that "beginning October 2026, DevOps Center is changing its name to Lifecycle Center". It captures changes in source control as a single source of truth, manages branches, promotes work through a pipeline, and is positioned as an alternative to change sets. Existing DevOps Center (Managed Package) users can keep using it.
- The
sfCLI (v2). Salesforce recommends that anyone onsfdx(v7) move tosf(v2), and says existing commands keep working after the move. Current documentation uses commands such assf project deploy start, which also offers aRunRelevantTeststest level (Beta). - Unlocked packages and second-generation managed packages (2GP). In the 1GP versus 2GP comparison, 2GP makes version control the source of truth, the Dev Hub owns the package, there are no packaging or patch orgs, versioning is flexible enough for branches and parallel development, and every packaging operation can be automated with Salesforce CLI.
- Data Mask & Seed. The Data Mask managed package retirement article says support for the legacy managed package ended on July 9, 2026, its display becomes read-only on December 31, 2026, and Data Mask & Seed, a Core app that needs no installation, has replaced it since the Summer '26 release. For "representative data in a secure manner", that's now the masking answer.
- Code Analyzer v5. The Code Analyzer release notes say v5 became generally available in April 2025 and v4 has been retired and unsupported since August 2025. The Code Analyzer overview describes engines such as PMD, ESLint and RetireJS, more than 500 built-in rules, and a GitHub Action for CI pipelines.
- Apex user mode by default from API 67.0. The Summer '26 release note says SOQL, SOSL, DML and Database methods run in user mode by default at API version 67.0 and later, and that
WITH SECURITY_ENFORCEDis removed as of API 67.0 (useWITH USER_MODE). For a lifecycle architect, that's a release-readiness item: code moved to API 67.0 can behave differently for users who lack access, so it needs permission-based tests before it ships.
A Six-to-Eight-Week Study Plan
- Read the exam guide and score yourself. Rate each of the 25 objectives from 1 to 3. With the weights this flat, a weak spot anywhere costs points. Our guide to using the exam outline to plan your study shows how.
- Take a baseline. Try the 18 free Development Lifecycle and Deployment Architect practice questions to see the scenario style and find your weakest section.
- Work the official trailmix. The exam guide recommends the Architect Journey: Development Lifecycle and Deployment trailmix, which groups its modules by exam section. (The guide's link text calls it "Development Lifecycle and Architect"; it's the same trailmix.)
- Draw an environment map. For one fictional customer with two project streams, a training team and a hotfix path, sketch every sandbox, its type, its refresh cadence and the branch that deploys to it. This one diagram covers System Design, Releasing and much of Planning.
- Get hands-on. In a free Developer Edition org with Dev Hub enabled, create a scratch org, build an unlocked package version, install it, run Code Analyzer over the project, and deploy with
sf project deploy startat different test levels. - Practice under time. Book the exam when you're comfortably above 65% and can explain why each wrong answer is too heavy, too risky or skips governance. Our guide to answering Salesforce scenario questions helps with the "choose 2" format.
Development Lifecycle and Deployment Architect Practice Exam on Certifyforce
Certifyforce has a practice bank for this exam, written to the official outline and checked against Salesforce Help, the Salesforce DX Developer Guide and Trailhead. It isn't affiliated with Salesforce, and it contains no recalled exam questions or brain dumps.
- The Platform Development Lifecycle and Deployment Architect practice exam: 300 reviewed questions across all eight sections, with timed 60-question exams weighted like the real one, section practice, and an explanation and source for every answer. The full pack is launching soon.
- 18 free practice questions picked across the eight sections in proportion to their weight, each with the answer, why the others are wrong and the documentation it was checked against. No account needed.
Frequently Asked Questions
How many questions are on the Development Lifecycle and Deployment Architect exam?
60 scored multiple-choice questions plus up to 5 unscored ones, in 105 minutes, with a 65% passing score, per the exam guide.
How much does the exam cost?
US$400 (JPY 60,000) plus applicable taxes, and a retake costs US$200 (JPY 30,000), per the exam guide.
Does it have a prerequisite?
No. The guide lists no prerequisite, but it describes a candidate with 2 to 3 years of Salesforce Platform experience and 1 to 2 years each in DevOps, ALM and governance.
Is it required for System Architect?
Yes. System Architect is granted when you hold Platform Developer, Platform Development Lifecycle and Deployment Architect, Platform Identity and Access Management Architect and Platform Integration Architect.
Does the exam cover Lifecycle Center and the sf CLI?
The outline aligns to Spring '23, before the Lifecycle Center name. Its objectives on deployment tools, source control and release management are still tested, so learn the current tools under their current names, and remember that older material says DevOps Center and sfdx.
How do I keep the certification?
Complete the certification's maintenance badge on Trailhead once a year. If you miss the due date, the certification expires.