Development-Lifecycle-and-Deployment-Architect Practice Test

B.   Refresh a Sandbox during the Release Preview Window to ensure they have the upcoming release.

C.   Run regression tests in an upgraded sandbox to detect any issues with the Upgrade.

D.   Review the release notes for automatically-enabled features and technical debt.

Explanation:

Refreshing a sandbox during the release preview window to ensure they have the upcoming release is a step that the team at UC should take to prepare for the new Salesforce release, as it allows them to test their application in an environment that matches the production environment after the upgrade. Running regression tests in an upgraded sandbox to detect any issues with the upgrade is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to verify that the existing functionality is not affected by the new features or changes introduced by the upgrade. Reviewing the release notes for automatically-enabled features and technical debt is also a step that the team at UC should take to prepare for the new Salesforce release, as it helps them to understand the impact and benefits of the new features or changes, as well as to identify and resolve any technical debt that may cause issues or conflicts with the upgrade. Contacting Salesforce to schedule a time to upgrade the full sandbox is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not possible to request a specific time for the upgrade of the full sandbox, which is determined by Salesforce and depends on the release window and the pod assignment. Upgrading any SOAP integrations to the newest WSDL as early as possible is not a step that the team at UC should take to prepare for the new Salesforce release, as it is not necessary to upgrade the SOAP integrations to the newest WSDL, unless they want to use the new features or fields introduced by the upgrade. The SOAP integrations will continue to work with the previous WSDL versions, as they are backward compatible.

D.   Utilize the daily release process to create the report directly in a full sandbox and then deploy it to production.

Explanation:

The best release strategy for creating a new report to support an urgent client request is to utilize the daily release process. The daily release process is designed for small and quick changes that do not require extensive testing or approval. The daily release process can create the report directly in a full sandbox and then deploy it to production. The major and minor release processes are more suitable for large and complex changes that require more testing and approval. The major and minor release processes should not create the report directly in production, as this may cause errors or conflicts.

C.   Product owner

Explanation:

A product owner is responsible for defining the scope and prioritizing the backlog of the project. A product owner can help the COE manage the scope creep between the different projects by aligning the business goals and ensuring the value delivery. A scrum master, a release manager, and a change manager are not directly involved in scope management.

D.   The team improves and evolves its processes and frequently delivers value to the end users.

Explanation:

An agile team is one that improves and evolves its processes and frequently delivers value to the end users. This is the main characteristic of an agile team, as opposed to a traditional team that follows a fixed plan and delivers on predefined dates. Agile teams use various frameworks, such as Scrum, Kanban, and Extreme Programming, but these are not essential to be agile. Agile teams also have shorter iterations, such as biweekly sprints, but these are not the only way to ensure on-time delivery.

C.   Load Test

D.   Performance Test

Explanation:

C and D are the correct answers, as Load Test and Performance Test are the test types that should be suggested to ensure that a large inbound call center does not experience platform slowdowns under high call volume for the Lead object. A load test is a test that measures the performance and behavior of the system under a specific load, such as a large number of concurrent users or requests. A performance test is a test that measures the speed, responsiveness, and stability of the system under various conditions, such as different configurations or environments. These tests can help to identify and prevent any potential issues or bottlenecks that could affect the user experience or the system functionality. A is incorrect, as Unit Test is not a test type that should be suggested for this scenario, as it is a test that verifies the functionality and logic of a single unit of code, such as a method or a class, but not the performance or behavior of the system as a whole. B is incorrect, as Stress Test is not a test type that should be suggested for this scenario, as it is a test that measures the performance and behavior of the system under extreme or abnormal conditions, such as exceeding the capacity or resources of the system, but not the performance or behavior of the system under normal or expected conditions. You can learn more about these tests in the Testing Strategies module on Trailhead.