B2C-Solution-Architect Questions and Answers

The shipping method name and description can be missing when order confirmation emails are triggered for languages other than US English, while other translated content appears correctly, for the following possible reasons:

• The name and description for the shipping method are not set up correctly in B2C Commerce or Service Cloud for the requested locale. The shipping method name and description are stored as attributes in B2C Commerce or Service Cloud, and they need to be translated and localized for each supported locale. If the translation or localization is missing or incorrect, the order confirmation email may not display them properly.
• The ShippingMethods data extension is missing the label and description field for the corresponding locale. The ShippingMethods data extension is a table in Marketing Cloud that stores the shipping method information for each locale. It has fields for label and description that need to match the values in B2C Commerce or Service Cloud. If the fields are missing or mismatched for a certain locale, the order confirmation email may not display them properly.

Option B is incorrect because the subscriber in Marketing Cloud does not need to have a preferred locale set. The locale can be determined by the order data or the storefront language. Option C is incorrect because the locale can be set correctly in the email template using AMPscript or SSJS variables. References:

• https://help.salesforce.com/s/articleView?id=sf.mc_co_transactional_messaging.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_order_confirmation_email.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_shipping_methods_data_extension.htm&type=5

• A is correct because the Service Cloud Connector only works with registered B2C Commerce customer accounts and does not support guests or anonymous storefront shoppers. The connector uses the customer ID to link the Service Cloud contact with the B2C Commerce customer profile.
• B is incorrect because the Service Cloud Connector supports both SOAP and REST services for data synchronization between Service Cloud and B2C Commerce.
• C is incorrect because the Service Cloud Connector requires B2C Commerce to be registered as a remote site in Service Cloud regardless of the geographic region. This is to allow outbound messages from Service Cloud to B2C Commerce.
• D is incorrect because the Service Cloud Connector requires a dedicated Integration User with administrative rights in both Service Cloud and B2C Commerce. This user is used to authenticate and authorize the data synchronization between the two systems.

References:

• : https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorOverview.html
• : https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorDataSynchronization.html
• : https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorSetup.html
• : https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/ServiceCloud/ServiceCloudConnectorUserSetup.html

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.

To enable transactional messages from B2C Commerce to Marketing Cloud, you need to configure API integration credentials in Marketing Cloud, which will generate an authentication token and a REST endpoint for your account. Then, you need to implement a server-side API callout in B2C Commerce for each of the required emails, which will use the authentication token and the REST endpoint to send the email data to Marketing Cloud. Finally, you need to configure a Transactional Messaging API in Marketing Cloud, which will allow you to create and manage transactional messages using REST API calls. You also need to use a transactional send classification for each of the required emails, which will indicate that the email is not subject to unsubscribe rules.

References:

• [API Integration]
• [Transactional Messaging API]
• [Send Classifications]

This flow allows the customer to purchase online and pick up their order in the store using B2C Commerce, Salesforce Order Management, and Service Cloud. B2C Commerce exports the order to Salesforce Order Management, which handles the order orchestration and fulfillment. Salesforce Order Management passes the order information to Service Cloud, which can be used by the store staff to check the order details and availability. Once the order is picked up by the customer, Service Cloud updates the final status in Salesforce Order Management, which can trigger notifications or invoices. References: https://help.salesforce.com/s/articleView?id=sf.order_mgmt_overview.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.order_mgmt_service_cloud_integration.htm &type=5

A. Fixing the data quality issues in Service Cloud before migrating to Marketing Cloud can help avoid duplicate or incomplete contacts in Marketing Cloud, which can affect the contact count, billing, and personalization. Data quality issues can be fixed by using tools such as Data Loader, Duplicate Management, or ETL tools. C. Mapping Contact, Lead, and Account objects within Marketing Cloud can help enable personalization by using data from Service Cloud in email content or journeys. Mapping can be done by using Marketing Cloud Connect or Customer 360 Data Manager. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_sync_leads_and_contacts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_map_salesforce_objects.htm &type=5

B. Email tracking for messages sent from the ecommerce site will not be replicated via Marketing Cloud Connect and therefore will not be visible to the Service Agents. Marketing Cloud Connect can only track email sends that are initiated from Marketing Cloud or Salesforce CRM, not from an external ecommerce site. This means that the Service Agents will not have a complete view of the customer’s email interactions or preferences. D. Contacts may be duplicated in Marketing Cloud during the transition phase, and additional work may be required to merge identities at a later date. Marketing Cloud Connect uses the Salesforce Contact ID or Lead ID as the contact key in Marketing Cloud, which is a unique identifier for each contact or lead. If the existing ecommerce site integration uses a different identifier, such as email address or customer ID, then it may create duplicate contacts in Marketing Cloud when syncing with Service Cloud. This can affect the contact count, billing, and personalization in Marketing Cloud. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_sync_leads_and_contacts.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5

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.

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

A custom solution in Service Cloud can use Apex or Lightning Web Components to call the B2C Commerce APIs and update the customer records in B2C Commerce. This option provides the most flexibility and control over the integration logic and error handling. Platform events, outbound messages, and change data capture are not supported by B2C Commerce out of the box, so they would require additional development or middleware to handle them. References:

• https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_rest_code_sample_basic.htm
• https://developer.salesforce.com/docs/component-library/documentation/en/lwc/lwc.data_wire_example
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/index.jsp?topic=%2Fcom.demandware.dochelp%2FOCAPI%2Fcurrent%2Fusage%2FRESTAPIs.html

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

• Option A is correct because running load testing in B2C Commerce pre-launch against the production instance connected to a full copy sandbox in Service Cloud is a recommended practice to ensure that the multi-cloud solution can handle the expected traffic and transactions without compromising performance or functionality.
• Option C is correct because using a single Marketing Cloud instance to connect to multiple Service Cloud environments using Marketing Cloud Connect for each business unit is a recommended practice to enable data synchronization and integration between the clouds without duplicating data or creating conflicts.
• Option B is incorrect because using Marketing Cloud business units as testing environments is not a recommended practice, as it may cause data quality issues, security risks, and configuration challenges. Marketing Cloud business units should be used for segmentation and personalization purposes, not for testing or development.
• Option D is incorrect because using a Service Cloud partial copy sandbox to provide better performance than a developer pro sandbox as well as a normal sandbox is not a valid statement, as partial copy sandboxes have the same performance characteristics as developer pro sandboxes and normal sandboxes. The main difference between partial copy sandboxes and other types of sandboxes is the amount of data they can store.

References:

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

This answer is correct because it is the primary system that should be used for all authentication between B2C Commerce site and Experience Cloud site. Salesforce Identity can act as an identity provider (IDP) for both B2C Commerce and Experience Cloud, and it can provide a single login and data experience between the two sites. Salesforce Identity can also store customer profile data in a single place and sync it across systems. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm &type=5

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

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/marketing-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

• Option B is correct because orders should be mapped from B2C Commerce to Marketing Cloud in order to meet the company’s needs. Orders contain purchasing data such as order number, order date, order total, order status, and order items, which can be used for marketing purposes such as segmentation, personalization, and reporting.
• Option C is correct because customer should be mapped from B2C Commerce to Marketing Cloud in order to meet the company’s needs. Customer contains subscriber data such as customer ID, email address, first name, last name, and phone number, which can be used for marketing purposes such as identification, communication, and targeting.
• Option A is incorrect because contact is not an object from B2C Commerce, but rather an object from Service Cloud or Sales Cloud. Contact contains customer data such as name, email address, phone number, and account ID, which can be used for marketing purposes if integrated with Marketing Cloud via Marketing Cloud Connect.
• Option D is incorrect because profile is not an object from B2C Commerce, but rather an object from Experience Cloud or Sales Cloud. Profile contains user data such as username, password, role, and permissions, which can be used for authentication and authorization purposes if integrated with Marketing Cloud via Salesforce Identity or Marketing Cloud Connect.

References:

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

Digital Engagement is a set of features in Service Cloud that enables agents to communicate with customers using social messaging channels such as Facebook, WhatsApp, and SMS. To justify the recommendation of implementing Digital Engagement, a Solution Architect can use the following reasons:

• Mobile Connect lacks integration with the service agent console without Digital Engagement. Mobile Connect is a feature in Marketing Cloud that allows sending and receiving SMS messages. However, without Digital Engagement, Mobile Connect messages cannot be handled by Service Cloud agents in the service console or omnichannel routing.
• Social Studio does not support 1:1 messaging on the apps listed in the scenario. Social Studio is a feature in Marketing Cloud that allows listening and engaging with customers on social media platforms. However, Social Studio does not support direct messaging on Facebook or WhatsApp, which are popular social messaging channels.

Option B is incorrect because Mobile Connect supports outbound messaging in more than 200 countries. Option D is incorrect because Social Studio can respond to public posts or comments on social media platforms. References:

• https://help.salesforce.com/s/articleView?id=sf.service_digital_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_moc_mobileconnect.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_moc_supported_countries.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_ss_social_studio_overview.htm&type=5

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

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

C. Case routing can be configured by configuring Service Cloud’s omni-channel routing feature to route cases to support teams based on the tier level of the customer submitting the case and the availability of agents supporting each tier level. This can help accomplish the goal by ensuring that cases are assigned to the most qualified and available agents based on predefined criteria and rules. D. Tier levels must be calculated regularly and attributed to Contact records in Service Cloud so that the tier level can be leveraged by Service Cloud’s omni-channel routing feature and synchronized back to B2C Commerce and Marketing Cloud. This can help accomplish the goal by maintaining consistent and updated customer data across different systems and platforms. References:

• https://help.salesforce.com/s/articleView?id=sf.service_presence_omnichannel_routing.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_implement_marketing_cloud_connect.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_integration.htm&type=5

B2C Commerce and Service Cloud are not natively integrated and require custom development to enable data synchronization and API access between them. B2C Commerce and Marketing Cloud also require custom development to enable API access for customer engagement scenarios. References: https://help.salesforce.com/s/articleView?id=sf.b2c_service_cloud_connector_overview.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

This approach allows the company to have a separate business unit for each B2C Commerce storefront, which provides data segregation and customization for each market. Each business unit can have its own Marketing Cloud product catalog, which is a data extension that contains product information for generating product recommendations using Einstein. D. This approach allows the company to implement abandoned cart using Marketing Cloud’s Behavioral Trigger feature, which can track customer behavior on the B2C Commerce storefront and trigger an email journey based on predefined rules. The abandonment journey can include product recommendations based on the products left in the cart. The B2C Commerce storefront must also be extended to re-create the customer’s shopping cart with abandoned products using a link or button in the email. References: https://help.salesforce.com/s/articleView?id=sf.mc_pb_product_catalog.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_pb_behavioral_triggers.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/abandoned-cart

A Marketing Cloud sandbox is a separate instance that can be used for testing and development purposes. It can be connected to multiple Service Cloud sandboxes using Marketing Cloud Connect. This setup allows data segregation and cost efficiency, as opposed to creating multiple Marketing Cloud instances or business units. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_sandbox.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_connect_multiple_salesforce_orgs.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/

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

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

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

Service Cloud and Marketing Cloud are considered authoritative systems for consent and compliance preferences, as well as primary person attributes such as name, address, birthday, phone, and email. Service Cloud is the system of record for customer service interactions and case management, and it can store customer consent and preferences for different channels and purposes. Marketing Cloud is the system of record for customer engagement and marketing campaigns, and it can store customer consent and preferences for email, SMS, push notifications, and other channels. B2C Commerce is not an authoritative system for consent and compliance preferences, as it does not store them natively. It can store some primary person attributes such as name, address, phone, and email, but they may not be the most up-to-date or accurate. Experience Cloud is not an authoritative system for consent and compliance preferences, as it relies on other systems to store them. It can store some primary person attributes such as name, email, and birthday, but they may not be the most up-to-date or accurate. References:

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

B. Service Cloud should be implemented before Marketing Cloud to ensure that the Salesforce Contact IDs can be used in Marketing Cloud as unique identifiers. This allows for a consistent and unified view of the customer across the Salesforce products and avoids duplicate contacts in Marketing Cloud. C. Customer data from B2C Commerce and the legacy CRM should be deduplicated before being imported into Service Cloud. This ensures that there are no duplicate contacts in Service Cloud that could cause data quality issues or conflicts when syncing with Marketing Cloud. D. Custom development work is required to connect B2C Commerce to Marketing Cloud and use the Salesforce Contact ID. This involves creating a service definition in B2C Commerce that points to Marketing Cloud’s REST API and passing the Salesforce Contact ID as the contact key when triggering journeys or updating contact data. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

Documenting the data type and size constraints in each system is important to ensure that the entities are mapped correctly and that no data is lost or corrupted during the integration process. Mapping B2C Commerce profile to Salesforce Platform Contact and to Marketing Cloud Contact is a best practice for cross-cloud data mapping design, as it allows for a consistent view of the customer across all platforms and enables cross-channel marketing and service capabilities.

Working with stakeholders to create a customer journey map that improves conversions and running reports on the value of cart items and time since the last activity are two tactics that a Solution Architect could recommend to understand how to optimize the checkout process. A customer journey map is a visual representation of the steps and interactions that a customer goes through when engaging with a company or brand. It can help identify pain points, opportunities, and best practices for improving conversions. Running reports on the value of cart items and time since the last activity can help analyze the shopping behavior and preferences of customers, as well as identify potential reasons for cart abandonment.

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.

This sequence of events ensures that all customer data is integrated across the systems and that Marketing Cloud uses Service Cloud Contact IDs as the subscriber key. This allows for a consistent and unified view of the customer across the Salesforce products. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect.htm &type=5

• 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

Salesforce CMS is a product that allows creating, managing, and delivering content across different channels and devices. Salesforce CMS can create common content that can be leveraged across customer touchpoints, such as websites, portals, apps, etc. The products that can leverage Salesforce content without custom integration are:

• Experience Cloud: Experience Cloud is a product that allows creating branded websites and portals for customers, partners, or employees. Experience Cloud can leverage Salesforce content without custom integration, by using CMS Connect or CMS Collections to display content from Salesforce CMS on Experience Cloud pages.
• B2C Commerce: B2C Commerce is a product that allows creating ecommerce websites and storefronts for online shopping. B2C Commerce can leverage Salesforce content without custom integration, by using CMS Connect or CMS Collections to display content from Salesforce CMS on B2C Commerce pages.

Option C is incorrect because Marketing Cloud is a product that allows creating and delivering personalized marketing campaigns across different channels and devices. Marketing Cloud cannot leverage Salesforce content without custom integration, as it requires using APIs or custom code to access content from Salesforce CMS. Option D is incorrect because Service Cloud is a product that allows managing customer service interactions across different channels and systems. Service Cloud cannot leverage Salesforce content without custom integration, as it requires using APIs or custom code to access content from Salesforce CMS. References:

• https://help.salesforce.com/s/articleView?id=sf.cms_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.networks_cms_connect.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.networks_cms_collections.htm&type=5

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

This solution allows the company to send the electronic receipt in near real time using the Marketing Cloud Transactional Messaging API, which can handle high-volume and time-sensitive messages. The POS system already has the Service Cloud Contact ID for the customer, so there is no need to make an extra API call to Service Cloud to fetch it. The Service Cloud Contact ID can be passed as the Marketing Cloud Contact Key to ensure data consistency across the systems. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5

This answer is correct because a reference architecture is an example artifact that can be used to ensure the company understands the systems involved in the solution. A reference architecture provides a high-level overview of the components, integrations, and interactions of the solution, which can help the company visualize how the solution will work and what systems are required. References: https://architect.salesforce.com/diagrams/framework/reference-architecture

• C is correct because Marketing Cloud Connect uses the SOAP API to integrate multiple business units in Marketing Cloud with Salesforce core orgs. The SOAP API enables data synchronization, triggered sends, journey builder integrations, and tracking data.
• A is incorrect because the Tooling API is used to create and modify metadata in Salesforce core orgs, such as custom objects, fields, workflows, etc. It is not used for Marketing Cloud Connect integration.
• B is incorrect because the REST API is used to access resources in Marketing Cloud, such as contacts, content, campaigns, etc. It is not used for Marketing Cloud Connect integration.
• D is incorrect because the Streaming API is used to receive notifications of data changes in Salesforce core orgs, such as record updates, deletes, etc. It is not used for Marketing Cloud Connect integration.

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.api_tooling.meta/api_tooling/intro_api_tooling.htm
• : https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm
• : https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/intro_stream.htm