Salesforce Developer Development-Lifecycle-and-Deployment-Architect Syllabus Exam Questions Answers

To reduce deployment time, UC can use the following strategies:

• Use recent deployment validations and the quick deploy feature, which can allow them to skip the validation step in production and deploy the changes faster, if they have already validated the changes in a sandbox within the last four days.
• Specify the test to run by using RunSpecifiedTests test level, which can allow them to run only the tests that are relevant to the components being deployed, instead of running all the tests in the org.

 To run a subset of tests, set the Run Specified Tests test level on the DeployOptions object and pass it as an argument to the deploy() call and specify only the test classes that are required to be executed, as specifying the test method is not supported in DeployOptions. These statements are true regarding running specific tests during deployments. The Run Specified Tests test level allows the developer to choose which tests to run in production, while specifying the test method is not a valid option for the DeployOptions object.

Test classes should execute under various profiles to ensure that the code works for different user permissions and sharing settings. Test data must have positive as well as negative data to cover all possible scenarios and edge cases.

 D is the correct answer, as utilizing automated source control, test, and build systems to test and deploy to production can help to maintain quality and reduce the risk of bugs being introduced to production. Automated systems can ensure that the code is consistent, version-controlled, tested, and validated before deploying to production. A is incorrect, as requiring developers to deploy completed code and unit tests directly to production can introduce errors and conflicts, as well as bypass the testing and validation stages. B is incorrect, as deploying all functionality together can create complexity and dependency issues, as well as delay the release of completed features. C is incorrect, as using a spreadsheet to track approved changes that should be released with change sets can be prone to human errors and inconsistencies, as well as lack of automation and integration. You can learn more about this topic in the Continuous Integration and Continuous Delivery module on Trailhead.