Salesforce Updated Development-Lifecycle-and-Deployment-Architect Exam Questions and Answers by ashley

The Executive Steering Committee is the management team that is empowered to approve additional budget requirements for a project, as they are responsible for providing strategic direction, oversight, and governance for the project. The Security Review Committee is responsible for ensuring that the project meets the security standards and policies of the organization. The Project Management Committee is responsible for managing the day-to-day activities and deliverables of the project. The Change Control Board is responsible for reviewing and approving any changes to the project scope, schedule, or resources.

 Implementing a pull request and secure code review will contribute to an improvement of code security by ensuring that the code is checked and approved by another developer before merging to the main branch. Integrating a static code security analysis tool in the CI/CD process will contribute to an improvement of code security by automatically scanning the code for vulnerabilities and enforcing security standards. Hiring a company specialized in secure code review or using two developers to review and fix current code vulnerabilities are not actions that will improve code security, but rather remediate existing security issues.

The development model that the architect should recommend to be used by the consolidated development team is the package development model. This model allows teams to build release artifacts that can be tested and released independently from artifacts for other projects, using unlocked packages or second-generation managed packages. This model can help improve the modularity, reusability, and maintainability of the code and configuration, as well as enable source-driven development and continuous integration and delivery. The org development model is not a good choice for the consolidated development team, as it is based on working directly in an org and using change sets or metadata API tools to deploy changes. This model can lead to conflicts, dependencies, and governance issues, especially when working on multiple projects or with multiple teams. The change set development model is also not a good choice for the consolidated development team, as it is based on using change sets to deploy changes between connected orgs. This model can be slow, error-prone, and limited, as it does not support all metadata types, dependencies, or automation. The package development model does not allow packages to be created and deployed using declarative (point-and-click) development tools, without writing code. This is a wrong statement, as the package development model supports both declarative and programmatic development tools, and requires writing code to create and install packages using the Salesforce CLI or APIs. See Package Development Model for more details.

 D is the correct answer, as the risk with this plan is that multiple work-streams with dependencies could impact the go-live. If the legacy system upgrade and the new integration are not aligned and coordinated, there could be delays, errors, or failures in the project delivery. A is incorrect, as the deadline being scheduled during a Salesforce release is not a risk, but an opportunity to leverage the new features and enhancements that Salesforce provides. B is incorrect, as the project team using the Waterfall methodology is not a risk, but a choice that depends on the project scope, complexity, and requirements. C is incorrect, as the legacy system team using an Agile methodology is not a risk, but a choice that depends on the project scope, complexity, and requirements. You can learn more about the risk management in the Project Management Strategies for Salesforce Implementations module on Trailhead.