Checklist progress
0/215Learned
Platform Administrator II
Study Checklist
Checklist progress
0/215Learned
Describe the options available to move metadata between environments
0/5
Describe the capabilities and best practices for using change sets to move metadata between environments
0/9
Deployment connections for change sets
Learn this conceptOutbound versus inbound change sets
Learn this conceptPermissions to upload and deploy change sets
Learn this conceptComponents available in change sets
Learn this conceptChange set coverage for data and destructive changes
Learn this conceptDependent components in change sets
Learn this conceptProfile settings and permission sets in change sets
Learn this conceptInbound change set validation versus deployment
Learn this conceptApex tests when deploying change sets
Learn this conceptPrepare for the Exam
Study Community
Ask questions and get the latest info from other Platform Administrator II studiers. 593 members and growing.
A change set sends setup customizations as components, but only listed component types can be added, and that list varies by the org's experience, edition, and which features are enabled. If you create or change something that is not available as a change set component, you cannot send it between orgs in a change set and must repeat the same setup steps in the destination. Even when a type can be added, folder location, profiles, and missing dependencies decide whether it deploys and who can use it afterward.