Lesson 16 of 17 · All lessons

Section 6 · App Deployment · 13% of exam

6.2 Use Change Sets Safely and Troubleshoot Deployments

4 min read Updated Nov 19, 2026

Exam objective

Given a use case, demonstrate knowledge, viability, and troubleshooting when using change sets. Change sets move supported metadata between connected Salesforce orgs, commonly from a sandbox to its production org. An outbound change set contains selected components; it is uploaded to the target org, where an inbound change set can be validated and deployed. This workflow is approachable for administrators and useful for controlled org-to-org releases, but it is not a complete source-control or application lifecycle system. Change sets do not move ordinary record data, and not every metadata type or dependency is supported.

Build the change set from the release scope, not by selecting components at random. Include related fields, layouts, record types, flows, permission changes, and other dependencies that the target needs. The dependency tool can help identify some dependencies, but it does not guarantee completeness. Compare source and target configuration, identify components that already exist, and document data setup steps separately. Use meaningful change-set names and descriptions so the deployment has a clear audit trail.

Validate in the target before the release window. Validation can reveal missing dependencies, tests that fail, or configuration conflicts without immediately deploying. Address failures at the source, upload the corrected set, and validate again. Test level requirements and code coverage apply where Apex is involved. After deployment, confirm activation state, permissions, page assignments, and end-to-end behavior. Components such as flows may require Salesforce Certified Platform App Builder | SU ·26 guide alignment 26 explicit activation or a deliberate version choice after deployment.

Change sets are less suitable for large teams with parallel changes, reusable products, complex branching, or a need for robust version comparison and automated release pipelines. In those situations, source-driven tools or packages may provide better control. Regardless of mechanism, define what was deployed, who approved it, how success is verified, and what recovery options exist.

Applied scenario: A team adds a field, updates a Lightning page, and changes a flow in a sandbox. Identify the field, page, flow, and any required permission-set or layout metadata. Verify that the flow references only components available in production and that data prerequisites are handled separately. Upload the outbound set, validate it in production, review any errors and test results, and deploy during the approved window. Then confirm the flow’s active version and test as a standard user. If the target org has a conflicting component, resolve the difference intentionally rather than assuming the change set will merge the two versions.

Design and risk review: A successful upload is not a successful deployment, and a validated change set is not a substitute for user acceptance testing. Missing dependencies and unsupported metadata can block deployment. Change sets do not carry data records, so a new required field or lookup may need a separate data migration plan. Avoid editing production metadata after validation because the target can drift. Keep a release record and a tested recovery approach for changes that alter user workflows.

Exam lens: First translate the stated requirement into a measurable outcome. Identify the actor, record or object in scope, timing, access boundary, and exception path. Eliminate choices that solve only the visible interface while missing the underlying data, security, or lifecycle requirement. Then compare the remaining supported features by fit, operational complexity, maintainability, and any dependency named in the scenario. A strong answer satisfies the stated need with the least fragile configuration and preserves the platform’s security and governance model. These are study heuristics, not additional official exam rules.

Extra concept: Treat configuration as a system rather than a list of settings. A field may participate in a formula, validation rule, flow, report, permission set, Lightning page, and deployment package at once. Before changing it, identify those dependencies, decide which are intentional, and test the full user journey. This dependency view explains why a locally correct change can still fail after deployment or for a different user. Use Setup dependency tools where available, source comparison, and focused regression checks; no single dependency view is guaranteed to reveal every runtime relationship.

Verification exercise: Turn the lesson scenario into a small test plan before calling the design complete. Record the starting data, the user permissions, the expected outcome, and the evidence that would confirm it. Test one ordinary path, one boundary condition, and one invalid or unauthorized path. Compare the result with the business requirement, then repeat after deployment in the target environment. This catches differences caused by data, activation, page assignment, sharing, or dependencies. Save the test cases with the release notes so another administrator can reproduce the result.

Key takeaways

  • Given a use case, demonstrate knowledge, viability, and troubleshooting when using change sets
  • Choose the platform feature that fits the requirement, data, access, and operating context.
  • Test realistic users, exceptions, dependencies, and lifecycle effects before release.
  • Official references: https://help.salesforce.com/s/articleView?id=005298964&language;=en_US&type;=1 https://help.salesforce.com/s/articleView?id=sf.changesets.htm&type;=5 https://trailhead.salesforce.com/content/learn/modules/app_deployment Salesforce Certified Platform App Builder
  • SU ·26 guide alignment 27

Check your knowledge

Answer exam-style App Deployment questions with answers and explanations.

Practice App Deployment
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Platform App Builder simulator: same number of questions, same time limit.

Get Complete Access