Free Salesforce Development-Lifecycle-and-Deployment-Architect Practice Exam with Questions & Answers | Set: 4

Integrating an agile issue tracker with software testing and continuous integration tools can provide the following benefits:

Developers can see automated test statuses that commit on a specific user story, which can help them identify and fix any errors or failures quickly.

Developers can use the committed code’s build status directly on the user story record, which can help them track the progress and quality of their work.

 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.

The best practice is to always fix the bug in the developer environment where the project work was done, and follow the normal deployment and testing process. This ensures that the code is consistent, traceable, and validated across all environments. Fixing the bug in UAT is not ideal, as it can introduce new issues, create conflicts with other changes, and bypass the version control system. Spinning up a new sandbox for a hot fix is not necessary, as it can add complexity and overhead to the deployment process. Treating the issue as a change request and putting it in the backlog is not advisable, as it can delay the resolution and affect the user experience.

The sandbox types that the architect should recommend for batch data testing are Partial Copy sandbox and Full sandbox. These sandbox types allow the testing of large data sets that are similar to the production data. Developer Pro sandbox and Developer sandbox have limited storage and may not be able to accommodate the data needed for the batch data testing.

Utilizing a dedicated developer pro sandbox to address critical bugs and release to production is the recommended release management strategy, as it allows the development team to work on the new project without being interrupted by the bug fixes, and also ensures that the bug fixes are deployed to production as soon as possible. Including fixes for critical bugs in the ongoing development sandboxes is not recommended, as it may delay the release of the bug fixes and also introduce conflicts with the new code. Keeping teams separate until the end of the project and creating a full copy sandbox to merge their work then is not recommended, as it may create a lot of merge conflicts and integration issues. Addressing critical bugs in the development sandboxes and pushing those changes to production separately is not recommended, as it may create inconsistencies between the development and production environments.

The optimal way to store the service centers as technical reference data is to add them to a custom metadata type. Custom metadata types allow you to create, update, and deploy records that are defined by a custom object. Custom metadata types are similar to list custom settings, but they have some advantages, such as being deployable, queryable, and packageable. Hierarchical custom settings are not suitable for storing multiple records of the same type, and defining a new custom object with a picklist field is unnecessary and inefficient.

 Extracting each permission set, committing and merging to source control, and running through CI checks is the best strategy to bring the issue of failing SOQL statements to the developer’s attention earlier. This way, the developers can review the changes made by the administrators, and ensure that they do not break any existing functionality or security rules. Asking administrators to only make changes to profiles instead would not solve the problem, as profiles can also affect SOQL queries. Creating a sandbox refresh strategy to ensure each sandbox is refreshed every day would not prevent the issue from happening, as the changes made by the administrators would still be propagated to the sandboxes. Advising developers to switch to SOSL queries that are more robust instead would not address the root cause of the issue, which is the lack of visibility and control over the permission sets.

The best option for the new BU is to use a new stand-alone Salesforce org, not integrated with the others. This will allow the new BU to have flexibility in their business processes, without affecting or being affected by the other BUs. Since the new BU does not share customers with the other BUs, there is no need to integrate with the customer 360-degree view org, which would add complexity and cost. Deploying the new BU in the customer 360-degree view org is not a good idea, as it would create confusion and duplication of data, as well as limit the customization options for the new BU. Using the same Salesforce org of another BU that shares geographical localization with the new BU is also not a good idea, as it would create conflicts and dependencies between the two BUs, as well as reduce the performance and security of the org. Using a new Salesforce org for the new BU, and customizing integration so that it reads and writes customer information from the customer data org is unnecessary and inefficient, as the new BU does not need to access or update the customer data of the other BUs.

 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.

Load testing is the type of testing that will help UC measure the page response time. Load testing simulates the expected number of concurrent users and measures how the system performs under normal load conditions. Unit testing, system integration testing, and stress testing are not designed to measure the page response time.