B2C-Solution-Architect Salesforce Certified B2C Solution Architect (SU24) Questions and Answers

Migrating the Subscriber Key in Marketing Cloud to be the Service Cloud Contact or Person Account ID allows for a consistent identification of customers across both systems. This also enables data synchronization and cross-cloud features via Marketing Cloud Connect. Using Service Cloud as a central point to hold unique identifiers from all systems, including B2C Commerce CustomerNo and Customer ID, allows for a single source of truth for customer data and facilitates data integration and reporting across systems. Customer 360 Data Manager is not yet available for B2C Commerce, so option B is not possible. Sending the Marketing Cloud Subscriber Key to Service Cloud and B2C Commerce is not necessary if option A is implemented, so option D is not optimal. References:

• https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_best_practices.htm&type=5
• https://www.salesforce.com/in/blog/2020/04/what-is-salesforce-customer-360.html

This answer is correct because Salesforce Connect can be used to display external data in Salesforce without copying or storing it. Salesforce Connect uses external objects to access data from an external system via an adapter. This way, the order data from the ERP system can be displayed in Service Cloud as read-only records without consuming additional storage space. References: https://help.salesforce.com/s/articleView?id=sf.datacloud_connect.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 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

A standard data extension is a type of data extension that can store any type of data in Marketing Cloud, including order and product records from B2C Commerce. A standard data extension can be created manually or imported from an external source, such as B2C Commerce. A standard data extension can also be used for segmentation, personalization, and reporting in Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_es_data_extensions.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_data_integration_with_commerce_cloud.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.

Customer 360 Data Manager is a platform service that enables companies to connect customer data across Salesforce apps and create a unified customer profile. It uses advanced matching algorithms to identify and link customer records from different systems based on common attributes such as name, email, phone, address, etc. It also assigns a consistent Global Party ID to each customer record, which serves as a unique identifier across systems. Customer 360 Data Manager can be used across multiple brands within a single merchant environment by creating separate data spaces for each brand. Option B is incorrect because Customer 360 Data Manager can relate the IDs between systems without additional custom development. Option C is incorrect because Customer 360 Data Manager supports multiple brands within a single merchant environment. Option D is incorrect because B2C Commerce, Service Cloud, and Marketing Cloud do not automatically use a common core Customer Profile managed by Customer 360 Data Manager; they need to be connected and configured via Customer 360 Data Manager. References:

• https://www.salesforce.com/in/blog/2020/04/what-is-salesforce-customer-360.html
• https://help.salesforce.com/s/articleView?id=sf.c360_overview.htm&type=5

Experience Cloud is a product that allows creating and managing digital experiences for customers, partners, employees, and communities. Experience Cloud can be integrated with external payment gateways and Pardot to offer secure and personalized experiences for members who want to set up recurring donations. To increase security for their existing users, a Solution Architect can recommend the following options:

• Implement high-assurance requirements for Experience Cloud profiles. High-assurance requirements are settings that define the level of security and identity verification needed for users to access certain pages or features in Experience Cloud. High-assurance requirements can help prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.
• Add a login flow that defines the scope of user access authorized by authentication providers. A login flow is a process that allows customizing the user login experience in Experience Cloud using various actions, such as collecting information, displaying messages, updating records, etc. A login flow can help define the scope of user access authorized by authentication providers, such as social media accounts or SAML-based identity providers. This can help limit or restrict the access of users based on their authentication method or credentials.
• Develop login flows to change the user’s session security level to initiate third-party identity verification. A session security level is a setting that determines the level of security and identity verification required for a user’s session in Experience Cloud. A session security level can be changed using login flows to initiate third-party identity verification, such as SMS verification, email verification, biometric verification, etc. This can help enhance the security and trust of the user’s session and prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.

Option C is incorrect because replacing Pardot with Marketing Cloud to implement SMS for multi-factor authentication is not a valid or feasible option to increase security for their existing users. Pardot is a product that allows creating and managing B2B marketing campaigns and activities, such as email marketing, lead generation, lead nurturing, etc. Marketing Cloud is a product that allows creating and managing B2C marketing campaigns and activities, such as email marketing, mobile marketing, social media marketing, etc. Replacing Pardot with Marketing Cloud would not only be costly and complex, but also unnecessary and irrelevant for their use case of setting up recurring donations. Moreover, implementing SMS for multi-factor authentication does not require replacing Pardot with Marketing Cloud, as it can be done using other methods or tools, such as login flows or third-party identity verification services. Option D is incorrect because maintaining GAuth tokens for existing Experience Cloud profiles is not an option or a way to increase security for their existing users. GAuth tokens are tokens that are used by Google Authenticator, an app that generates one-time passwords for two-factor authentication. GAuth tokens are not related to Experience Cloud profiles or their security settings. References:

• https://help.salesforce.com/s/articleView?id=sf.networks_security.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.networks_login_flow_examples.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.networks_session_security_levels.htm&type=5

The B2C Commerce to 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. When introducing the Service Cloud Connector into an existing Salesforce Org, the following functionality considerations should be aware of:

• In order to implement the Service Cloud Connector it is necessary to enable Person Accounts, a change which cannot be reverted once implemented. 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. Enabling Person Accounts is an irreversible change that affects the entire Salesforce Org and may have implications for other features or customizations.
• The Service Cloud Connector is distributed as a managed package that can be extended to meet client-specific needs but with core functionality that cannot be altered. A managed package is a collection of application components that can be installed from AppExchange or other sources. The Service Cloud Connector is a managed package that provides core functionality for integrating B2C Commerce and Service Cloud. The core functionality cannot be modified or deleted, but it can be extended or customized using Apex code, Visualforce pages, or Lightning components.

Option C is incorrect because the Service Cloud Connector does not natively support accounts and contacts, households, and multi-brand customer models. It only supports person accounts as a customer model by default. Option D is incorrect because the Service Cloud Connector provides a collection of Lightning components that display customer and order information within Service Cloud, which do not need to be customized or deployed by a developer. 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.distribution_installing_packages.htm&type=5

• Option B is correct because Marketing Cloud should implement a second business unit and provide each B2C Commerce storefront with its own Marketing Cloud business unit. This is a recommended practice to enable multi-brand marketing campaigns and segmentation based on different storefronts and customer profiles.
• Option C is correct because Marketing Cloud must undergo a subscriber key migration with Salesforce Professional Services and select a subscriber key that aligns with Salesforce multi-cloud architecture best practices. This is a recommended practice to enable data integration and identity resolution across multiple Salesforce clouds using Customer 360 Data Manager. Email address is not a suitable subscriber key for multi-cloud scenarios, as it may change over time or be shared by multiple customers.
• Option A is incorrect because Marketing Cloud should not serve as the Salesforce primary for customer profiles and leverage customer email addresses as a multi-cloud customer identifier. This is not a recommended practice, as it would create data quality issues, security risks, and integration challenges across multiple Salesforce clouds. Customer email addresses are also not suitable as a multi-cloud customer identifier, as they may change over time or be shared by multiple customers.
• Option D is incorrect because B2C Commerce should not integrate with Marketing Cloud and create a Marketing Cloud Contact when a B2C Commerce customer registers or places an order via the storefront. This is not a recommended practice, as it would create data duplication, synchronization issues, and performance impacts across multiple Salesforce clouds. B2C Commerce should integrate with Service Cloud or Customer 360 Data Manager to create or update customer records based on their actions on the storefront.

References:

• [Get Started with B2C Solution Architect Cert Prep - Trailhead]
• [Certification - B2C Solution Architect - Trailhead]
• [B2C Solution Architect Certification Guide | Salesforce Ben]

These answers are correct 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

Product Catalogs are a type of data extension that contain product information for generating product recommendations using Einstein in Marketing Cloud. Product Catalogs can be configured natively to sync from B2C Commerce to Marketing Cloud using a point and click configuration in the Marketing Cloud Business Manager. References: https://help.salesforce.com/s/articleView?id=sf.mc_pb_product_catalog.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

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.

A. The Contact Data Portability report in Marketing Cloud is a feature that allows creating a report containing subscriber data related to a single contact, such as email address, name, phone number, preferences, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. B. The Customer Data Snapshots report in Commerce Cloud is a feature that allows creating a report containing purchaser data related to a single customer, such as order history, payment methods, addresses, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. References: https://help.salesforce.com/s/articleView?id=sf.mc_overview_contact_data_portability.htm &type=5 https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/admin/b2c_customer_data_snapshots.html

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

The Journey Membership Lightning component is a pre-built component that displays the journeys that a contact is in and their status in each journey. It can be added to the Contact Page Layout in Service Cloud using the Marketing Cloud Connect Managed Package, which enables integration between Service Cloud and Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_journey_membership_lightning_component.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect.htm &type=5

• 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

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

Bulk API is a feature of Data Loader that allows loading large amounts of data into Salesforce faster and more efficiently. Bulk API uses asynchronous processing to handle data in batches, which reduces network overhead and improves performance. Bulk API is suitable for loading data files with more than 20,000 records or larger than 10 MB. The export file has more than 2 million records, so Bulk API should be used to load this data back into Salesforce faster. References:

• https://help.salesforce.com/s/articleView?id=sf.data_loader_bulk.htm&type=5
• https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm

• B is correct because Marketing Cloud can be used for customer segmentation based on VIP status and cart abandonment behavior. B2C Commerce can be used for creation of coupon codes using promotion rules and coupon code restrictions. B2C Commerce and Marketing Cloud functionalities can be used to send abandoned cart emails using the Marketing Cloud Connector cartridge and the Abandoned Cart Journey template. Marketing Cloud can track email open and forward count using tracking metrics.
• A is incorrect because Service Cloud is not used for customer segmentation or creation of coupon codes. Service Cloud is used for customer service and case management.
• C is incorrect because B2C Commerce is not used for customer segmentation or creation of coupon codes. B2C Commerce is used for online shopping and order management.
• D is incorrect because Tableau CRM is not used to track email open and forward count. Tableau CRM is used for data analysis and visualization.

References:

• : https://help.salesforce.com/s/articleView?id=sf.mc_co_create_audience_segment.htm&type=5
• : https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/coupons/b2c_creating_coupon_codes.html
• : https://help.salesforce.com/s/articleView?id=sf.mc_co_abandoned_cart_journey.htm&type=5
• : https://help.salesforce.com/s/articleView?id=sf.mc_es_email_tracking_metrics.htm&type=5

Queues and Assignment rules are features of Service Cloud that allow incoming support cases to be automatically routed to the correct team or agent based on predefined criteria, such as customer purchases, case origin, or case priority.

A connected B2C Solution approach is an approach that allows integrating B2C Commerce and Service Cloud to provide a seamless and omnichannel experience for customers across different touchpoints. A connected B2C Solution approach can provide various benefits, such as increased customer satisfaction, loyalty, retention, and revenue. To convince the company to shift to a connected B2C Solution approach, a Solution Architect should say the following:

• Agents will have easy access to customer data to provide a better service experience when customers call in. By integrating B2C Commerce and Service Cloud using features such as Service Cloud Connector or Salesforce Order Management, agents will be able to access customer and order information from B2C Commerce directly in Service Console without switching between multiple systems. This will enable agents to answer customer questions more quickly and accurately, resolve issues more efficiently, and offer personalized recommendations or solutions.

Option B is incorrect because agents will not have a better interface using Service Cloud and B2C Commerce with Heroku. Heroku is a platform that allows building, running, and scaling custom web applications using various languages and frameworks. Heroku is not directly related to creating a connected B2C Solution approach, although it can be used to extend or customize the functionality of B2C Commerce or Service Cloud. Option C is incorrect because agents cannot utilize SSO to launch an ‘Order on Behalf of’ storefront experience within the B2C Commerce UI. SSO is a feature that allows users to log in to multiple applications or systems with the same credentials. SSO does not enable launching an ‘Order on Behalf of’ storefront experience within the B2C Commerce UI, which is a feature that allows agents to create orders on behalf of customers using the storefront login. To enable this feature, the company needs to use Service Cloud Connector or Salesforce Order Management to integrate B2C Commerce and Service Cloud. Option D is incorrect because agents’ success rates will not be better measured after helping the company define ROI KPIs together. Although this is a possible benefit of shifting to a connected B2C Solution approach, it is not the most convincing or compelling one for the company’s situation. The company’s main pain point is the lack of systems and access to customer and order data, which affects their service quality and customer satisfaction. Therefore, the most convincing argument for shifting to a connected B2C Solution approach is how it can improve the service experience for both agents and customers by providing easy access to customer data. References:

• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_overview.htm&type=5
• https://www.salesforce.com/products/commerce-cloud/ecommerce/order-management/
• https://help.salesforce.com/s/articleView?id=sf.sso_about.htm&type=5

• A is correct because integrating product, order, and customer data feeds into Marketing Cloud Data Extensions is a prerequisite for enabling an Abandoned Cart Journey. Data Extensions are tables that store data in Marketing Cloud and can be used to define audience segments and personalize messages.
• D is correct because implementing the Marketing Cloud collect.js through the storefront by using the Connector’s reference implementation is a prerequisite for enabling an Abandoned Cart Journey. The collect.js script tracks customer behavior on the storefront and sends data to Marketing Cloud using the Connector cartridge.
• B is incorrect because integrating product, order, and customer data feeds into Service Cloud objects is not needed for enabling an Abandoned Cart Journey. Service Cloud objects are used to store data in Service Cloud and can be used to manage customer service cases and interactions.
• C is incorrect because using Mulesoft to bring order and customer data feeds from B2C Commerce to Marketing Cloud is not needed for enabling an Abandoned Cart Journey. Mulesoft is a platform that provides integration solutions for various systems and applications.

References:

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

Marketing Cloud provides both REST and SOAP APIs for integrating with other systems, including Service Cloud. Both APIs can be used to perform various operations such as creating, updating, or deleting data objects, triggering messages, retrieving tracking data, and more. The REST API uses JSON request and response bodies, while the SOAP API uses XML request and response bodies. The choice of API depends on the use case, preference, and compatibility of the systems involved. References:

• https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm
• https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-getting-started.meta/mc-getting-started/get-started-with-marketing-cloud-apis.htm

Identity is a feature that allows managing user authentication and access across different applications and 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 the social 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 it does 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 allows creating 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

Enabling Collect Tracking within Marketing Cloud Personalization Builder is the first step that a Solution Architect should do to accommodate a scalable and functional abandoned cart solution between B2C Commerce and Marketing Cloud. Collect Tracking is a feature that allows Marketing Cloud to track web analytics data from B2C Commerce using collect.js code on the storefront pages. This data can be used to create Abandoned Cart Journeys in Marketing Cloud using Einstein Web Recommendations. The other steps are not necessary or optimal for this solution.

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/

• Option D is correct because Marketing Cloud with Enterprise Communication Strategy and a single Salesforce org with Connected Campus for consolidating existing departmental orgs is the best solution to meet the university’s needs. Marketing Cloud with Enterprise Communication Strategy allows the university to create and manage personalized communications across multiple channels and audiences, while a single Salesforce org with Connected Campus enables the university to unify and streamline its data, processes, and services across different departments and colleges.
• Option A is incorrect because Marketing Cloud with multiple business units, Marketing Cloud Connect, and multiple existing Salesforce orgs is not a suitable solution for the university’s needs, as it would create data silos, integration challenges, and governance issues across different Salesforce clouds and orgs. Marketing Cloud Connect is also not necessary for the university’s communication strategy, as it is mainly used for data synchronization and integration between Marketing Cloud and Service Cloud or Sales Cloud.
• Option B is incorrect because Marketing Cloud with multiple business units and a single Salesforce org with Divisions for consolidating existing departmental orgs is not a suitable solution for the university’s needs, as it would create complexity and overhead in managing multiple business units and divisions within the same Salesforce cloud and org. Divisions are also not recommended for multi-brand or multi-department scenarios, as they are mainly used for large-scale data segmentation and reporting purposes.
• Option C is incorrect because Marketing Cloud with Enterprise Communication Strategy, Marketing Cloud Connect, and multiple existing Salesforce orgs is not a suitable solution for the university’s needs, as it would create data silos, integration challenges, and governance issues across different Salesforce clouds and orgs. Marketing Cloud Connect is also not necessary for the university’s communication strategy, as it is mainly used for data synchronization and integration between Marketing Cloud and Service Cloud or Sales Cloud.

References:

• [Get Started with B2C Solution Architect Cert Prep - Trailhead]
• [Certification - B2C Solution Architect - Trailhead]
• [B2C Solution Architect Certification Guide | Salesforce Ben]

Marketing Cloud should be the system of record for lifetime engagement tracking and history, as well as other data for personalization or segmentation, as it is the system that collects and analyzes the customer’s interactions and behaviors across multiple channels and touchpoints. Marketing Cloud can also use features like Audience Builder and Contact Builder to create unified customer profiles and segments based on various data sources3 . Service Cloud should be the system of record for storing primary attributes (name, address, birthday, phone, and email) about the customer, as it is the system 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 .

• A is correct because including functional subject matter experts and technical resources across multiple discovery workshops, grouped by business function, is a best practice for capturing requirements and ensuring alignment across different stakeholders1.
• B is correct because conducting discovery workshops and presenting the solution back to the design authority or executive stakeholders is a best practice for validating the solution and obtaining feedback and approval1.
• C is incorrect because conducting discovery workshops to create a user acceptance testing document is not the purpose of discovery workshops. User acceptance testing documents are created after the solution design is finalized and approved2.
• D is incorrect because including the customer service team to provide detailed user stories prior to the discovery workshops is not necessary. User stories are created during the discovery workshops based on the business requirements and pain points identified by the stakeholders1.

References:

• 1: https://trailhead.salesforce.com/content/learn/modules/om-salesforce-order-management/om-discovery-workshops
• 2: https://trailhead.salesforce.com/content/learn/modules/om-salesforce-order-management/om-user-acceptance-testing

• 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.

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. 

C. This implementation strategy allows the company to replace their legacy commerce system first, which is their highest priority, and then integrate it with Service Cloud to provide better customer service. By using the Service Cloud Contact ID as the Marketing Cloud Contact Key, the company can ensure a consistent and unified view of the customer across the Salesforce products when Marketing Cloud is implemented later. D. This implementation strategy allows the company to achieve a unified customer experience across all three clouds from the start, but it also requires more resources and coordination to implement all three clouds at the same time. The primary identifiers for all three clouds must be synced to ensure data consistency and avoid duplication. References: https://trailhead.salesforce.com/content/learn/modules/marketing-cloud-contact-management/understand-contacts-and-contact-model-relationships

A headless B2C Commerce approach can help solve the needs by decoupling the front-end presentation layer from the back-end commerce functionality. This can allow the company to leverage their existing content management systems and deliver consistent branding across different countries. LINK cartridges can help integrate B2C Commerce with third-party systems and services, such as payment providers, tax calculators, or social media platforms. SFRA-style development can help create a responsive and customizable storefront that follows best practices and standards. Heroku and MuleSoft can help build and connect custom applications and APIs that support the complex business logic and data flows required by the global pharmaceutical company. References:

• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_headless.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_link.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_sfra.htm&type=5
• https://www.salesforce.com/products/platform/overview/
• https://www.mulesoft.com/platform/enterprise-integration

Synchronized Data Sources are a feature that allows accessing and integrating data from Sales Cloud or Service Cloud into Marketing Cloud for use in marketing activities. Synchronized Data Sources can help automate the data synchronization process and ensure that data is consistent and up-to-date across different Salesforce platforms. To ensure the expected data is available within Marketing Cloud, a Solution Architect should utilize Synchronized Data Sources within Marketing Cloud.

B2C Commerce can trigger a Marketing Cloud post-purchase journey using the Transactional Messaging API. Journey Builder can use a Wait activity to delay the email delivery based on a fixed duration or a date attribute. Einstein Engagement Split can use AI to determine the optimal path for each customer based on their engagement behavior, such as open rate. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce.com/s/articleView?id=sf.mc_jb_wait_activity.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_jb_einstein_engagement_split.htm &type=5

This answer is correct because it aligns with the executive team’s request to see the benefits and return on investment sooner than three years. A multi-phased approach allows for incremental delivery of functionality across all clouds, which can provide value to the business and customers faster and more frequently. References: https://trailhead.salesforce.com/en/content/learn/modules/solution-design/solution-design-process

• Option A is correct because authentication credentials should be stored and managed by Experience Cloud as the system of record for this customer data. Experience Cloud acts as an identity provider (IDP) for commerce, meaning that it verifies the identity of customers who log in to ecommerce sites using their communities credentials. Experience Cloud can also leverage Salesforce Identity features to provide secure and seamless authentication across multiple Salesforce clouds and external systems.
• Option B is incorrect because address book should not be stored and managed by Experience Cloud as the system of record for this customer data. Address book is mainly used for ecommerce purposes, such as shipping and billing addresses, and it should be stored and managed by B2C Commerce as the system of record. B2C Commerce can also integrate with Experience Cloud to provide a consistent user experience across ecommerce sites and communities.

• 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 for customer 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, but rather 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 that there 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

Curating tiered experiences in Marketing Cloud allows the company to create personalized content and offers based on the loyalty level of the customers. Segmenting Journeys within CDP enables the company to use data from multiple sources to create customer segments and target them with relevant messages across channels. Creating Journeys by tiers in Marketing Cloud allows the company to design and execute customer journeys based on the loyalty program tiers and goals.

This approach allows the company to use Service Cloud for capturing and resolving tickets, which provides a better customer service experience than B2C Commerce. It also allows the company to archive resolved cases and related data into Heroku, which is a cloud platform that can store large amounts of data without hitting the platform’s governor limits. Using Salesforce Connect, the company can display the archived data back in Service Cloud without storing it in Salesforce, thus saving storage space and costs. References: https://help.salesforce.com/s/articleView?id=sf.data_source_connect.htm &type=5 https://www.heroku.com/home

Marketing Cloud and B2C Commerce are the two products that a Solution Architect should include in the architecture to meet UC’s needs. Marketing Cloud allows UC to create customer group segments using its e-commerce data and send personalized messages across channels, while adhering to the current customer’s compliance preferences for previous campaigns. B2C Commerce enables UC to cross-sell its new product categories on its online storefront and provide a seamless shopping experience for its customers.

A. A service definition in B2C Commerce is a configuration that defines how B2C Commerce communicates with an external system, such as Marketing Cloud. By creating a service definition that points to Marketing Cloud’s REST API, the company can enable B2C Commerce to call Marketing Cloud’s endpoints for various purposes, such as triggering journeys or updating contact data. D. After purchase, the company can use the B2C Commerce service definition to send redemption data to Marketing Cloud using the REST API. This data can include the coupon code, the journey ID, and the contact key. Marketing Cloud can use this data to update the contact’s journey status and stop sending reminder emails. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api