Pearson Development-Lifecycle-and-Deployment-Architect New Attempt

A and D are the correct answers, as they are the locking behaviors that will occur during a deployment. A is correct, as the production org will be locked and administrators cannot modify metadata during this time, to prevent any conflicts or inconsistencies in the deployment. D is correct, as the production org will be locked and users will still be able to read/write data to the org, to minimize the impact on the business operations and user experience. B is incorrect, as the sandbox org will not be locked and administrators can still modify metadata, as the sandbox org is not the target of the deployment. C is incorrect, as the production org will not be locked and users can only read data during this time, as this would disrupt the business operations and user experience. You can learn more about the locking behaviors in the [Deploy Changes with Change Sets] unit on Trailhead.

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.

C and D are the correct answers, as they are the best strategies to address a critical production issue occurring in the middle of development. C is correct, as using a source control system to allow separate branches for current development and production bug fixes can help to isolate the changes and avoid conflicts or overwriting. D is correct, as refreshing a sandbox for replication of the issue and testing the use-case scenarios once the code is fixed can help to ensure the quality and functionality of the solution before deploying it to production. A is incorrect, as creating separate branches for current development and production bug fixes and deploying the fix with current development when ready can delay the resolution of the production issue and introduce new risks or errors. B is incorrect, as utilizing one branch for both development and production bug fixes to avoid out-of-sync branches and simplify deployment can create confusion and complexity in the code and make it harder to test and validate. You can learn more about these strategies in the Application Lifecycle and Deployment module on Trailhead.

The optimal way to store the service centers as technical reference data is to add them to a custom metadata type. Custom metadata types allow you to create, update, and deploy records that are defined by a custom object. Custom metadata types are similar to list custom settings, but they have some advantages, such as being deployable, queryable, and packageable. Hierarchical custom settings are not suitable for storing multiple records of the same type, and defining a new custom object with a picklist field is unnecessary and inefficient.