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. 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.
• D. 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.

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

Universal Containers (UC) is a global organisation that wants to establish a 628 Commerce site to meet changing customer expectationsand expand into new markets. These expectations include being able to self- serve 24x7 and get automated updates on orders. There are existing sales channels used at UC. Including a standard Sales team as well as a partner sales channel.
The sales leader met with a Solution Architect and shared that they want to grow their digital capabilities over the next 2 years. Time is of the essence and the sales leader needs to have the ecommerce solution in place as soon as possible to capture market share in new geographies before other competitors move in. The executive team has promised prompt access to key stakeholders as needed.
What is the appropriate next step 'or the Solution Architect?

• A. Recommend discovery meetings with additional stakeholders to gather information on the functional and technical requirement across the sales and other functional areas, then provide a recommendation based on information gathered to deliver an MVP.
• B. Propose the introduction of B2B Commerce and CPQ to address the key areas of need such as global commerce, complex pricing, quoting and discounting needs; highlight the key features 6r>a the alignment of the features to the needs outlined.
• C. Propose a set of high-level design options with architecture diagrams depicting thepotential elements of a solution that would meet the needs of the enterprise, including pros and cons to help the stakeholders make final decisions.
• D. Recommend in iterative rollout strategy for one of the new geographies where B2B Commerce is first rolled out to secure first mover status, while theSolution Architect gathers more requirements around other capabilities and requirements, and then roll those out over subsequent phases.

Towards the end of the discovery phase, the sales manager and subject matter experts raise a request to get hands-on experience with the solution as soon as possible. They want to ensure the requirements they provided are correctly built out inSalesforce. The project sponsor is unsure how that request may affect the schedule.
Which method should a Solution Architect consider in this scenario to validate the requirements during the build sprint without impacting the project timelines?

• A. Run a User Acceptance Testing discovery session, based on the Functional Specification Document, to ensure the testing script meets the end users' needs.
• B. Give every end user the Functional Specification Document as their training materials and test them on the contents.
• C. Ensurethe project sponsor reviews and signs off on the Functional Specification Document as an acknowledgment that what was built aligns with the original requirements.
• D. Give the end users access to a sandbox environment and a testing script for each of the user stories. Ask UAT testers to perform their tasks and collect feedback from them in the testing script.