Universal Containers (UC) innovative apps division is releasing an application which can be installed in their trading partners Salesforce environment. The partners can then build on top of the application with process builders and triggers so the container booking process can be integrated with the trading partners own processes. What is the recommended mechanism for releasing the application?
Correct Answer: D
Explanation Managed package is the recommended mechanism for releasing an application that can be installed in other Salesforce environments. Managed packages allow for versioning, licensing, and upgradeability of the application. They also protect the intellectual property of the developer by hiding the source code of the Apex classes and Visualforce pages.
Universal Containers is validating an outbound change set from the Developer Sandbox to the production org. Which two locking behaviors will occur during a deployment? Choose 2 answers
Correct Answer: A,D
Explanation A and D are the correct answers, as they are the locking behaviors that will occur during a deployment. A is correct, as the production org will be locked and administrators cannot modify metadata during this time, to prevent any conflicts or inconsistencies in the deployment. D is correct, as the production org will be locked and users will still be able to read/write data to the org, to minimize the impact on the business operations and user experience. B is incorrect, as the sandbox org will not be locked and administrators can still modify metadata, as the sandbox org is not the target of the deployment. C is incorrect, as the production org will not be locked and users can only read data during this time, as this would disrupt the business operations and user experience. You can learn more about the locking behaviors in the [Deploy Changes with Change Sets] unit on Trailhead.
Universal Containers (UC) had implemented two full sandboxes. One, known as Stage, is used for performance, regression testing, and production readiness check. The other is used primarily for user acceptance testing (UAT). Both full sandboxes were refreshed two months ago. Currently, UC is targeting to start user acceptance testing in two weeks, and do production release in four weeks. An admin also realized Salesforce will have a major release in six weeks. UC needs to release on the current Salesforce version, but also wants to make sure the new Salesforce release does not break anything What should an architect recommend?
Correct Answer: A
Explanation The best option for UC is to refresh Stage now, and do not refresh UAT. This way, Stage will be on the preview instance and UAT will not. This will allow UC to test their application on both the current and the next Salesforce version, and ensure that they can release on the current version without any issues. Option B is incorrect because it is not necessary to check the Sandbox Preview Guide or refresh and redeploy to UAT. Option C is incorrect because it is too late to work with support to get on the preview instance after the cutoff dates. Option D is incorrect because it will result in both Stage and UAT being on the same version, which will not allow UC to test their application on the next Salesforce version.
Universal Containers CUC) is an enterprise financial company that operates in EMEA, AMER, and APAC. Because of regulatory requirements, UC has a separate Salesforce org for each region. Each org has its own customizations that fit for the region needs, but there are also standard processes that apply to all regions requirements. As the deployment architect, what should be considered for the multi-org deployment strategy?
Correct Answer: C
Explanation Deploying metadata to production orgs using package development model is the best option for the multi-org deployment strategy, as it allows you to create modular and reusable packages that can be easily installed and updated across different orgs. Deploying metadata to production orgs using managed packages is not suitable for this scenario, as managed packages are typically used by ISVs to distribute their applications to customers, and they have some limitations and restrictions that may not fit the requirements of UC. Deploying metadata to production orgs using unmanaged packages is also not a good option, as unmanaged packages are mainly used for one-time distribution of components, and they do not support upgrades or dependencies. Deploying metadata to production orgs using change sets is not feasible for this scenario, as change sets can only be used to deploy metadata between connected orgs in the same Salesforce instance, and UC has separate orgs for each region. See [Package Development Model] for more details.
Universal Containers (UC) has multiple development teams that work on separate streams of work, with different timelines. Each stream has different releases of code and config, and thedelivery dates differ between them. What is a suitable branching policy to recommend?
Correct Answer: B
Explanation 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.
