What two considerations should an app builder keep in mind during this process?

An app builder is preparing to deploy a new app from the sandbox to production using change sets.

What two considerations should an app builder keep in mind during this process? Choose 2 answers
A . Salesforce Connect automatically establishes a link between environments.
B . Change sets do not include all components and may have to perform some changes manually.
C . Users should be logged out of production when receiving inbound change sets.
D . Transactions will revert if the deployment errors.

View Answer

Answer: B, C

Explanation:

The two considerations that an app builder should keep in mind during the deployment process using change sets are: Change sets do not include all components and may have to perform some changes manually. Change sets are a way to deploy metadata changes from one Salesforce org to another, but they do not support all types of components, such as reports, dashboards, email templates, etc. The app builder may have to use other methods, such as unmanaged packages or manual configuration, to deploy these components. Users should be logged out of production when receiving inbound change sets. This is a best practice to avoid any errors or conflicts that may occur when deploying changes to production. Users may be working on records or components that are being updated by the change set, which may cause data loss or inconsistency. Salesforce Connect does not automatically establish a link between environments. Salesforce Connect is a feature that allows users to access data from external sources without storing it in Salesforce. It does not have anything to do with deploying changes between Salesforce orgs. Transactions will not revert if the deployment errors. Transactions are units of work that are either completed entirely or not at all. If a deployment error occurs during a transaction, the transaction will be rolled back and no changes will be made to the target org. However, this does not mean that the source org will revert to its previous state before the deployment.