Salesforce Updated B2C-Solution-Architect Exam Questions and Answers by marlie

B2C Commerce Governance and Quotas are a set of rules and limits that apply to B2C Commerce instances to ensure the efficiency and stability of solutions built on the platform. The following considerations should be kept in mind when considering B2C Commerce Governance and Quotas:

• Object quotas status is updated with an up to 20-minute delay. Therefore, a Solution Architect must consider this delay when performing calculations related to traffic and limits. Object quotas are limits on the number of objects that can be created or stored in B2C Commerce, such as products, categories, customers, orders, etc. The object quotas status shows the current usage and remaining capacity of each object quota. However, the status is not updated in real time, but with an up to 20-minute delay. This means that the Solution Architect should account for this delay when estimating the traffic and limits for each object quota.
• If an enforced quota is exceeded, an exception is thrown, which prevents the current operation from completing. The Solution Architect should design the solution so that the exception can be caught within a customization. Enforced quotas are quotas that are strictly enforced by B2C Commerce and cannot be exceeded or changed by customers. Examples of enforced quotas are API calls per hour, script execution time, cache size, etc. If an enforced quota is exceeded, B2C Commerce throws an exception that stops the current operation from completing. This can result in errors or failures in the storefront or backend processes. The Solution Architect should design the solution so that the exception can be caught within a customization and handled gracefully.

Option B is incorrect because sandbox quotas cannot be softened by exporting them from a production instance and importing them onto a sandbox instance. Sandbox quotas are fixed and cannot be changed by customers. Option C is incorrect because the Solution Architect cannot assume that quota violations have not occurred unless a site is experiencing performance issues. Quota violations can occur without affecting the site performance, but they can still cause errors or failures in certain operations or processes. References:

• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/GovernanceOverview.html
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/ObjectQuotas.html
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/EnforcedQuotas.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 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

This option ensures that the Marketing Cloud Contact is linked to the correct Salesforce record after the Lead is converted to a Contact, and that the contact utilization is not affected by duplicate records. The other options can result in data loss, inconsistent reporting, or unnecessary complexity.

Creating Individuals within CDP and creating customer groups within B2C Commerce with the correct segments are the configurations that a Solution Architect should create to correctly identify unified profiles as individuals between CDP and B2C Commerce. Individuals are the entities that represent a person in CDP and can be created from various data sources using identity resolution rules. Customer groups are the entities that represent a segment of customers in B2C Commerce and can be created using attributes or rules. The Commerce CDP Connector allows for bi-directional synchronization of Individuals and customer groups between CDP and B2C Commerce, enabling a unified profile process.