Development-Lifecycle-and-Deployment-Architect Exam Dumps - Salesforce Certified Development Lifecycle and Deployment Architect (WI25)

User fields are preserved during metadata deployments and Salesforce attempts to locate a matching user in the target org during deployment. If the username in the source org doesn’t exist in the target org, the deployment will stop until the usernames are resolved or removed.

Refreshing all non-preview sandboxes during the release preview window is the best way to handle the situation of having a mix of preview and non-preview instances for the release of a major project. A release preview window is a period of time before a Salesforce seasonal release, where the customers can test their applications and integrations in a sandbox that has the same version as the upcoming release. By refreshing all non-preview sandboxes during this window, the architect can ensure that all the sandboxes are aligned with the same version and avoid any conflicts or errors during the deployment. Refreshing the sandboxes when the release management team has time, mixing instance types, or contacting support to rollback the release are not good practices, as they can cause inconsistency, confusion, or disruption in the release process.

The architect should recommend the use of an automated testing tool daily in all Developer Orgs, and when branches are merged. This strategy allows the team to catch and fix any errors or bugs early in the development cycle, and to ensure that the code is stable and consistent before deployment. Running automated tests only when branches are merged is not sufficient, as it may delay the detection and resolution of issues. Running automated tests only in Full or Partial Copy sandboxes is not advisable, as it may not cover all the scenarios and environments.

QUESTIONNO: 172

Universal Containers (UC) is a large enterprise with a complex system landscape. UC is

currently rolling out new infrastructure and strategies around Salesforce DevOps. Some of the

key feature’s UC is looking to support is rollback of metadata after a deployment, and the

backup and restore of data to help recover from deployment issues, system bugs, or outages in

their downstream systems.

Regulations in the industry mean that UC must be able to provide strategies to recover and

rollback from issues. The regulator has discovered UC is not currently providing these, and must

do so as soon as possible to remain compliant.

What should an architect advise?

A. Salesforce backs up all data and will restore it for customers on request.

B. Evaluate third-party and AppExchange products.

C. Advise stakeholders that rollback is not possible for Salesforce.

D. Custom build a feature rollback and data restore tool for Salesforce

Answer: B

The architect should advise UC to evaluate third-party and AppExchange products that can provide the features they are looking for, such as rollback of metadata and backup and restore of data. Salesforce does not offer these features natively, and building a custom solution can be costly and time-consuming. There are several products available in the market that can help UC meet their regulatory requirements and recover from issues. For example, Gearset is a DevOps tool that can perform metadata rollback and data backup and restore, among other features