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

A suitable branching policy to recommend for multiple development teams that work on separate streams of work, with different timelines, is trunk-based development. This policy allows each team to work on their own feature branches, and merge them to the main branch (trunk) frequently, using pull requests and code reviews. This can help avoid merge conflicts, ensure code quality, and enable continuous integration and delivery. Leaf-based development is not a valid branching policy, as it is a term used to describe the nodes in a tree data structure. GitHub flow is a specific implementation of trunk-based development, but it is not a branching policy by itself. Scratch-org-based development is not a branching policy, but a development model that uses scratch orgs as ephemeral environments. See Trunk-Based Development for more details.

Deploying unsupported components manually before/after deployment is the best way to address the issue of Metadata API not supporting all the components yet. Metadata API is a powerful tool for deploying changes between orgs, but it does not cover all the metadata types that are available in Salesforce. Some examples of unsupported components are email templates, dashboards, reports, and custom settings. These components need to be deployed manually by using other tools or methods, such as change sets, data loader, or manual configuration.

The Tooling API is the best choice for the team that wants to use SOQL queries to retrieve and make changes to smaller pieces of Salesforce metadata through their Java application. The Tooling API provides access to metadata objects such as Apex classes, triggers, workflows, validation rules, custom objects, and fields. It also supports CRUD operations, as well as executing anonymous Apex code. The other APIs are not suitable for this use case, as they either deal with larger metadata components (Metadata API), user interface components (User Interface API), or data records (Any Salesforce API).

According to the [Salesforce Performance Testing Guide], performance tests must be run in a sandbox, a business justification must be provided to Salesforce, and performance tests may be run without advanced notice, but Salesforce will not store performance logs. Salesforce does not need to be informed 7 days before starting performance tests, and Salesforce will not monitor test activity to ensure there are no issues with Salesforce Services.

The problem is that UAT is on a preview release and SIT is not. A preview release is a version of Salesforce that contains the features and enhancements that will be available in the next major release. Preview releases are usually available a few weeks before the official release date, and they are assigned to a subset of instances. If UAT and SIT are on different instances, they may have different release versions, which can cause deployment issues. For example, if UAT has a preview release that contains some new metadata types that are not available in SIT, then deploying those metadata types from SIT to UAT will fail. To avoid this problem, the architect should check the Sandbox Preview Guide1 and the Release Notes2 to see if there are any changes that affect the deployment, and refresh and redeploy the sandboxes accordingly. There is a problem, and it is not expected behavior. Using the DX command line instead will not solve the problem, as it will still encounter the same version mismatch. SIT is not on a preview release and UAT is not, as that would not cause any deployment issues.

To move to the package development model, the administrator must enable both the Dev Hub and the Second-Generation Managed Packages in setup. The Dev Hub is the main org where the administrator can create and manage scratch orgs and packages. The Second-Generation Managed Packages are the new format of packages that support modular development and versioning. The Unlocked Packages are a type of second-generation packages that are not tied to a namespace and can be installed and customized in any org. The Source Tracking for Scratch Orgs is a feature that allows the administrator to track the changes made in a scratch org and push or pull them to or from a source repository.

The only condition that would make continuous integration unsuitable for UC is if their Salesforce instance has only standard functionality, as this would mean that there is no need for code deployment or version control. Option A is not a valid reason, as test scripts can be generated and executed as part of the continuous integration process. Option B is not a valid reason, as a full sandbox is not a requirement for continuous integration, and other types of sandboxes can be used instead. Option D is not a valid reason, as there are free or low-cost software tools available for continuous integration, such as Jenkins, Git, and Ant