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

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

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

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

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.

This answer is correct because it is a way to reduce the storage size in Salesforce and still be able to access the ERP Invoice records in Salesforce. Salesforce Connect/External Objects can be used to display external data in Salesforce without copying or storing it. Custom Apex adapters can be used to connect to any external system that has a web service API, such as an ERP system. References: https://help.salesforce.com/s/articleView?id=sf.datacloud_connect.htm &type=5 https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_connector_intro.htm

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

Heroku is a cloud platform that allows developers to build, run, and scale applications using various languages and frameworks. Postgres is a relational database that can store large amounts of structured data. A custom solution using Heroku and Postgres can handle the high volume and frequency of data points generated by the “Track-My-Hike” feature, as well as provide scalability and flexibility for future enhancements. References: https://www.heroku.com/home https://www.postgresql.org/

• Option A is correct because the ability to change designs may affect the choice of survey tools and platforms, as well as the level of customization and maintenance required.
• Option C is correct because the volume of survey responses may impact the performance, scalability, and reliability of the survey solution, as well as the data storage and integration requirements.
• Option E is correct because the frequency of updating surveys may influence the design and governance of the survey solution, as well as the change management and testing processes.
• Option B is incorrect because front-end development capabilities are not relevant to the survey requirements, but rather to the implementation details and skills of the team.
• Option D is incorrect because the number of possible answers for a survey question is not a critical factor for designing a multi-cloud solution, but rather a minor detail that can be easily accommodated by most survey tools.

References:

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

Introducing a leads-management process and a web-to-lead form can have implications for consent, preferences, and compliance for converted leads in Marketing Cloud. For example, if a lead opts out of email communication in Sales Cloud, this preference should be reflected in Marketing Cloud as well. Similarly, if a lead is converted to a contact in Sales Cloud, the corresponding subscriber record in Marketing Cloud should be updated with the new ID and status. Leads can also have a detrimental impact on the quality of contact records in Sales Cloud if they are not properly deduplicated, validated, and enriched. For example, if a lead is created with an invalid or duplicate email address, this can affect the deliverability and personalization of email messages in Marketing Cloud. 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_subscriber_key.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_web_to_lead.htm&type=5

This answer is correct because managing inventory data inside of B2C Commerce makes it easier to parse by store and enable buy online pick up in store (BOPIS) functionality. B2C Commerce can store inventory information for multiple locations and provide real-time availability information to customers and service agents. B2C Commerce can also integrate with Salesforce OMS to manage order fulfillment and payment processing for BOPIS orders. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_oms_integration.htm &type=5

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

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

The 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

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

Enabling Contact to Multiple Accounts allows a single contact to be related to multiple accounts, which can prevent the creation of duplicate contacts with different primary accounts. Duplicate Matching Rules can help identify and prevent duplicate records based on the criteria and actions that you specify. 

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

• Need access to all external data in near real-time. Salesforce Connect allows accessing external data from ERP or other systems in near real-time, without any delays or synchronization issues. This ensures that the data is always up-to-date and consistent across systems.
• The external data is changing frequently. Salesforce Connect allows reflecting any changes or updates made to the external data in ERP or other systems immediately in Salesforce, without requiring any manual intervention or batch processes. This ensures that the data is always accurate and reliable across systems.
• Need real-time access to a small fraction of external data. Salesforce Connect allows accessing only a small fraction of external data that is relevant and needed for a specific use case, such as displaying customer order history or details. This reduces network overhead and improves performance.

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

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

A. SMS opt-in will sync with Service Cloud when contact ID is the subscriber key in Marketing Cloud. This can help enable consent and profile management across the clouds by allowing customers to opt-in or opt-out of SMS messages and reflecting their preferences in both Service Cloud and Marketing Cloud. This can also help comply with industry regulations and best practices for SMS marketing. C. Profile changes in B2C Commerce will sync to Service Cloud when person accounts are used. This can help enable consent and profile management across the clouds by allowing customers to update their profile information in B2C Commerce and syncing their changes to Service Cloud. This can also help maintain consistent and accurate customer data across different systems and platforms. References:

• https://help.salesforce.com/s/articleView?id=sf.mc_co_person_accounts.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

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

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

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

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/

These answers are correct because they are actions that a Solution Architect should take to accurately capture the requirements for a multi-cloud solution design. Including functional and technical experts across discovery workshops can help ensure that the requirements and priorities are captured from different perspectives and domains. Drafting a requirements and process document can help document the business needs, expectations, and constraints for the solution design. Inviting key business and technical/design team stakeholders to review and approve the document can help validate the requirements and ensure alignment. References: https://trailhead.salesforce.com/en/content/learn/modules/solution-design/solution-design-process

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]

• 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

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

B. An ETL (Extract, Transform, Load) tool is a software that can help extract data from multiple sources, transform it according to business rules, and load it into a target destination, such as Salesforce. An ETL tool can also help run data cleansing tools, such as deduplication, validation, standardization, and enrichment, to obtain a clean data set before migrating it to Salesforce. C. Iteratively testing smaller loads against a developer or partial copy sandbox and the full load against a full copy sandbox can help ensure the data migration is successful and error-free. A developer or partial copy sandbox can be used for testing the data quality, mapping, and transformation rules, while a full copy sandbox can be used for testing the performance, scalability, and integrity of the data migration. References: https://trailhead.salesforce.com/en/content/learn/modules/data-management-basics/data-management-basics-migrate https://help.salesforce.com/s/articleView?id=sf.data_sandbox_create.htm &type=5

Shield Platform Encryption is a feature that allows you to encrypt sensitive data at rest in Service Cloud and B2C Commerce, while preserving platform functionality. Encrypted Data Sending (EDS) is a feature that allows you to send encrypted data from Service Cloud to Marketing Cloud using an encryption key that only you control. B2C Commerce’s crypto API is a set of methods that allow you to encrypt and decrypt data using symmetric or asymmetric keys in your code.

References:

• [Salesforce Shield Platform Encryption Implementation Guide]
• [Encrypted Data Sending (EDS) for Marketing Cloud]
• [B2C Commerce Crypto 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

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.

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

Both options A and B are valid ways to implement an Abandoned Cart Solution Workflow using B2C Commerce and Marketing Cloud. Option A uses streaming updates for catalog importing, which allows for near real-time updates of product information in Marketing Cloud. Option B uses data feeds that are transferred via SFTP and imported via Automation Studio, which allows for more control over the data format and frequency. Both options use collect.js or Collect Tracking Code to monitor shopper behavior on the B2C Commerce site and share it with Marketing Cloud. Both options also use Journey Builder to trigger personalized messages based on abandoned cart events. Option C is not valid because Google Analytics tracking is not part of the solution. Option D is not valid because inventory data is not required for the solution. References:

• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_abandonedcart_req_workflow.htm&language=en_US&type=5
• https://trailhead.salesforce.com/content/learn/modules/salesforce-solution-kits-quick-look/c360-sk1

• 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

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.

This answer is correct because it is a way to store payment information while still maintaining security and compliance. A tokenized payment card is a method that replaces sensitive card data with a unique identifier or token that cannot be mathematically reversed. The actual card data is stored in a secure vault by a payment processor or gateway. This way, the company can facilitate one-click ordering and automatic payment without exposing or storing the actual card data. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_payment_processing.htm &type=5

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.

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

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

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.

A multi-cloud integration is a solution that allows connecting and integrating data and applications across different cloud platforms and systems. A multi-cloud integration can provide various benefits, such as scalability, flexibility, resilience, and innovation. To design and implement a robust and scalable multi-cloud integration, a Solution Architect should recommend the following:

• Build an application network by adopting an API-led connectivity approach that packages underlying connectivity and orchestration services as easily discoverable and reusable API building blocks. An application network is a way of organizing applications, data, and devices into a network of reusable services that can be composed and recomposed to meet changing business needs. An API-led connectivity approach is a methodical way to connect data and applications through reusable and purposeful APIs that are developed to play a specific role: unlocking data from systems, composing data into processes, or delivering an experience. By building an application network using an API-led connectivity approach, the Solution Architect can enable a composable, connected, and automated solution that can leverage the capabilities of different cloud platforms and systems in a flexible and agile way.

Option A is incorrect because implementing an integration solution using an outbound messaging design pattern and Salesforce Connect as the integration approach is not suitable or scalable for a multi-cloud integration. An outbound messaging design pattern is a way of sending notifications from Salesforce to external systems when a record is created or updated. Salesforce Connect is a feature that allows accessing and integrating external data from various sources without copying or storing it in Salesforce. These approaches are limited in functionality, performance, security, and reliability for a complex multi-cloud integration scenario. Option B is incorrect because implementing a custom integration solution using lightweight middleware tools like Jitterbit or Talend is not optimal or sustainable for a multi-cloud integration. Lightweight middleware tools are software applications that provide basic integration capabilities, such as data transformation, routing, orchestration, etc. However, these tools are not designed for building an application network or supporting an API-led connectivity approach. They also require custom code or configuration that can increase the cost and complexity of the solution. Option D is incorrect because building multiple point-to-point application integrations connecting the multi-cloud and on-premises applications using SOA (Service-Oriented Architecture) and SOAP web services is not advisable or scalable for a multi-cloud integration. Point-to-point integrations are direct connections between two applications or systems that are tightly coupled and hard to maintain. SOA is an architectural style that organizes applications into loosely coupled services that communicate through standardized interfaces. SOAP web services are protocols that allow exchanging structured data between applications using XML messages. However, these approaches are outdated and inefficient for a modern multi-cloud integration scenario. They also create complexity and fragility in the solution. References:

• https://www.mulesoft.com/resources/api/what-is-api-led-connectivity
• https://www.mulesoft.com/resources/api/what-is-an-application-network
• https://help.salesforce.com/s/articleView?id=sf.datacloud_connect_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.workflow_om_outboundmessaging.htm&type=5

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

To enable the ‘Order on Behalf of’ functionality, the B2C Commerce account must have the ‘Order on Behalf of’ permission enabled and the ‘Customer Service’ role assigned. The agents must also have a user record in Service Cloud and an account created in B2C Commerce with the same email address. References: https://help.salesforce.com/s/articleView?id=sf.b2c_service_cloud_connector_order_on_behalf_of.htm &type=5