What are the capabilities of using change sets? Choose three answers.
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: A, C & D
Change sets allows the deploying of customizations from one salesforce org to another.
You have the ability move metadata either from sandbox to production or from one sandbox to another.
In addition to this change sets are available in both salesforce classic and lightning.
Option B is incorrect because change sets don't contain data or any records.
They contain only metadata.
Sure, I'd be happy to explain the capabilities of using change sets in Salesforce!
A. Change sets are considered the standard way of deploying customizations from one Salesforce org to another:
Change sets in Salesforce are a way to bundle up and move customizations from one Salesforce org to another. This includes things like custom objects, fields, Apex classes, Visualforce pages, and more. Change sets are considered the standard way of deploying these customizations because they are easy to use and understand, and they are built into the Salesforce platform. With change sets, you can be confident that your customizations will move from one org to another without issue.
B. Change sets allow moving data from sandbox to production and between one sandbox to the other:
While change sets are primarily focused on moving metadata (i.e., customizations) from one org to another, they can also be used to move data. This is particularly useful when you are testing changes in a sandbox environment and want to move that data to production or another sandbox. For example, if you have created test records in a sandbox to test a new custom object, you can include those records in a change set and move them to production.
C. Change sets allow moving metadata from sandbox to production and between one sandbox to the other:
As mentioned above, change sets are primarily focused on moving metadata from one org to another. This includes customizations like custom objects, fields, Apex classes, Visualforce pages, and more. When you create a change set, you select the metadata components that you want to move and then upload the change set to the target org. Once the change set is deployed, the metadata components are available in the target org.
D. Change sets are available in both classic and lightning experience:
Finally, it is worth noting that change sets are available in both classic and lightning experience. This means that no matter which user interface you are using, you can still use change sets to move customizations and data between orgs. In classic, change sets are accessed via the Setup menu, while in lightning experience they are accessed via the App Launcher.