How should permission sets be deployed to Production when they have been created in a sandbox?

• A. Create an Unmanaged Package
• B. Publish a Managed Package
• C. Use a Change Set
• D. Manually re-create the Permission Sets

Answer: (C)

Permission sets are metadata that can be moved between Salesforce environments, and the cleanest, governance-friendly way to deploy them from a sandbox to Production is through a Change Set. With an outbound Change Set, you bundle the permission sets (and any related dependencies you need to include), upload the set to Production, and then deploy (and validate) it in Production. This process preserves configuration, gives you an audit trail, and supports dependency checks to help prevent missing permissions or access issues after deployment.

Unmanaged or managed packages are alternatives but aren’t as well suited for this internal, environment-to-environment deployment. Unmanaged packages aren’t upgradeable and are generally used for distribution to customers; managed packages add licensing and distribution complexities that aren’t needed for sandbox-to-production moves. Manually re-creating permission sets in Production is error-prone and defeats version control and change-management practices. Using a Change Set keeps deployments consistent, traceable, and aligned with standard Salesforce release processes.