Salesforce B2C-Solution-Architect - Salesforce Certified B2C Solution Architect

To adhere to global data privacy acts and respect customers’ privacy, the retailer should enable terms and conditions functionality within Marketing Cloud, which will allow them to display a custom message and a checkbox for customers to agree before they can submit a form or join a list. The retailer should also use profile and preference center functionality for Marketing Cloud Email Studio, which will allow them to capture consent and opt-in confirmation from customers, as well as provide them with options to manage their email preferences and unsubscribe.

References:

[Terms and Conditions]

[Profile and Preference Centers]

Option A is correct because Customer 360 Data Manager can be used to ensure that there is only a single contact for a particular person across all the subsidiaries of a company. Customer 360 Data Manager is a tool that enables data integration and identity resolution across multiple Salesforce clouds and external systems. It can match and merge duplicate contacts based on various criteria and create a single source of truth for customer data.

Option C is correct because Duplicate Matching Rules can be used to ensure that there is only a single contact for a particular person across all the subsidiaries of a company. Duplicate Matching Rules are rules that define how Salesforce identifies duplicate records based on standard or custom fields. They can prevent users from creating or updating duplicate contacts based on various criteria and actions.

Option B is incorrect because Third-party application or AppExchange tool is not an option that the Solution Architect can use to ensure that there is only a single contact for a particular person across all the subsidiaries of a company. Third-party application or AppExchange tool is not a specific or native solution for this problem, but rather a general or external solution that may or may not work depending on the features and compatibility of the application or tool.

Option D is incorrect because Lightning Data Services is not an option that the Solution Architect can use to ensure that there is only a single contact for a particular person across all the subsidiaries of a company. Lightning Data Services is a tool that enables developers to access, cache, and modify data in Lightning web components without using Apex code. It does not have any functionality to prevent or resolve duplicate contacts.

References:

[Get Started with B2C Solution Architect Cert Prep - Trailhead]

[Certification - B2C Solution Architect - Trailhead]

B2C Solution Architect Certification Guide | Salesforce Ben

C is correct because Marketing Cloud Connect uses the SOAP API to integrate multiple business units in Marketing Cloud with Salesforce core orgs. The SOAP API enables data synchronization, triggered sends, journey builder integrations, and tracking data.

A is incorrect because the Tooling API is used to create and modify metadata in Salesforce core orgs, such as custom objects, fields, workflows, etc. It is not used for Marketing Cloud Connect integration.

B is incorrect because the REST API is used to access resources in Marketing Cloud, such as contacts, content, campaigns, etc. It is not used for Marketing Cloud Connect integration.

D is incorrect because the Streaming API is used to receive notifications of data changes in Salesforce core orgs, such as record updates, deletes, etc. It is not used for Marketing Cloud Connect integration.

References:

: https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm

: https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_api_tooling.htm

: https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm

: https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/intro_stream.htm

The fieldMapping custom settings in Service Cloud define how the attributes from the Commerce Profile are mapped to the fields on the Service Contact. If the nationalParks attribute was not mapped, then the service agent would not be able to see or update it in the Service Cloud console. References: https://help.salesforce.com/s/articleView?id=sf.b2c_service_cloud_connector_field_mapping.htm&type=5

Salesforce Connect is a feature that allows accessing and integrating external data from various sources without copying or storing it in Salesforce. Salesforce Connect uses external objects and external data sources to create a virtual data model that can be used in Salesforce applications and tools. The justifications for using Salesforce Connect in this solution are:

Need access to all external data in near real-time. Salesforce Connect allows accessing external data from ERP or other systems in near real-time, without any delays or synchronization issues. This ensures that the data is always up-to-date and consistent across systems.

The external data is changing frequently. Salesforce Connect allows reflecting any changes or updates made to the external data in ERP or other systems immediately in Salesforce, without requiring any manual intervention or batch processes. This ensures that the data is always accurate and reliable across systems.

Need real-time access to a small fraction of external data. Salesforce Connect allows accessing only a small fraction of external data that is relevant and needed for a specific use case, such as displaying customer order history or details. This reduces network overhead and improves performance.

Option A is incorrect because accessing external data using workflows and triggers is not possible or supported with Salesforce Connect. Option C is incorrect because integrating external data without writing custom code is not a justification for using Salesforce Connect, as it may require some custom code or configuration depending on the data source and use case. References:

https://help.salesforce.com/s/articleView?id=sf.datacloud_connect_overview.htm &type=5

https://help.salesforce.com/s/articleView?id=sf.datacloud_connect_considerations.htm &type=5

These are three considerations that the financial services firm should be aware of when limiting data processing across these clouds. Removing a data processing restricted contact within Marketing Cloud requires removing the restriction first before removing the contact, as deleting a restricted contact will result in an error message. Exporting relevant customer data on Salesforce Platform so it is retained first before deleting or providing any data is a best practice for complying with data requests or regulations. Restricting data within Marketing Cloud requires contacting a Marketing Cloud account representative, as this feature is not available in the user interface.

A is correct because the Service Cloud Connector only works with registered B2C Commerce customer accounts and does not support guests or anonymous storefront shoppers. The connector uses the customer ID to link the Service Cloud contact with the B2C Commerce customer profile.

B is incorrect because the Service Cloud Connector supports both SOAP and REST services for data synchronization between Service Cloud and B2C Commerce.

C is incorrect because the Service Cloud Connector requires B2C Commerce to be registered as a remote site in Service Cloud regardless of the geographic region. This is to allow outbound messages from Service Cloud to B2C Commerce.

D is incorrect because the Service Cloud Connector requires a dedicated Integration User with administrative rights in both Service Cloud and B2C Commerce. This user is used to authenticate and authorize the data synchronization between the two systems.

References:

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorOverview.html

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorDataSynchronization.html

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorSetup.html

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorUserSetup.html

Option A is correct because running load testing in B2C Commerce pre-launch against the production instance connected to a full copy sandbox in Service Cloud is a recommended practice to ensure that the multi-cloud solution can handle the expected traffic and transactions without compromising performance or functionality.

Option C is correct because using a single Marketing Cloud instance to connect to multiple Service Cloud environments using Marketing Cloud Connect for each business unit is a recommended practice to enable data synchronization and integration between the clouds without duplicating data or creating conflicts.

Option B is incorrect because using Marketing Cloud business units as testing environments is not a recommended practice, as it may cause data quality issues, security risks, and configuration challenges. Marketing Cloud business units should be used for segmentation and personalization purposes, not for testing or development.

Option D is incorrect because using a Service Cloud partial copy sandbox to provide better performance than a developer pro sandbox as well as a normal sandbox is not a valid statement, as partial copy sandboxes have the same performance characteristics as developer pro sandboxes and normal sandboxes. The main difference between partial copy sandboxes and other types of sandboxes is the amount of data they can store.

References:

[Get Started with B2C Solution Architect Cert Prep - Trailhead]

[Certification - B2C Solution Architect - Trailhead]

These answers are correct because they are ways that Salesforce CDP can help the organization in this scenario. Salesforce CDP can ingest customer data from each system and use matching rules to find records representing the same person, uniting them under a Unified Individual. This creates a single view of the customer across all systems and channels. Salesforce CDP can also power experiences through other channels like Marketing Cloud Engagement by activating customer segments. This enables personalized and targeted marketing campaigns based on customer data and behavior. References: https://www.salesforce.com/products/customer-data-platform/overview/

CDP is a feature that allows creating a unified and holistic view of the customer across different systems and channels. CDP can use various identifiers, such as email, phone, or social media, to recognize customers as humans and extend existing records related to that human across connected systems, such as B2C Commerce, Service Cloud, and Marketing Cloud. CDP can also assign a consistent Global Party ID to each human, which can be used as a unique identifier across the systems. References: https://www.salesforceben.com/the-drip/complet e-guide-to-customer-data-platforms-and-salesforce-cdp/