Free Practice Questions for Salesforce B2C-Solution-Architect Exam

This option allows you to use Apex code to make HTTP requests and receive HTTP responses from an external system, such as a pricing and quotation service. You can use the @future(callout=true) annotation to make asynchronous callouts from Apex triggers or invocable methods. The other options are either not feasible or not optimal for this use case. 

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/

B is correct because B2C Commerce order management does not support complex or advanced use cases such as split shipments, backorders, partial cancellations, or returns3. Salesforce Order Management provides these capabilities out of the box or with minimal customization.

C is correct because Salesforce Order Management can be installed as a managed package in an existing Service Cloud org, which means that the existing Service Cloud implementation team can leverage their existing skills and knowledge to extend the product to meet the business needs.

E is correct because Salesforce Order Management shares the same database with Service Cloud, which eliminates the need for additional integration between the two systems. Other solutions would require building custom integration to synchronize data between different databases.

A is incorrect because Salesforce Order Management does not replace the Service Cloud Connector, which is used to synchronize data between Service Cloud and B2C Commerce. Salesforce Order Management integrates with both Service Cloud and B2C Commerce using platform events and REST APIs.

D is incorrect because Salesforce Order Management does not support synchronizing orders from one B2C Commerce realm to multiple Salesforce orgs without customization. The standard integration assumes that there is a one-to-one relationship between a B2C Commerce realm and a Salesforce org.

References:

3: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementOverview.html

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

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

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

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

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

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

Change Data Capture is an event-driven integration mechanism that allows near-real-time synchronization of Salesforce data changes with external systems. It does not impact the system performance as it uses asynchronous processing and does not require triggers or code. References: https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_intro.htm

This answer is correct because it is a recommended time to refresh the full copy sandbox. Refreshing the full copy sandbox after each major release to production can help ensure that the sandbox has the most updated data and metadata from production, which can facilitate testing and development activities. Refreshing the full copy sandbox too frequently can be costly and time-consuming, as it consumes a lot of storage space and requires data masking or anonymization. References: https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm &type=5

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

Option D is correct because B2C Commerce should be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. B2C Commerce is the first point of contact for customers who register an account before making their first purchase, and it can store and update important profile and commerce information like email, phone number, beauty preferences, and saved addresses. B2C Commerce can also integrate with Experience Cloud and Salesforce Identity to provide a consistent and secure user experience across the social community and the ecommerce site.

Option A is incorrect because Salesforce Identity should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Salesforce Identity is mainly used for authentication and identity management purposes, not for storing and updating customer profile and commerce information. Salesforce Identity can also integrate with Experience Cloud and B2C Commerce to provide a single sign-on (SSO) experience for customers across the social community and the ecommerce site.

Option B is incorrect because Address book should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Address book is not a system or an application, but rather a feature or a data element that can be stored and updated in B2C Commerce or other Salesforce clouds.

Option C is incorrect because Wishlist should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Wishlist is not a system or an application, but rather a feature or a data element that can be stored and updated in B2C Commerce or other Salesforce clouds.

References:

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

[Certification - B2C Solution Architect - Trailhead]

B2C Solution Architect Certification Guide | Salesforce Ben

An abandoned cart solution is a solution that allows sending personalized and timely email reminders to customers who have added items to their shopping cart but have not completed the purchase. An abandoned cart solution can help increase conversion rates, revenue, and customer loyalty. To implement an abandoned cart solution for their ecommerce storefront in Marketing Cloud, a Solution Architect should follow the following process:

Implement collect.js in the ecommerce storefront. Collect.js is a JavaScript code that allows tracking customer behavior and interactions on the ecommerce website, such as browsing products, adding items to cart, etc. Collect.js sends this behavioral data to Marketing Cloud for further analysis and action.

Create a behavioral trigger. A behavioral trigger is a rule that defines how to map behavioral data to a target data extension when a customer takes a particular action, such as abandoning a cart or browser session. A behavioral trigger can help automate the data flow and segmentation process based on customer behavior.

Create an email in Marketing Cloud. An email is a message that contains text, images, links, and other content that can be sent to customers via email. An email can be created using Content Builder, a tool that allows designing and managing email content in Marketing Cloud.

Create a journey. A journey is a sequence of messages and actions that are triggered by customer events or attributes. A journey can be created using Journey Builder, a tool that allows designing and managing customer journeys in Marketing Cloud.

Option A is incorrect because exporting the purchase data from B2C Commerce, importing the data into Marketing Cloud, and creating an email in Content Builder is not a sufficient or efficient process for implementing an abandoned cart solution. This process does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. Option B is incorrect because setting up Marketing Cloud Connector, creating an email in Marketing Cloud, and creating a send trigger is not a suitable or scalable process for implementing an abandoned cart solution. Marketing Cloud Connector is a feature that allows integrating Marketing Cloud with other Salesforce products, such as Sales Cloud or Service Cloud. It is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. A send trigger is a rule that defines how to send an email to customers based on certain criteria or conditions. However, a send trigger does not capture or leverage the behavioral data collected by collect.js, which is crucial for creating an effective abandoned cart solution. Option D is incorrect because setting up Einstein Recommendations, setting up Marketing Cloud Connector, and creating an email in Marketing Cloud is not a relevant or optimal process for implementing an abandoned cart solution. Einstein Recommendations is a feature that allows generating personalized product recommendations based on customer behavior and preferences. It is not directly related to creating an abandoned cart solution, although it can be used to enhance the email content with relevant recommendations. As mentioned before, Marketing Cloud Connector is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. This process also does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. References:

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

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

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

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

 Marketing Cloud with multiple business units connected to multiple existing Salesforce orgs with Marketing Cloud Connect is the option that a Solution Architect should recommend to meet the university’s needs. Marketing Cloud allows the university to create and execute personalized marketing campaigns across various channels and audiences. Multiple business units enable the university to have separate sub-accounts for each branded school or department, with different permissions, settings, and content. Multiple existing Salesforce orgs allow the university to maintain their existing finances, business processes, and strategies for each college or school. Marketing Cloud Connect enables the integration between Marketing Cloud and Salesforce orgs, allowing for data synchronization, cross-cloud reporting, and journey activation.