Which deployment involves selecting source and destination orgs?

The correct answer revolves around the concept of metadata deployments, which are focused on managing and transferring configurations and changes between different Salesforce environments. In metadata deployments, users meticulously select both a source org, which contains the changes or configurations they want to deploy, and a destination org, where those changes will be applied. This process ensures that the specific components, such as Apex classes, Visualforce pages, or custom objects, are accurately transferred from the source to the destination.

In contrast, standalone deployments may not specifically involve selecting both source and destination orgs, as they can refer to a more general process that doesn’t focus on the controlled transfer of metadata. Automated deployments can streamline this process but still fundamentally rely on the configuration of source and destination, which is why metadata deployment is more representative of the described process. Manual deployments also involve selecting orgs, but they imply a more hands-on approach, not exclusively focusing on metadata management. Therefore, metadata deployment distinctly encapsulates the act of directly selecting and managing the transfer of changes between two specific orgs.