Lesson 17 of 17 · All lessons

Section 6 · App Deployment · 13% of exam

6.3 Choose Packages and Build a Deployment Plan

4 min read Updated Nov 19, 2026

Exam objective

Describe unmanaged and managed package use cases and considerations, and determine an appropriate deployment plan for a scenario.

Packages group metadata for distribution and reuse. Unmanaged packages are commonly used to distribute editable components or sample configuration, but the recipient owns the installed metadata and there is no upgrade path that preserves a managed package identity. They can be useful for one-off delivery or open examples, but updates and collision management become the recipient’s responsibility. Managed packages are designed for controlled distribution by a publisher, support versioning and upgrades, and can protect intellectual property depending on the packaging model. They introduce publisher, namespace, licensing, security-review, and dependency considerations. Choose a package when the requirement is to distribute a reusable application or component across orgs or customers. For a simple change moving between a company’s own orgs, a package may be unnecessary; change sets or source-driven deployments may fit better. Package planning starts with metadata boundaries: what belongs together, what dependencies are required, what should be configurable, and how upgrades affect subscribers. A package cannot be treated as a bag of unrelated metadata if components have dependencies or shared versioning needs. A deployment plan starts with scope and target. Inventory objects, fields, flows, actions, Lightning pages, permission changes, package dependencies, and any records that must be migrated. Select a deployment path supported for those components. Build and test in a development environment, review changes, validate in a target-like environment, obtain business acceptance, and schedule the production release. Communicate user-visible changes and provide training or support where needed.

After deployment, verify that components exist, are active, are assigned to the intended audience, and function with production data and permissions. Monitor errors and adoption. If the deployment fails, know whether to fix forward, deactivate a feature, or restore prior metadata. Record version identifiers and deployment results. Salesforce metadata deployment is not always an atomic rollback of every data or configuration effect, so plan recovery before release. Applied scenario: An ISV wants to distribute a reusable case-triage application to many customer orgs and publish controlled updates. A managed package is likely a better fit than an unmanaged package because the publisher needs versioned upgrades and a stable product identity. Define package boundaries, namespace, licensing, dependencies, supported editions, and security review requirements. Build and test an upgrade path from an earlier version, not only a fresh installation. For an internal one-time deployment of a page and flow between two orgs, compare change sets or source deployment instead of introducing a package lifecycle the team does not need.

Design and risk review: Unmanaged metadata can be edited by recipients, making future updates harder to reconcile. Managed packaging brings publisher obligations, namespace effects, dependency management, and subscriber testing. A deployment plan that lists only metadata but ignores data migration, permission assignments, activation, or user communication is incomplete. Do not assume every component supports every packaging or deployment method. Check current packaging and metadata documentation for compatibility and test the exact route in a nonproduction target. Salesforce Certified Platform App Builder | SU ·26 guide alignment 28

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

  • Describe unmanaged and managed package use cases and considerations, and determine an appropriate deployment plan for a scenario
  • 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://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/ https://trailhead.salesforce.com/content/learn/modules/app_deployment Salesforce Certified Platform App Builder
  • SU ·26 guide alignment 29

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