Universal Containers (UC) is about to implement Sales Cloud, Service Cloud, and Revenue Cloud within its newly created Salesforce environment. But before UC begins, the CIO would like to understand the options for creating and migrating changes within Salesforce. UC is about to use a sandbox for the initial build and will deploy customisation up to the production environment. UC has decided to build packages of metadata to silo the functionality between the three clouds it is implementing for.
What are two key considerations a Solution Architect should keep in mind when recommending packaging?
Choose 2answers

• A. It is impossible to track source controlwith package development; either the org owns the source or a source control does, but never both.
• B. Only utilize one functional automation tool (Flow, Workflow Rules, Process Builder) per object.
• C. Clouds like Revenue Cloud have their own packages so it is easy to work with them because their automation is limited.
• D. Design the package as modular, loosely coupled units of metadata rather than large chunks of an org.

Universal Containers (UC) is in the process of identifying if Revenue Cloud will work for its business processes. UC has already implemented Sales Cloud, which includes complex steps and checklists that are orchestrated based on changes made to an Opportunity. Based on the current Sales Cloud implementation, UC has concerns about how Revenue Cloud will interact with its current customizations on the Opportunity object and if it will be difficult to customize the solution in the future.
Which design approach should a Solution Architect recommend tomitigate concerns about custom processes on any single object?

• A. Migrate automations from Process Builder to flows triggered by record updates, organizing operations in separate flows for the "Before Save" and "After Save" contexts.
• B. Leave the orchestration of the automation to Process Builder, but invoke autolaunched flows from Process Builderso that the actual operations run in flows.
• C. Use an event-driven design to separate automations that could run asynchronously from the save cycle with a third-party tool like Heroku.
• D. Migrate automations from Process Builder to a single flow that is triggered by record updates, using only the "After Save" context so that all operations can be organized in a single flow.

SharpField is a fast-growing company that provides SaaS for commercial service providers. SharpField has been acquiring other similar companies and plans to continue to do so for thenear future.
After a recent acquisition of a company that also has a Salesforce org, the CIO wants to know the correct path forward on deciding whether to integrate the acquired companies into SharpField's existing landscape.
What should a Solution Architect recommend to the CIO to ensure the correct org strategy for SharpField going forward?

• A. Prioritize migrating the newly acquired company toSharpField's Salesforce org first, then perform an org strategy analysis to assess the Business, Technology, Governance, and Operations requirements for any future acquisitions.
• B. Recommend a single-org strategy and development of strict processes for all acquired companies to follow.
• C. Prioritize completing an in-depth org strategy analysis, focused on the Business, Technology, Governance, and Operations requirements at SharpField.
• D. Recommend a multi-org strategy and development of required integration layers to move the required shared data between instances of any and all acquired Salesforce instances.

Universal Containers uses an ERP as system of record (SOR) for its product data, and Sales Cloud and Revenue Cloud for its sales data. TheProduct data must be synced with Salesforce so that sales representatives can add the products to their Opportunities and Quotes. As Products are deactivated within the ERP, they should no longer be available. Since Sales Cloud is the SOR for Opportunities and Revenue Cloud is the SOR for Quotes, the Solution Architect has been asked to come up with an archiving strategy that preserves Opportunity and Quote data related to these deactivated products m Salesforce for historical reference.
What should a Solution Architect recommend to manage the deactivation of the Products and archiving of the Saks data?

• A. Deactivate the Product m Salesforce once it is deactivated m the ERP. Archive the Opportunity and Quote data in a third-party system and bring back into Salesforce as External Objects.
• B. Deactivate the Product in Salesforce once it is deactivated m the ERP. Mark the Opportunity and Quote data in Salesforce as inactive so they do not show up in reporting.
• C. Remove the Product from active Opportunities and Quotes. Archive the Opportunity and Quote data in a third-parry system and bring back into Salesforce as External Objects.
• D. Delete the Product in Salesforce once it is deactivated in the ERP. Archive the Opportunity and Quote data m a third-party system and bring back into Salesforce as External Objects.

Universal Containers serves customers globally across two businesses. Each business has its own org for managing itssales and support operations. Each line of business also maintains its own reporting systems using both CRM Analytics and Salesforce reports, but the CEO is asking for a unique dashboard that includes the global opportunity pipeline with data from both orgs.
What should a Solution Architect propose?

• A. Use CRM Analytics in the primary org and create a Salesforce External Connection. Then, create a dataflow to combine data from both orgs.
• B. Use one org as primary and create external objects for the accounts and opportunities of the other one.
  Then, use standard reports.
• C. Use one org as primary and an ETL tool to synchronize the accounts and opportunities of the other org.
  Then, use standard reports.
• D. Use CRM Analytics in the primary org and then, in thedashboards, use Salesforce Connect to query the data from the other org.