When configuring a change set, which two practices should an administrator adhere to in order to ensure a successful deployment to production? Choose…

When deploying with change sets, two key practices ensure success. First, once a change set is uploaded, it is locked. If a dependent component is forgotten, the administrator must clone the original change set, add the missing component, and upload the new version. Second, permissions are not automatically included with their related components. An administrator must manually add relevant profiles or permission sets to the change set to ensure users have access to the new functionality in production.

C. Run deployment validations on the change set in the sandbox prior to uploading to production: Validation occurs in the target environment (production) after the change set has been uploaded, not in the source environment (sandbox).
D. When deploying a new record type, ensure the new record type is the only component in the change set: There is no such restriction; record types can and often should be deployed with their dependent components like page layouts and picklist values.

1. Salesforce Help. (2024). Change Sets Best Practices. Retrieved from Salesforce Help & Training. Section: "Plan Your Deployment" and "Add Permissions and Access Settings to Change Sets".

2. Salesforce Help. (2024). Upload a Change Set. Retrieved from Salesforce Help & Training. Note: "After you upload a change set, you can’t make changes to it or recall it. To add dependent components that you forgot, clone the change set, add the components, and upload it again."

3. Salesforce Developer Documentation. (2023). Deploying Changes with Change Sets. Trailhead Module. Unit: "Deploy a Change Set".