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

C. Hooks are a way to extend the existing OCAPI endpoints with custom logic and data. By using hooks, the merchant can add additional information about the custom product options and component availability to the OCAPI product endpoint, which can be consumed by Service Cloud to display the custom product experience. D. CSR Order on Behalf Of is a feature that allows a CSR to access the existing B2C Commerce storefront as a customer and perform actions on their behalf, such as making purchases or reviewing custom products. This feature can be enabled in Service Cloud using the Commerce Cloud Connector. References: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OCAPI/current/usage/Hooks.html https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/CSR/CSRorderonbehalfof.html

A. Shield and Event Monitoring Analytics App, Pardot can help meet these needs by providing enhanced security, compliance, auditing, analytics, and marketing capabilities for the insurance company. Shield can help protect sensitive data with encryption, monitor user activity with event logs, enforce data retention policies with archiving, and comply with industry regulations with field audit trails. Event Monitoring Analytics App can help analyze user behavior, performance, adoption, and usage with prebuilt dashboards and reports. Pardot can help create personalized email campaigns, track customer engagement, automate lead generation, and measure marketing ROI. References:

• https://www.salesforce.com/products/platform/products/salesforce-shield/
• https://www.salesforce.com/products/platform/products/event-monitoring-analytics-app/
• https://www.salesforce.com/products/marketing-cloud/best-marketing-automation-software/

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.

Contact, Order, and Product are the standard objects from Sales Cloud that a Solution Architect should map to B2C Commerce objects. Contact represents a person who is a customer or a potential customer of the company. Order represents an order placed by a customer for one or more products. Product represents an item or service that the company sells. These objects can be mapped to B2C Commerce objects such as Customer, Order, and Product using the B2C Commerce APIs or the Commerce Cloud Connector. 

Syncing Person Account object can help map subscriber data in Marketing Cloud when the company has Person Account set up on their Sales Cloud. This can enable bi-directional data integration between Sales Cloud and Marketing Cloud for Person Accounts, which are records that combine both Account and Contact information for individuals. References:

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

These answers are correct because they are ways that Salesforce CDP can help the organization in this scenario. Salesforce CDP can ingest customer data from each system and use matching rules to find records representing the same person, uniting them under a Unified Individual. This creates a single view of the customer across all systems and channels. Salesforce CDP can also power experiences through other channels like Marketing Cloud Engagement by activating customer segments. This enables personalized and targeted marketing campaigns based on customer data and behavior. References: https://www.salesforce.com/products/customer-data-platform/overview/

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]

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

A GIT repository is a version control system that allows developers to track changes in code and collaborate on projects. A GIT repository can help with tracing configuration and code changes across different environments and branches. Static code analysis tools are software tools that analyze source code or compiled versions of code to find potential errors, bugs, vulnerabilities, or quality issues. Static code analysis tools can help with ensuring basic standards for code quality and security. CI/CD pipelines are automated workflows that enable developers to integrate code changes into a shared repository and deliver them to production environments with speed and reliability. CI/CD pipelines can help with testing, deploying, and monitoring configuration and code changes across different environments. Smoke testing is a type of software testing that verifies the basic functionality of an application or system after deployment. Smoke testing can help with ensuring the stability and performance of configuration and code changes, but it does not trace or enforce them. Salesforce DX is a set of tools and features that enable developers to build applications on the Salesforce Platform using an org development model or a package development model. Salesforce DX can help with managing configuration and code changes across different environments, but it is not specific to multi-cloud implementations. References:

• https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control
• https://www.perforce.com/blog/qac/what-static-code-analysis
• https://www.redhat.com/en/topics/devops/what-is-ci-cd
• https://www.guru99.com/smoke-testing.html
• https://developer.salesforce.com/platform/dx

This answer is correct because it is a way to export all the customer data from B2C Commerce and import into Service Cloud without additional development. Business Manager is a tool that allows B2C Commerce administrators to export customer data in CSV format. Data Loader is a tool that allows Salesforce administrators to import data from CSV files into Salesforce objects. References: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/BusinessManager/ExportingCustomerData.html https://developer.salesforce.com/docs/atlas.en-us.dataLoader.meta/dataLoader/data_loader.htm

This answer is correct because it is a way to respond to the management team’s request to help formulate a roadmap for these new capabilities using the relationship design process. The relationship design process is a method that centers relationships as the building blocks of business and social value. It is based on four mindsets that can help design products and services from a place of compassion: compassion, intention, courage, and reciprocity. By facilitating a workshop with the management team, applying the relationship design process, a Solution Architect can help create a roadmap that aligns with business objectives and builds customer trust. References: https://www.salesforce.com/blog/how-relationship-design-works/

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

To enable the scenario of sending promotional emails with coupon offers generated in B2C Commerce, the following elements are required:

• A B2C Commerce cartridge to call Marketing Cloud APIs, such as the Transactional Messaging API, to trigger the email journey and pass the coupon code as a data attribute.
• A Marketing Cloud Installed Package to create an API integration between B2C Commerce and Marketing Cloud and provide authentication credentials and permissions.
• A B2C Commerce storefront to generate and manage the coupon codes and redemption logic. References: https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/transactional-messaging-api https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/promotions/b2c_coupon_codes.html

B. Using a Salesforce record ID as a single unique identifier to apply across channels and clouds can help ensure GDPR compliance by enabling data portability, deletion, and anonymization across systems. This can also reduce data duplication and improve data quality. D. Setting field-level encryption across B2C Commerce, Marketing Cloud, and Service Cloud can help ensure GDPR compliance by protecting sensitive data from unauthorized access or disclosure. This can also help meet the requirements of data minimization and pseudonymization. References:

• https://trailhead.salesforce.com/en/content/learn/modules/gdpr_basics/gdpr_basics_principles
• https://help.salesforce.com/s/articleView?id=sf.mc_co_contact_key.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_security.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.field_level_encryption.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

This answer is correct because it is a next step that a Solution Architect should suggest to provide UC the kind of understanding they are looking for regarding how to manage or work with health related data while still keeping their users trust. A Consequence Scanning Workshop is a method that helps identify potential positive and negative consequences of a product or service on people, society, and environment. It can help UC anticipate the impact of their work on their users’ trust and privacy, and design solutions that mitigate risks and maximize benefits. References: https://www.salesforce.com/blog/how-relationship-design-works/

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

The B2C Commerce - Service Cloud Connector is a solution that enables integration between B2C Commerce and Service Cloud. It allows displaying customer and order information in Service Cloud, creating orders on behalf of customers, and synchronizing customer data between the two systems. Prior to implementation, a Solution Architect should keep in mind the following considerations:

• Guests or anonymous storefront shoppers are not supported in this scenario. The Service Cloud Connector requires a customer account to be created in B2C Commerce and Service Cloud for each shopper. Guests or anonymous shoppers who do not have an account cannot be supported by the Service Cloud Connector. Therefore, the Solution Architect should ensure that the B2C Commerce storefront requires or encourages shoppers to create an account before placing an order.
• Service agents need a corresponding storefront login mapped to their Service Cloud user record. The Service Cloud Connector requires a mapping between the service agent’s user record in Service Cloud and the customer’s account record in B2C Commerce. This mapping allows the service agent to access customer and order information from B2C Commerce and create orders on behalf of the customer using the storefront login. Therefore, the Solution Architect should ensure that the service agent’s user record has a field that stores the corresponding storefront login of the customer.
• The Service Cloud Connector only supports Person Accounts as a customer model. Person Accounts are a type of account in Salesforce that combines an account and a contact into a single record. The Service Cloud Connector requires Person Accounts to store customer information from B2C Commerce. Therefore, the Solution Architect should ensure that Person Accounts are enabled and configured in Service Cloud before implementing the Service Cloud Connector.

Option B is incorrect because B2C Commerce does not need to be registered as a remote site for the Service Cloud Connector to work. A remote site is a web service or domain that Salesforce can access from Apex code or Visualforce pages. The Service Cloud Connector does not use Apex code or Visualforce pages to access B2C Commerce, but rather uses REST APIs and OAuth 2.0 authentication. References:

• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.accounts_person.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.remoteaccess_define.htm&type=5

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

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

Salesforce Shield Encryption is a feature that allows encrypting sensitive data at rest in Salesforce without compromising functionality or performance. Shield Encryption uses probabilistic encryption to protect data while preserving its format and length. Field-Level Encryption is a feature in Marketing Cloud that allows encrypting sensitive data at rest in Marketing Cloud using customer-managed keys. Field-Level Encryption uses deterministic encryption to protect data while preserving its format and length. When determining an appropriate solution for encrypting specific fields in Service Cloud as well as in data extensions in Marketing Cloud, the following considerations are relevant:

• With Shield, encrypted fields cannot be used to filter or sort in Process Builder and Flow Builder. Process Builder and Flow Builder are tools in Salesforce that allow creating automated workflows and processes based on certain criteria or conditions. However, Shield Encryption does not support filtering or sorting on encrypted fields in these tools, because probabilistic encryption does not allow exact matching or comparison of values.
• Shield encryption can be done on any standard or custom field on all field types, but cannot be set to encrypt those fields in Marketing Cloud. Shield Encryption supports encrypting any standard or custom field on any field type in Salesforce, such as text, email, phone, date, etc. However, Shield Encryption does not apply to Marketing Cloud fields or data extensions, because they are stored in a separate database from Salesforce. To encrypt fields in Marketing Cloud, Field-Level Encryption must be used.

Option A is incorrect because with Shield, encrypted fields are visible to the user if they have the View Encrypted Data permission, but there are other feature impacts such as filtering, sorting, searching, etc. Option C is incorrect because Field-Level Encryption is not required on Marketing Cloud to encrypt the custom fields if they are already encrypted by Shield Encryption in Service Cloud. However, Field-Level Encryption can be used on Marketing Cloud if additional encryption or customer-managed keys are needed. References:

• https://help.salesforce.com/s/articleView?id=sf.security_pe_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.security_pe_considerations_general.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_overview_field_level_encryption.htm&type=5

• B is correct because B2C Commerce order management does not support complex or advanced use cases such as split shipments, backorders, partial cancellations, or returns3. Salesforce Order Management provides these capabilities out of the box or with minimal customization.
• C is correct because Salesforce Order Management can be installed as a managed package in an existing Service Cloud org, which means that the existing Service Cloud implementation team can leverage their existing skills and knowledge to extend the product to meet the business needs.
• E is correct because Salesforce Order Management shares the same database with Service Cloud, which eliminates the need for additional integration between the two systems. Other solutions would require building custom integration to synchronize data between different databases.
• A is incorrect because Salesforce Order Management does not replace the Service Cloud Connector, which is used to synchronize data between Service Cloud and B2C Commerce. Salesforce Order Management integrates with both Service Cloud and B2C Commerce using platform events and REST APIs.
• D is incorrect because Salesforce Order Management does not support synchronizing orders from one B2C Commerce realm to multiple Salesforce orgs without customization. The standard integration assumes that there is a one-to-one relationship between a B2C Commerce realm and a Salesforce org.

References:

• 3: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/OrderManagement/OrderManagementOverview.html
• : https://help.salesforce.com/s/articleView?id=sf.om_order_management.htm&type=5
• : https://help.salesforce.com/s/articleView?id=sf.om_installation.htm&type=5
• : https://help.salesforce.com/s/articleView?id=sf.om_data_model.htm&type=5
• : https://help.salesforce.com/s/articleView?id=sf.om_b2c_commerce_integration.htm&type=5
• : https://help.salesforce.com/s/articleView?id=sf.om_b2c_commerce_integration_overview.htm&type=5

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

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

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

Marketing Cloud should be the single source of truth for customer journey flow, which is the sequence of interactions that a customer has with a brand across different channels and touchpoints. Marketing Cloud can help design, execute, and optimize customer journeys using Journey Builder, which can leverage data from other systems, such as B2C Commerce or Service Cloud, to trigger or personalize journeys. References: https://help.salesforce.com/s/articleView?id=sf.mc_jb_journey_builder.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

A Technical Design Specification is a document that describes the technical architecture and design of a solution, including the data mapping/model and systems integration. This document can help the company understand the solution that is needed and how it will meet their requirements. References: https://trailhead.salesforce.com/content/learn/modules/solution-design-for-technical-architects/define-the-technical-architecture

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

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.

• Option A is correct because configuring Einstein Retargeting Recommendations in Marketing Cloud to automate segment generation for Journey Builder is a valid recommendation to improve the success of the automated campaign. Einstein Retargeting Recommendations uses machine learning to identify customers who are likely to purchase again based on their past behavior and preferences, and automatically creates segments for Journey Builder to send personalized messages and offers.
• Option D is correct because using Einstein Discovery to generate a retargeting score representing likelihood to purchase in the next three months is a valid recommendation to improve the success of the automated campaign. Einstein Discovery uses advanced analytics and AI to analyze data from multiple sources and generate predictive insights and recommendations. A retargeting score can help the company prioritize and target customers who have a high probability of buying again.
• Option B is incorrect because using SMS as a channel due to its significantly higher engagement rate as compared to email is not a valid recommendation to improve the success of the automated campaign. SMS may have a higher engagement rate than email, but it also has a higher cost and a lower personalization potential. SMS should be used sparingly and strategically for time-sensitive or urgent messages, not for general re-engagement campaigns.
• Option C is incorrect because generating personalized coupon codes in B2C Commerce and sending them through Marketing Cloud to be able to effectively track impact of campaigns is not a valid recommendation to improve the success of the automated campaign. Personalized coupon codes may increase conversions and loyalty, but they also reduce margins and profitability. Coupon codes should be used selectively and carefully for customers who have a high lifetime value or a high retargeting score, not for all customers who made purchases in the last 24 months.

References:

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

• Option B is correct because allowing customers to unsubscribe via email with one click is a best practice for email marketing and compliance with anti-spam laws, and allowing customers to opt-in or opt-out of specific communication methods through a hosted preference center is a way to provide more granular control and personalization for customers.
• Option C is correct because using native B2C Commerce registration options during the browse and checkout experience is a way to capture customer information and consent, and extending these features to provide an opt-in or opt-out communication preference center on a secure page within the same storefront UI is a way to leverage the existing B2C Commerce platform and provide a consistent user experience.
• Option A is incorrect because allowing cookie consent to auto-enable email and/or mobile communications directly to the customer is not a valid or sufficient way to obtain customer consent for direct marketing purposes, and may violate privacy laws and regulations.
• Option D is incorrect because implicitly enrolling all customers in direct mobile communications during checkout is not a valid or sufficient way to obtain customer consent for direct marketing purposes, and may violate privacy laws and regulations. Additionally, allowing customers to opt-in or opt-out of all services via email sent by Marketing Cloud is not a user-friendly or secure way to manage customer preferences.

References:

• [Certification - B2C Solution Architect - Trailhead]
• [Study for the B2C Solution Architect Certification | Salesforce - Trailhead]
• [B2C Solution Architect Certification Guide | Salesforce Ben]

• 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

• 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

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 .

Business Manager is a web-based tool that allows B2C Commerce administrators to export customer data in CSV format. Data Loader is a desktop tool that allows Salesforce administrators to import data in CSV format into Service Cloud. This is an efficient way to migrate a large batch of customer records from one system to another. References: https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/BusinessManager/BusinessManager.html https://help.salesforce.com/s/articleView?id=sf.data_loader.htm &type=5

B. Creating a custom preference center that updates the records in Sales Cloud can help meet the requirements by allowing customers to manage their subscription preferences and opt-in or opt-out of different email lists or publications. This can also provide more granular control over the data synchronization between Sales Cloud and Marketing Cloud. D. Implementing the Marketing Cloud Connector can help meet the requirements by enabling bi-directional data integration between Sales Cloud and Marketing Cloud. This can also allow Marketing Cloud to honor the unsubscribe status of contacts or leads in Sales Cloud when sending emails. References:

• 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.mc_co_unsubscribes_and_subscribers.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_create_a_custom_profile_center.htm&type=5

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

CDP is a feature that allows creating a unified and holistic view of the customer across different systems and channels. CDP can use various identifiers, such as email, phone, or social media, to recognize customers as humans and extend existing records related to that human across connected systems, such as B2C Commerce, Service Cloud, and Marketing Cloud. CDP can also assign a consistent Global Party ID to each human, which can be used as a unique identifier across the systems. References: https://www.salesforceben.com/the-drip/complete-guide-to-customer-data-platforms-and-salesforce-cdp/

The fieldMapping custom settings in Service Cloud define how the attributes from the Commerce Profile are mapped to the fields on the Service Contact. If the nationalParks attribute was not mapped, then the service agent would not be able to see or update it in the Service Cloud console. References: https://help.salesforce.com/s/articleView?id=sf.b2c_service_cloud_connector_field_mapping.htm &type=5

A self-service portal is a feature in Service Cloud that allows creating branded websites and portals for customers to access self-service resources, such as knowledge articles, case management, chat, etc. To ensure that the theme of the self-service portal is consistent with the theme of the B2C Commerce storefront, a Solution Architect should do the following:

• Set the value of the Style Sheet URL setting to match the publicly-accessible URL of the style sheet the organization wants to use. The Style Sheet URL setting is a configuration option in Service Cloud that allows specifying a custom style sheet for the self-service portal. The style sheet must be hosted on a publicly-accessible web server and must follow certain guidelines and limitations. By setting the value of the Style Sheet URL setting to match the style sheet used by the B2C Commerce storefront, the Solution Architect can ensure that the self-service portal has the same look and feel as the storefront.

Option B is incorrect because there is no Portal Theme URL setting in Service Cloud. Option C is incorrect because copying any relevant CSS code from the organization’s website and pasting it into the pages for the self-service portal in Page Builder is not a recommended or supported way of customizing the theme of the self-service portal. Option D is incorrect because making a copy of the appropriate CSS file from the organization’s web server and uploading it to the self-service portal is not possible or advisable. The CSS file must be hosted on a publicly-accessible web server and referenced by the Style Sheet URL setting. References:

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

To adhere to global data privacy acts and respect customers’ privacy, the retailer should enable terms and conditions functionality within Marketing Cloud, which will allow them to display a custom message and a checkbox for customers to agree before they can submit a form or join a list. The retailer should also use profile and preference center functionality for Marketing Cloud Email Studio, which will allow them to capture consent and opt-in confirmation from customers, as well as provide them with options to manage their email preferences and unsubscribe.

References:

• [Terms and Conditions]
• [Profile and Preference Centers]