Free Practice Questions for Salesforce B2C-Solution-Architect Exam

Salesforce Connect is a feature that allows accessing and integrating external data from various sources without copying or storing it in Salesforce. Salesforce Connect uses external objects and external data sources to create a virtual data model that can be used in Salesforce applications and tools. The justifications for using Salesforce Connect in this solution are:

Need access to all external data in near real-time. Salesforce Connect allows accessing external data from ERP or other systems in near real-time, without any delays or synchronization issues. This ensures that the data is always up-to-date and consistent across systems.

The external data is changing frequently. Salesforce Connect allows reflecting any changes or updates made to the external data in ERP or other systems immediately in Salesforce, without requiring any manual intervention or batch processes. This ensures that the data is always accurate and reliable across systems.

Need real-time access to a small fraction of external data. Salesforce Connect allows accessing only a small fraction of external data that is relevant and needed for a specific use case, such as displaying customer order history or details. This reduces network overhead and improves performance.

Option A is incorrect because accessing external data using workflows and triggers is not possible or supported with Salesforce Connect. Option C is incorrect because integrating external data without writing custom code is not a justification for using Salesforce Connect, as it may require some custom code or configuration depending on the data source and use case. References:

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

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

A. Enabling customer service agents to enroll customers in an Abandoned Cart Journey in Marketing Cloud if an interaction does not result in the processing of an order can help increase checkouts and decrease the time from adding items to completing a checkout by sending targeted and personalized messages to customers who have left items in their carts without purchasing them. This can help re-engage customers, remind them of their cart contents, and encourage them to complete their orders. D. Monitoring the cart items and time since it has been active in B2C Commerce and sending a reminder and checkout incentive 18 hours after the cart was last modified can help increase checkouts and decrease the time from adding items to completing a checkout by leveraging customer behavior data, timing, and urgency to motivate customers to buy their items before they are out of stock or unavailable. This can help reduce cart abandonment, increase conversion rates, and boost customer loyalty. References:

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

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

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.

B. Extending the B2C Commerce storefront to trigger emails via Marketing Cloud’s journey REST APIs allows the customer to send triggered emails based on customer behavior on the storefront, such as signing up, placing an order, or abandoning a cart. The REST APIs can also pass data attributes, such as order details or personalization information, to Marketing Cloud. D. Copying and pasting the Collect Script within the head or body in the website template allows the customer to track customer behavior on the storefront using Marketing Cloud’s Web & Mobile Analytics feature. The Collect Script can also capture customer attributes, such as email address or contact key, and send them to Marketing Cloud. E. Updating order.export custom object in B2C Commerce with the Marketing Cloud object data extension allows the customer to map order data from B2C Commerce to Marketing Cloud using a point-and-click configuration in Business Manager. This enables order data synchronization between B2C Commerce and Marketing Cloud. References: https://developer.salesforce.com/docs/commerce/sfra/mar keting-cloud/marketing-cloud-integration https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce.com/s/articleView?id=sf.mc_pb_web_and_mobile_analytics.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_with_commerce_cloud.htm &type=5

Shield is a set of security tools that can help protect sensitive data across Salesforce products, including encryption, auditing, and monitoring. Shield can help comply with data privacy and security regulations that require geo-fencing or data residency. Salesforce Connect is a feature that allows accessing data from external sources without storing it in Salesforce. Salesforce Connect can help comply with data privacy and security regulations that restrict cross-border data transfers or require data localization. References: https://www.salesforce.com/products/platform/products/shield/ https://help.salesforce.com/s/articleView?id=sf.data_source_connect.htm &type=5

The Storefront Reference Architecture (SFRA) is a modern, mobile-first framework for building B2C Commerce storefronts that are fast, responsive, and scalable. Marketing Cloud is a powerful platform for customer engagement that can integrate with B2C Commerce and provide personalized, cross-channel marketing campaigns. References: https://developer.salesforce.com/docs/commerce/sfra/overview/about-sfra https://www.salesforce.com/products/marketing-cloud/overview/

These answers are correct because they are ways to model a customer across all three systems using the Marketing Cloud Subscriber Key and Service Cloud as sources of truth. The Marketing Cloud Subscriber Key can be sent to Service Cloud and B2C Commerce to be held for reference, which can help link customer records across systems and enable cross-channel marketing and service. Service Cloud can be used as system of record for customer data and consent preferences across all channels, which can help comply with data privacy laws and provide a consistent customer experience. References: https://help.salesforce.com/s/articleView? id=sf.mc_co_marketing_cloud_connect_best_practices.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm &type=5

API-led connectivity is a method of connecting data to applications through reusable and purposeful APIs. MuleSoft Accelerator for Salesforce B2C Commerce Cloud is a solution that uses API-led connectivity to integrate B2C Commerce with other systems such as PIM, ERP, or Service Cloud. The benefits of API-led connectivity while implementing the MuleSoft accelerator for B2C Commerce are:

It enables self-service and an increase in productivity through reusable microservices and APIs. API-led connectivity allows developers to create modular and reusable microservices and APIs that can be easily discovered, accessed, and composed by other developers or business users. This reduces duplication of effort, increases agility, and accelerates time to market.

It enforces a distributed approach and allows for the creation of Experience APIs, Data APIs, and System APIs. API-led connectivity follows a distributed approach that decouples data sources from data consumers, enabling greater scalability, flexibility, and security. It also allows for the creation of three layers of APIs: Experience APIs that tailor data to specific channels or devices, Data APIs that orchestrate data from multiple sources, and System APIs that connect to core systems of record.

Option B is incorrect because API-led connectivity does not let the business quickly integrate different systems without involving IT. It requires IT to design, build, and manage the APIs that enable integration. Option C is incorrect because API-led connectivity does not offer a template-driven approach for development. It offers a methodology and a framework for developing APIs based on best practices. References:

https://www.mulesoft.com/resources/api/what-is-api-led-connectivity

https://www.mulesoft.com/exchange/org.mule.examples/mulesoft-accelerator-for-salesforce-b2c-commerce-cloud/

Service Cloud contact should be considered the authoritative record for consent and compliance preferences, as well as primary person attributes such as name, address, birthday, phone, and email. Service Cloud contact is the core entity that represents a person across multiple Salesforce clouds and can store and manage the customer’s consent and compliance preferences using features like Individual object, Data Protection and Privacy, and Consent Management. The other systems can use Service Cloud contact as the master record and sync or update the customer data accordingly.

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