Pass the Salesforce Developer Development-Lifecycle-and-Deployment-Architect Questions and answers with ValidTests

Two software development methodologies that an architect should suggest to solve the issue of visibility are Scrum and Kanban. Scrum is based on the value of openness, which means that the team members and stakeholders share information and feedback regularly and transparently. Kanban is based on the principle of making everything visible, which means that the team uses a visual board to track the progress and status of the work items. Waterfall is not a good methodology for visibility, as it does not allow for frequent communication and feedback. DevOps is not a methodology, but a culture and practice that aims to improve collaboration and delivery across the software development lifecycle.

Allowing no code/configuration changes directly in the production org and using Metadata API to automate deployment to the production org are two options that will streamline the process. These options help to enforce a consistent and controlled deployment process that avoids manual errors and conflicts in the production org.

 Two options that should be considered when making production changes in a highly regulated and audited environment are: all changes including hotfixes should be reviewed against security principles, and any production change should have explicit stakeholder approval. These options can help ensure that the changes are compliant with the regulations and have the necessary authorization and documentation. No manual steps should be carried out is not a valid option, as some changes may require manual steps, such as data migration or post-deployment verification. After deployment, the development team should test and verify functionality in production is also not a valid option, as testing and verification should be done in a lower environment before deploying to production, and the responsibility of testing and verifying functionality in production should be assigned to a different team than the development team. See Application Lifecycle and Deployment for more details.

The development model that is optimized for this need is to use unlocked packages to deploy the global code and allow each country to create its customized unlocked package extensions. This model can help maintain the global standardization and consistency of the code, while also providing the flexibility and autonomy for each region to customize some aspects of the code for their specific needs. Unlocked packages are a type of second-generation packaging that can be created and installed using the Salesforce CLI or APIs, and can be upgraded or uninstalled as needed. Unlocked package extensions are a type of unlocked packages that can depend on and extend another unlocked package or a managed package. See Unlocked Packages for more details.

The best way to stop the rollbacks from happening is to ensure report metadata is exported daily and that it is merged into the developer branches before the next release. This way, the reports and dashboards will be up to date and consistent across all environments. Using a third-party data warehouse is not a solution, as it does not address the root cause of the rollbacks. Removing the executive’s ability to change reports is not a good practice, as it limits their flexibility and autonomy. Backing up and reimporting the reports before and after the release is not a reliable or scalable solution, as it can introduce errors and inconsistencies.

 B and D are the decisions that should be made by an Architecture Review Board (ARB), as they involve choosing the best methodology and authentication mechanism for the project, which have significant impacts on the project scope, quality, and security. A is not a decision that should be made by an ARB, as it is a low-level design decision that can be made by the developers or technical leads. C is not a decision that should be made by an ARB, as it is a testing decision that can be made by the testers or quality assurance leads.

QUESTIONNO: 87

What is the process used to initiate a connection for change sets?

A. Modify the source org to allow an outbound connection to the target org

B. Modify the target org to accept an outbound connection from the source org

C. Modify the target org to accept an inbound connection from the source org

D. Modify the source org to allow an inbound connection to the target org

Answer: A

A is the correct answer, as the process to initiate a connection for change sets is to modify the source org to allow an outbound connection to the target org. B and C are incorrect, as the target org does not need to accept any connection from the source org, but only to deploy the inbound change sets that are sent from the source org. D is incorrect, as the source org does not need to allow any inbound connection to the target org, but only to create and upload the outbound change sets to the target org. You can learn more about this process in the Change Sets Basics module on Trailhead.

Following an ALM process can help avoid defects from being deployed to production, by ensuring that the code is tested and validated in different environments before reaching the end users. It can also help release new features on a consistent schedule, by establishing a clear roadmap and timeline for the development and deployment phases. Moreover, it can help prevent existing working functionality from stopping, by implementing backup and rollback strategies, as well as monitoring and troubleshooting tools. Training new users after each minor and major release is not a benefit of ALM, but rather a best practice for user adoption and change management. Defining metrics for application development project success is not a benefit of ALM, but rather a part of the project management and evaluation process.