Free Salesforce B2C-Solution-Architect Practice Exam with Questions & Answers | Set: 4

These answers arecorrect because they are part of the solution design process that a Solution Architect should follow to ensure the right solution can be delivered. Capturing functional specifications, understanding system integrations and data sources, and identifying pain points and expected outcomes are essential steps to design a solution that meets the business needs and expectations.References:https:// trailhead.salesforce.com/en/content/learn/modules/solution-design/solution-design-process

Marketing Cloud treats leads and contacts as separate records, even if they have the same email address. This means that syncing leads from Sales Cloud to Marketing Cloud can create duplicate contacts and increase the contact count and billing. To avoid this, the marketing team should consider using contacts only or converting leads to contacts before syncing them to Marketing Cloud.References:https://help.salesforce.com/s/articleView?id=sf.mc_co_sync_leads_and_contacts.htm &type=5

Identity is a feature that allows managing user authentication and access across different applicationsand systems. Identity can be either internal or external to Salesforce, depending on where the user credentials are stored and verified. To cover NTOs identity needs, a Solution Architect should recommend the following:

• Define a user registration handler to support user provisioning and authentication via social services like Google and Facebook. A user registration handler is a class in Apex code that defines the logic for creating and updating user accounts based on information from an external identity provider. A user registration handler can support user provisioning and authentication via social services like Google and Facebook, by using OAuth 2.0 protocols and OpenID Connect standards to exchange user information and tokens between Salesforce and thesocial services.
• Leverage Salesforce Identity as the identity provider to centralize authentication for both Experience Cloud and B2C Commerce in one place. Salesforce Identity is a product that allows using Salesforce as an identity provider for other applications and systems. Salesforce Identity can centralize authentication for both Experience Cloud and B2C Commerce in one place, by using single sign-on (SSO) protocols and standards to enable users to log in to both applications with the same credentials.

Option C is incorrect because leveraging B2C Commerce as the identity provider for both Storefront and the Service Portal is not possible or advisable. B2C Commerce does not support acting as an identity provider for other applications or systems, as itdoes not support SSO protocols or standards. Option D is incorrect because using Salesforce CDP, which automatically syncs profiles and authentication information across systems, is not a valid or available option. Salesforce CDP is a product that allowscreating unified customer profiles from various data sources, but it does not sync or manage authentication information across systems. References:

• https://help.salesforce.com/s/articleView?id=sf.identity_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.identity_provider.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.sso_about.htm&type=5
• https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_interface_Auth_RegistrationHandler.htm

• 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 forcustomer 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, butrather 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 thatthere 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 answer is correct because it describes the capabilities of a B2C Commerce and Service Cloud integration with Order Management that can benefit service agents most. By sending order and transaction information to Service Cloud, service agents can have a complete view of the customer’s order history, status, and payment details, which can help them provide better service during returns, exchanges, and payments.References:https://help.salesforce.com/s/articleView?id=sf .b2c_commerce_service_cloud_integration.htm&type=5

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 B2CCommerce 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 ServiceCloud 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

• A is correct because Salesforce Order Management does not have native support for multiple distribution centers and requires either an AppExchange package or custom Apex triggers to implement fulfillment rules based on custom attributes1.

Request and reply is an integration pattern that allows a system to send a message to another system and wait for a response. This pattern is suitable for scenarios where the sender needs to receive an immediate confirmation or acknowledgment from the receiver. In this case, B2C Commerce needs to receive the order number and status from the ERP system after sending the order details. References:

• https://architect.salesforce.com/design/integration-patterns-and-practices/request-and-reply/
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementOverview.html

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 Clouduser 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 B2CCommerce 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

Salesforce Order Management is a product that allows managing orders across different channels and systems. To migrate the existing in-house order management solution to the Salesforce Order Management product, the following actions should be taken:

• Configure data extensions and triggered sends in Marketing Cloud to support transactional emails for ordering scenarios. Data extensions are tables that store data inMarketing Cloud, and triggered sends are email messages that are sent automatically based on an external event. Data extensions and triggered sends can be used to store order data and send order confirmation, shipment notification, or cancellation emailsto customers.
• Modify the Service Cloud Connector implementation to remove potentially conflicting features with the Order Management Connector. The Service Cloud Connector is a cartridge that enables integration between B2C Commerce and Service Cloud. TheOrder Management Connector is a cartridge that enables integration between B2C Commerce and Salesforce Order Management. Some features of the Service Cloud Connector, such as order history or order cancellation, may conflict with the Order Management Connector, so they should be removed or disabled.
• Integrate Salesforce Order Management to B2C Commerce for order history and user self service. This integration allows customers to view their order history and status, track their shipments, cancel their orders, or initiate returns on the B2C Commerce storefront. This integration also allows agents to view and manage orders in Service Cloud.

Option D is incorrect because migrating subscriber keys in Marketing Cloud to a new Order Management customer identifier is not necessary or recommended. Option E is incorrect because replacing the Service Cloud Connector with an Order Management Connector for B2C Commerce is not possible or advisable. References:

• https://help.salesforce.com/s/articleView?id=sf.order_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_transactional_messaging.htm&type=5
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementOverview.html
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementConnector.html