Explanation:

Universal Containers wants to move permission sets (which define object- and field-level access) from a sandbox to production — a common requirement during configuration or development.
Using a change set is the best practice method supported by Salesforce for deploying metadata, including permission sets.

🔍 A. Use a change set ✅
Change sets are the recommended way to move metadata (including permission sets) between related Salesforce orgs (e.g., sandbox → production).
You can include:
Permission sets
Custom objects
Fields
Profiles
Page layouts, etc.
Change sets ensure a controlled, auditable, and safe deployment process.
Changes are validated before deployment, reducing risk of errors.
✅ Best practice when deploying from sandbox to a connected production org.

🔍 B. Re-create them manually
Manually creating permission sets in production is:
Error-prone
Time-consuming
Difficult to track and maintain
It is not scalable and goes against standard deployment best practices
🔴 Not recommended

🔍 C. Use Salesforce Workbench
Workbench is a powerful tool, but it is not ideal for deploying permission sets
While Workbench supports the Metadata API, using it for permission sets:
Requires manual XML handling
Is more complex and riskier than using change sets
More appropriate for complex or cross-org deployments, not typical sandbox-to-production flows
🟡 Possible, but not the best practice

📚 References:
Salesforce Help: Deploy Permission Sets Using Change Sets
Trailhead: Change Set Development Model

✅ Final Answer: A. Use a change set
Because it's the safest, simplest, and Salesforce-recommended method for deploying permission sets and other metadata from sandbox to production.