Development-Lifecycle-and-Deployment-Architect Practice Test

A.   Multiple triggers on the same object, making it hard to understand the order of operations.

B.   Multiple unit test failures would be encountered.

D.   Duplicated logic across Visual force pages and Apex classes performing similar tasks.

Explanation:

Multiple triggers on the same object can cause conflicts and performance issues. Multiple unit test failures can indicate poor code quality and lack of maintenance. Duplicated logic across Visualforce pages and Apex classes can lead to inconsistency and redundancy.

B.   Version control repository

D.   Continuous integration tool

E.   Issue tracking Tool

Explanation:

To support application lifecycle methodology, you need tools that can help you manage the source code, automate the deployment process, and track the issues and bugs. A version control repository is a tool that allows you to store, track, and collaborate on the source code of your application. A continuous integration tool is a tool that allows you to automate the deployment of your code to different environments, as well as run tests and validations. An issue tracking tool is a tool that allows you to record, monitor, and resolve the issues and bugs that arise during the development and testing phases. A database management system is a tool that allows you to store, manipulate, and query data, but it is not directly related to application lifecycle methodology. A middleware is a software layer that facilitates communication and data exchange between different applications, but it is not directly related to application lifecycle methodology either.

D.   Manually validate change sets before deployment.

Explanation:

Manually validating change sets before deployment is a recommended practice to avoid possible delays while deploying a change set, as it can help you identify and resolve any errors or dependencies before the actual deployment. Change set performance is not independent of included components, as some components may take longer to deploy than others. Manually creating new custom objects and new custom fields or manually applying the field type changes are not advisable, as they can introduce human errors and inconsistencies between environments. See Deploy Changes with Change Sets for more details.

A.   Introduce manual code review before deployment to the testing sandbox.

D.   Introduce static code analysis before deployment to the testing sandbox.

Explanation:

The best options to enforce code quality in UC’s continuous integration process are to introduce manual code review before deployment to the testing sandbox and to introduce static code analysis before deployment to the testing sandbox. Manual code review can help identify and fix any errors, bugs, or best practices violations in the code. Static code analysis can help check the code quality, complexity, and security using automated tools and standards. Introducing manual code review before deployment to the production org may be too late, as the code may have already caused defects or issues in the testing sandbox. Increasing the size of the testing team assigned to the project may not improve the code quality, as the testing team may not have the skills or authority to review or modify the code. Testing data creation is outside the scope of code quality.

B.   Use an AppExchange or third-party tool that is specialized in Salesforce deployment.

Explanation:

To track Salesforce metadata throughout the development lifecycle across sandboxes and production, the architect should recommend using an AppExchange or third-party tool that is specialized in Salesforce deployment. These tools can provide features such as version control, dependency analysis, automated testing, and rollback capabilities. Using an Excel sheet to track deployment steps and document the SFDX commands is not a reliable or scalable solution, as it is prone to human errors and does not provide any automation or validation. Using ChangeSet to track deployed customizations is also not a good option, as ChangeSet is limited in the types of metadata it can deploy and does not support versioning or dependency management. Using Salesforce SFDX commands to deploy to different sandboxes is a possible solution, but it requires a high level of technical expertise and does not provide a graphical interface or reporting capabilities.