B2C-Solution-Architect Exam Dumps : Salesforce Certified B2C Solution Architect (Arch-302)

The B2C Commerce to Service Cloud Connector is a solution that enables integration between B2C Commerce and Service Cloud. It allows displaying customer and order information in Service Cloud, creating orders on behalf of customers, and synchronizing customer data between the two systems. When introducing the Service Cloud Connector into an existing Salesforce Org, the following functionality considerations should be aware of:

• In order to implement the Service Cloud Connector it is necessary to enable Person Accounts, a change which cannot be reverted once implemented. Person Accounts are a type of account in Salesforce that combines an account and a contact into a single record. The Service Cloud Connector requires Person Accounts to store customer information from B2C Commerce. Enabling Person Accounts is an irreversible change that affects the entire Salesforce Org and may have implications for other features or customizations.
• The Service Cloud Connector is distributed as a managed package that can be extended to meet client-specific needs but with core functionality that cannot be altered. A managed package is a collection of application components that can be installed from AppExchange or other sources. The Service Cloud Connector is a managed package that provides core functionality for integrating B2C Commerce and Service Cloud. The core functionality cannot be modified or deleted, but it can be extended or customized using Apex code, Visualforce pages, or Lightning components.

Option C is incorrect because the Service Cloud Connector does not natively support accounts and contacts, households, and multi-brand customer models. It only supports person accounts as a customer model by default. Option D is incorrect because the Service Cloud Connector provides a collection of Lightning components that display customer and order information within Service Cloud, which do not need to be customized or deployed by a developer. References:

• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5

A. Fixing the data quality issues in Service Cloud before migrating to Marketing Cloud can help avoid duplicate or incomplete contacts in Marketing Cloud, which can affect the contact count, billing, and personalization. Data quality issues can be fixed by using tools such as Data Loader, Duplicate Management, or ETL tools. C. Mapping Contact, Lead, and Account objects within Marketing Cloud can help enable personalization by using data from Service Cloud in email content or journeys. Mapping can be done by using Marketing Cloud Connect or Customer 360 Data Manager. References: &type=5 &type=5 &type=5

Marketing Cloud should be the system of record for lifetime engagement tracking and history, as well as other data for personalization or segmentation, as it is the system that collects and analyzes the customer’s interactions and behaviors across multiple channels and touchpoints. Marketing Cloud can also use features like Audience Builder and Contact Builder to create unified customer profiles and segments based on various data sources3 . Service Cloud should be the system of record for storing primary attributes (name, address, birthday, phone, and email) about the customer, as it is the system that represents a person across multiple Salesforce clouds and can store and manage the customer’s consent and compliance preferences using features like Individual object, Data Protection and Privacy, and Consent Management .