Salesforce B2C-Solution-Architect Exam With Confidence Using Practice Dumps

The REST calls between B2C Commerce and Service Cloud are subject to API governor limits, which can affect the performance and availability of the integration. The service agent users need to have B2C Commerce permissions and access keys to log in and place orders on behalf of registered storefront shoppers. 

Marketing Cloud account hierarchy is the way of organizing Marketing Cloud accounts and business units to support different business needs and use cases. A Marketing Cloud tenant is a top-level account that contains one or more business units. A business unit is a sub-account that can have its own data, content, users, and permissions. To set up Marketing Cloud account hierarchy for a company that has ecommerce sites for three countries: Australia, New Zealand, and Singapore, a Solution Architect should recommend the following:

• Use a single Marketing Cloud tenant and map business units to each site irrespective of the realm. This option allows the company to have a centralized account that can manage all the sites across different countries and regions. It also allows the company to have separate business units for each site that can have their own data, content, users, and permissions. This way, the company can maintain consistency and compliance across all the sites, while also enabling personalization and segmentation for each site.

Option A is incorrect because using a separate Marketing Cloud tenant for each site is not necessary or advisable. It would create complexity and inefficiency in managing multiple accounts and duplicating data and content across them. It would also increase the cost and maintenance of the solution. Option B is incorrect because using a separate Marketing Cloud tenant for each realm and mapping business units to sites within each realm is not optimal or scalable. It would create inconsistency and fragmentation between the realms and limit the ability to share data and content across them. It would also increase the cost and maintenance of the solution. Option D is incorrect because using a single Marketing Cloud tenant and mapping business units to each realm is not sufficient or flexible. It would not allow the company to have separate data, content, users, and permissions for each site within a realm. It would also limit the ability to personalize and segment for each site. References:

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

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