SALESFORCE CERTIFICATION
Certified Platform Development Lifecycle and Deployment Architect Practice Exam
Exam Number: 3710 | Last updated 14-Apr-26 | 1246+ questions across 6 vendor-aligned objectives
The Development Lifecycle and Deployment Architect certification is for professionals who design release management strategies, version control processes, and CI/CD pipelines for Salesforce development teams. It addresses the unique challenges of deploying metadata-driven changes across sandboxes and production environments.
A full 25% of the exam targets Release Management, covering release planning, governance, rollback strategies, and environment management. At 25%, Deployment Strategies represents the single largest exam section, covering change sets, Metadata API, unlocked packages, and Salesforce DX. The exam allocates 20% to Source Control and Branching, covering Git workflows, branching strategies, and metadata merge patterns. Together, these domains form the backbone of the certification and warrant the bulk of your preparation time.
Beyond the core areas, the exam also evaluates complementary skills. At 15%, Testing and Ci/cd represents the single largest exam section, which spans automated testing, continuous integration, and quality gates. The exam allocates 15% to Environment Strategy, which spans sandbox types, scratch orgs, and environment routing. Although individually lighter, these topics frequently appear in scenario-based questions that blend multiple skill areas.
Every answer links to the source. Each explanation below includes a hyperlink to the exact Salesforce documentation page the question was derived from. PowerKram is the only practice platform with source-verified explanations. Learn about our methodology →
277
practice exam users
98.2%
satisfied users
89.9%
passed the exam
4.3/5
quality rating
Test your Certified Devops Architect knowledge
10 of 1246+ questions
Question #1 - Ship and rollback change sets, Metadata API, and unlocked packages to ship changes safely through structured release pipelines with rollback capabilities
A Salesforce Center of Excellence manages a large org with 15 development teams working on independent features simultaneously. Teams frequently experience merge conflicts when deploying to UAT.
Which development model should the architect recommend?
A) Package Development Model using unlocked packages with dependency management
B) Source-driven development with a monolithic repository
C) A single shared developer sandbox with strict schedules
D) Org Development Model with change sets
Show solution
Correct answers: A – Explanation:
Unlocked packages modularize the codebase so each team develops and deploys independently with explicit dependency management. Change sets lack versioning. Shared sandboxes create bottlenecks. A monolithic repository concentrates conflicts. Source: Trailhead: SFDX Dev Model
Question #2 - Ship and rollback change sets, Metadata API, and unlocked packages to ship changes safely through structured release pipelines with rollback capabilities
A release manager needs every production deployment to pass automated tests with 85% coverage, a security scan, and change advisory board approval.
What CI/CD pipeline configuration should the architect implement?
A) A scheduled weekly deployment window with manual testing
B) Manual change sets with a verification checklist
C) Salesforce CLI deployment with RunAllTests flag and manual security review
D) A CI/CD pipeline with automated test execution, static code analysis gates, and an approval workflow step
Show solution
Correct answers: D – Explanation:
A CI/CD pipeline automates quality gates and halts on failure. An approval step integrates the change advisory board. Change sets with spreadsheets are error-prone. Post-deployment testing misses defects. Scheduled windows lack automation. Source: Trailhead: SF DevOps
Question #3 - Promote and govern sandbox types, scratch orgs, and environment routing to ship changes safely through structured release pipelines with rollback capabilities
An architect is designing an environment strategy for an enterprise with development, QA, staging, and production environments.
What environment strategy should the architect recommend?
A) Full-copy sandboxes for all environments
B) Additional full-copy sandbox licenses for each environment
C) Developer sandboxes for everything with Apex test data scripts
D) Developer sandboxes for dev, partial-copy for QA with anonymized data, full-copy for staging/UAT
Show solution
Correct answers: D – Explanation:
This tiered strategy matches sandbox types to each environment’s needs. Developer sandboxes for coding, partial-copy for representative QA data, full-copy for final UAT. Full-copy for all is wasteful. Developer sandboxes alone lack realistic data. Additional licenses increase costs. Source: Trailhead: SF DevOps
Question #4 - Promote and govern sandbox types, scratch orgs, and environment routing to ship changes safely through structured release pipelines with rollback capabilities
A team using Salesforce DX finds that deployment to a scratch org succeeds, but the same deployment fails in UAT sandbox with missing dependent metadata errors.
What is the most likely cause?
A) The project’s sfdx-project.json does not declare all dependencies, and the scratch org definition compensates
B) Sandboxes have stricter governor limits
C) The UAT sandbox needs to be refreshed
D) Scratch orgs include all features by default
Show solution
Correct answers: A – Explanation:
Scratch org definitions can enable features that automatically create supporting metadata. If the project does not explicitly declare all dependencies, deployments may succeed in scratch orgs but fail elsewhere. Scratch orgs do not include all features by default. Governor limits are the same. Refresh is unrelated to dependency errors. Source: Salesforce Docs: Salesforce DX Guide
Question #5 - Promote and govern Git workflows, branching strategies, and metadata merge patterns to ship changes safely through structured release pipelines with rollback capabilities
Two developers modify the same Apex class in different branches. A Git merge conflict is detected when merging to main.
What is the recommended process for resolving this metadata conflict?
A) Accept the most recent change and overwrite the other
B) Have both developers rewrite their changes separately
C) Manually resolve the conflict, then validate by deploying to a scratch org and running tests
D) Create a new class combining both changes
Show solution
Correct answers: C – Explanation:
Git merge conflicts must be manually resolved by reviewing both changes. The merged code should then be validated in a scratch org. Overwriting discards valid work. Creating a new class fragments the codebase. Rewriting wastes effort. Source: Trailhead: Git & GitHub Basics
Question #6 - Ship and rollback change sets, Metadata API, and unlocked packages to ship changes safely through structured release pipelines with rollback capabilities
An architect needs to deploy destructive changes — removing deprecated custom fields and Apex classes — from the repository to production.
How should the architect handle destructive metadata changes?
A) Deploy empty versions of each component
B) Include a destructiveChanges.xml manifest in the deployment package
C) Run a post-deployment Apex script to delete the metadata
D) Manually delete components in production after deployment
Show solution
Correct answers: B – Explanation:
Salesforce Metadata API supports destructiveChanges.xml manifests for including removals in deployment packages. Manual deletion is not repeatable. Empty components do not remove them. Apex cannot delete metadata at runtime. Source: Salesforce Docs: Metadata API Guide
Question #7 - Promote and govern sandbox types, scratch orgs, and environment routing to ship changes safely through structured release pipelines with rollback capabilities
A company is transitioning from change sets to Salesforce DX. The team has no source control and all customizations exist only in production.
What is the first step?
A) Retrieve all metadata from production using Salesforce CLI and commit it to Git as the baseline
B) Install a DevOps AppExchange tool to handle the transition
C) Create scratch orgs and build all customizations from scratch
D) Deploy production to a developer sandbox as the source of truth
Show solution
Correct answers: A – Explanation:
The foundational step is retrieving complete metadata from production and committing it to Git as the source of truth. Starting from scratch discards existing work. Sandboxes are not source control. AppExchange tools augment but cannot replace initial retrieval. Source: Salesforce Docs: Salesforce DX Guide
Question #8 - Validate and troubleshoot automated testing, continuous integration, and quality gates to catch issues before they reach production and maintain code quality across releases
A CI/CD pipeline runs Apex tests on every pull request. The test suite takes 45 minutes, slowing development.
How should the architect optimize test execution?
A) Run tests in parallel across multiple scratch orgs
B) Reduce the number of test methods
C) Run only tests related to changed classes on PRs, and run the full suite on main branch merge
D) Skip tests on pull requests entirely
Show solution
Correct answers: C – Explanation:
Targeted testing on PRs provides fast feedback, while the full suite on main branch merges ensures comprehensive coverage. Skipping PR tests risks merging broken code. Reducing tests lowers coverage. Parallel orgs add complexity without addressing root inefficiency. Source: Salesforce Docs: Salesforce DX Guide
Question #9 - Ship and rollback change sets, Metadata API, and unlocked packages to ship changes safely through structured release pipelines with rollback capabilities
An architect is designing a rollback strategy after a recent deployment introduced a regression bug not caught by automated tests.
What rollback approach should the architect implement?
A) Redeploy the previous version from Git with a destructiveChanges.xml for new components
B) Restore the production org from a Salesforce-provided backup
C) Create a hotfix deployment with manual fixes
D) Use the Salesforce ‘Undo Deployment’ feature in Setup
Show solution
Correct answers: A – Explanation:
With source control, the previous version is always available. Rolling back involves deploying the last good version plus destructiveChanges.xml to remove new components. Salesforce has no native Undo Deployment. Salesforce does not provide org restore. Hotfixes are not a rollback strategy. Source: Salesforce Docs: Metadata API Guide
Question #10 - Promote and govern sandbox types, scratch orgs, and environment routing to ship changes safely through structured release pipelines with rollback capabilities
A company needs to promote changes across dev, QA, staging, and production. Each environment has different API endpoint URLs and credentials.
How should the architect manage environment-specific configurations?
A) Maintain separate Git branches for each environment
B) Hardcode values and manually update after each deployment
C) Use custom metadata types or named credentials excluded from the deployment package and configured per environment
D) Deploy everything and use a post-deployment script to overwrite values
Show solution
Correct answers: C – Explanation:
Custom metadata types and named credentials store environment-specific configurations independently. By excluding them from the deployment package, the same code promotes across environments. Hardcoding requires manual intervention. Separate branches create merge issues. Post-deployment scripts add fragile dependencies. Source: Trailhead: Custom Metadata Types
Get 1246+ more questions with source-linked explanations
Every answer traces to the exact Salesforce documentation page — so you learn from the source, not just memorize answers.
Exam mode & learn mode · Score by objective · Updated 14-Apr-26
Learn more...
What the Certified Devops Architect exam measures
- Package and release release planning, governance, and rollback strategies to ship changes safely through structured release pipelines with rollback capabilities
- Promote and govern Git workflows, branching strategies, and metadata merge patterns to ship changes safely through structured release pipelines with rollback capabilities
- Ship and rollback change sets, Metadata API, and unlocked packages to ship changes safely through structured release pipelines with rollback capabilities
- Validate and troubleshoot automated testing, continuous integration, and quality gates to catch issues before they reach production and maintain code quality across releases
- Promote and govern sandbox types, scratch orgs, and environment routing to ship changes safely through structured release pipelines with rollback capabilities
How to prepare for this exam
- Confirm readiness with the official exam guide
- Complete the Development Lifecycle and Deployment trail on Trailhead — focus on Salesforce DX and packaging modules
- Set up a Salesforce DX project with source control, create a scratch org, and practice deploying with both CLI commands and unlocked packages
- Implement a CI/CD pipeline for a Salesforce project at work — even a basic GitHub Actions workflow counts as valuable hands-on experience
- Focus first on Release Management and Deployment Strategies, which together account for 50% of the exam
- Use PowerKram’s learn mode to study deployment scenarios with detailed architectural explanations
- Simulate exam conditions with PowerKram’s exam mode to sharpen your decision-making under time constraints
Career paths and salary outlook
DevOps and release management roles are increasingly vital as Salesforce orgs grow in complexity:
- Salesforce DevOps Architect — $145,000–$195,000 per year, designing CI/CD pipelines and deployment strategies (Glassdoor salary data)
- Salesforce Release Manager — $120,000–$160,000 per year, coordinating deployments and managing environment strategy (Indeed salary data)
- Salesforce Technical Architect — $165,000–$220,000 per year, owning platform architecture including development lifecycle (Glassdoor salary data)
Official resources
Follow the Development Lifecycle and Deployment Architect Learning Path on Trailhead. The official exam guide provides the full objective list and study resources.