Pass the Salesforce Architect Exams B2C-Solution-Architect Questions and answers with ValidTests

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

This flow allows the customer to purchase online and pick up their order in the store using B2C Commerce, Salesforce Order Management, and Service Cloud. B2C Commerce exports the order to Salesforce Order Management, which handles the order orchestration and fulfillment. Salesforce Order Management passes the order information to Service Cloud, which can be used by the store staff to check the order details and availability. Once the order is picked up by the customer, Service Cloud updates the final status in Salesforce Order Management, which can trigger notifications or invoices. References: https://help.salesforce.com/s/articleView?id=sf.order_mgmt_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_mgmt_service_cloud_integration.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 headless B2C Commerce approach can help solve the needs by decoupling the front-end presentation layer from the back-end commerce functionality. This can allow the company to leverage their existing content management systems and deliver consistent branding across different countries. LINK cartridges can help integrate B2C Commerce with third-party systems and services, such as payment providers, tax calculators, or social media platforms. SFRA-style development can help create a responsive and customizable storefront that follows best practices and standards. Heroku and MuleSoft can help build and connect custom applications and APIs that support the complex business logic and data flows required by the global pharmaceutical company. References:

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

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

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

https://www.salesforce.com/products/platform/overview/

https://www.mulesoft.com/platform/enterprise-integration

The Order on Behalf of functionality allows Service Cloud agents to create orders for customers on the B2C Commerce storefront. To enable this functionality, the following design and architecture considerations should be followed:

Verify that the permissions used are Login_On_Behalf, Login_Agent, and Create_Order_On_BehaIf_Of business manager functional permissions. These permissions are required for the Service Cloud Connector user in B2C Commerce to perform the Order on Behalf of actions.

The Order on Behalf of feature in the Service to B2C Commerce Connector only supports person accounts as a customer model by default. If the customers using the storefront are household accounts, additional customization is required to map the household account ID to the B2C Commerce customer ID.

Verify that agents are Service Cloud and B2C Commerce users with Order on Behalf rights. Agents need to have both Service Cloud and B2C Commerce user accounts with the appropriate roles and permissions to access the Order on Behalf of feature.

Option C is incorrect because a default user is not required for anonymous storefront shoppers. Option D is incorrect because the REST calls between B2C Commerce and Service Cloud do count towards API governor limits. References:

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

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

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

B. Service Cloud should be implemented before Marketing Cloud to ensure that the Salesforce Contact IDs can be used in Marketing Cloud as unique identifiers. This allows for a consistent and unified view of the customer across the Salesforce products and avoids duplicate contacts in Marketing Cloud. C. Customer data from B2C Commerce and the legacy CRM should be deduplicated before being imported into Service Cloud. This ensures that there are no duplicate contacts in Service Cloud that could cause data quality issues or conflicts when syncing with Marketing Cloud. D. Custom development work is required to connect B2C Commerce to Marketing Cloud and use the Salesforce Contact ID. This involves creating a service definition in B2C Commerce that points to Marketing Cloud’s REST API and passing the Salesforce Contact ID as the contact key when triggering journeys or updating contact data. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

Field Level Encryption is a feature that allows encrypting data at field level in Marketing Cloud. It encrypts data at rest to facilitate compliance with data privacy and security regulations. It also allows importing encrypted data into Marketing Cloud and decrypting it at send time. References: https://help.salesforce.com/s/articleView?id=sf.mc_overview_field_level_encryption.htm &language=en_US&type=5

B is correct because Marketing Cloud can be used for customer segmentation based on VIP status and cart abandonment behavior. B2C Commerce can be used for creation of coupon codes using promotion rules and coupon code restrictions. B2C Commerce and Marketing Cloud functionalities can be used to send abandoned cart emails using the Marketing Cloud Connector cartridge and the Abandoned Cart Journey template. Marketing Cloud can track email open and forward count using tracking metrics.

A is incorrect because Service Cloud is not used for customer segmentation or creation of coupon codes. Service Cloud is used for customer service and case management.

C is incorrect because B2C Commerce is not used for customer segmentation or creation of coupon codes. B2C Commerce is used for online shopping and order management.

D is incorrect because Tableau CRM is not used to track email open and forward count. Tableau CRM is used for data analysis and visualization.

References:

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

: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/coupons/b2c_creating_coupon_codes.html

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

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

This answer is correct because it is a way to export all the customer data from B2C Commerce and import into Service Cloud without additional development. Business Manager is a tool that allows B2C Commerce administrators to export customer data in CSV format. Data Loader is a tool that allows Salesforce administrators to import data from CSV files into Salesforce objects. References: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/BusinessManager/ExportingCustomerData.html https://developer.salesforce.com/docs/atlas.en-us.dataLoader.meta/dataLoader/data_loader.htm

The B2C Commerce - 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. Prior to implementation, a Solution Architect should keep in mind the following considerations:

Guests or anonymous storefront shoppers are not supported in this scenario. The Service Cloud Connector requires a customer account to be created in B2C Commerce and Service Cloud for each shopper. Guests or anonymous shoppers who do not have an account cannot be supported by the Service Cloud Connector. Therefore, the Solution Architect should ensure that the B2C Commerce storefront requires or encourages shoppers to create an account before placing an order.

Service agents need a corresponding storefront login mapped to their Service Cloud user record. The Service Cloud Connector requires a mapping between the service agent’s user record in Service Cloud and the customer’s account record in B2C Commerce. This mapping allows the service agent to access customer and order information from B2C Commerce and create orders on behalf of the customer using the storefront login. Therefore, the Solution Architect should ensure that the service agent’s user record has a field that stores the corresponding storefront login of the customer.

The Service Cloud Connector only supports Person Accounts as a customer model. 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. Therefore, the Solution Architect should ensure that Person Accounts are enabled and configured in Service Cloud before implementing the Service Cloud Connector.

Option B is incorrect because B2C Commerce does not need to be registered as a remote site for the Service Cloud Connector to work. A remote site is a web service or domain that Salesforce can access from Apex code or Visualforce pages. The Service Cloud Connector does not use Apex code or Visualforce pages to access B2C Commerce, but rather uses REST APIs and OAuth 2.0 authentication. 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.remoteaccess_define.htm &type=5