Checklist progress
0/316Learned
Platform App Builder
Study Checklist
Checklist progress
0/316Learned
Given a set of business requirements, recommend a solution for managing the application lifecycle, including sandbox types
0/11
Given a use case, demonstrate knowledge, viability, and troubleshooting when using change sets.
0/16
Describe the use cases and considerations when using unmanaged and managed packages.
0/11
When to use managed versus unmanaged packages
Learn this conceptNamespace prefixes on packaged component API names
Learn this conceptSubscriber customization of packaged components
Learn this conceptManaged package upgrades and versioning
Learn this conceptUninstall behavior for installed packages
Learn this conceptUnmanaged packages versus change sets for metadata migration
Learn this conceptAppExchange package install in a sandbox
Learn this conceptPackage installation user access options
Learn this conceptPackaged components and org edition limits
Learn this conceptUnlocked packages versus managed packages for internal apps
Learn this conceptAppExchange security review for public managed packages
Learn this conceptGiven a scenario, determine the appropriate deployment plan.
0/6
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Platform App Builder studiers. 592 members and growing.
A package is a container of related Salesforce metadata, features, customizations, and schema, that you install into orgs. For internal business apps you do not plan to list on AppExchange, unlocked packages are the usual choice: version control is the source of truth, and you install immutable versions into orgs while still being able to change that metadata in production. Managed packages exist for a different job, commercial AppExchange distribution, where the package developer can upgrade subscriber orgs and Salesforce applies manageability rules to each component.