Salesforce Development-Lifecycle-and-Deployment-Architect Dumps Questions Answers

Deploying unsupported components manually before/after deployment is the best way to address the issue of Metadata API not supporting all the components yet. Metadata API is a powerful tool for deploying changes between orgs, but it does not cover all the metadata types that are available in Salesforce. Some examples of unsupported components are email templates, dashboards, reports, and custom settings. These components need to be deployed manually by using other tools or methods, such as change sets, data loader, or manual configuration.

The recommended mechanism for releasing the application that can be installed in the trading partners’ Salesforce environments is a managed package. A managed package is a collection of application components that can be distributed and installed in other orgs. Managed packages allow you to control the visibility and upgradability of the components, as well as provide namespace isolation and license management. Change sets are not suitable for releasing applications to other orgs, as they can only be used for orgs that are affiliated with the same production org. Unmanaged packages are not ideal for releasing applications that need to be updated frequently, as they do not allow you to push upgrades or control the components after installation. Zip file deployable by SFDX or ANT is not a user-friendly way of releasing applications, as it requires the users to have technical knowledge and tools to install the components.

 The change set performance may depend on the included components, especially if they are complex or have many dependencies. The change set may take more time than usual if it includes changes to permission sets and profiles, as these components require additional validation and processing. The change set may not take more time if it includes field type changes, new custom objects and fields, or other simple components.