Salesforce B2C-Solution-Architect Salesforce Certified B2C Solution Architect (SU24) Exam Practice Test

The REST calls between B2C Commerce and Service Cloud are subject to API governor limits, which can affect the performance and availability of the integration. The service agent users need to have B2C Commerce permissions and access keys to log in and place orders on behalf of registered storefront shoppers. 

Change Data Capture is an event-driven integration mechanism that allows near-real-time synchronization of Salesforce data changes with external systems. It does not impact the system performance as it uses asynchronous processing and does not require triggers or code. References: https://developer.salesforce.com/docs/atlas.en-us.change_data_capture.meta/change_data_capture/cdc_intro.htm

• Option D is correct because B2C Commerce should be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. B2C Commerce is the first point of contact for customers who register an account before making their first purchase, and it can store and update important profile and commerce information like email, phone number, beauty preferences, and saved addresses. B2C Commerce can also integrate with Experience Cloud and Salesforce Identity to provide a consistent and secure user experience across the social community and the ecommerce site.
• Option A is incorrect because Salesforce Identity should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Salesforce Identity is mainly used for authentication and identity management purposes, not for storing and updating customer profile and commerce information. Salesforce Identity can also integrate with Experience Cloud and B2C Commerce to provide a single sign-on (SSO) experience for customers across the social community and the ecommerce site.
• Option B is incorrect because Address book should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Address book is not a system or an application, but rather a feature or a data element that can be stored and updated in B2C Commerce or other Salesforce clouds.
• Option C is incorrect because Wishlist should not be the system of record for the primary profile after reviewing the workflow and attempting to minimize migration of customer profile data. Wishlist is not a system or an application, but rather a feature or a data element that can be stored and updated in B2C Commerce or other Salesforce clouds.

References:

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

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

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

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.

• 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

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

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/

This answer is correct because Salesforce Privacy Center is a tool that helps satisfy customer requests and data privacy laws related to the right-to-be-forgotten requirement. Salesforce Privacy Center allows admins to create policies that delete, archive, or de-identify the data subject’s PII in an org within 30 days of their request, without additional development. References: https://help.salesforce.com/s/articleView?id=privacy_center.htm &type=5&language=en_US

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

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

This answer is correct because the consent data model in Marketing Cloud allows for multiple contacts per individual customer, each with their own consent preferences for different brands. This enables consent-based marketing campaigns across multiple brands in a single org. References: https://help.salesforce.com/s/articleView?id=sf.mc_cab_consents.htm &type=5

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. 

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

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.

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

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

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

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

Identity is a feature that allows managing user authentication and access across different applications and systems. Identity can be either internal or external to Salesforce, depending on where the user credentials are stored and verified. To cover NTOs identity needs, a Solution Architect should recommend the following:

• Define a user registration handler to support user provisioning and authentication via social services like Google and Facebook. A user registration handler is a class in Apex code that defines the logic for creating and updating user accounts based on information from an external identity provider. A user registration handler can support user provisioning and authentication via social services like Google and Facebook, by using OAuth 2.0 protocols and OpenID Connect standards to exchange user information and tokens between Salesforce and the social services.
• Leverage Salesforce Identity as the identity provider to centralize authentication for both Experience Cloud and B2C Commerce in one place. Salesforce Identity is a product that allows using Salesforce as an identity provider for other applications and systems. Salesforce Identity can centralize authentication for both Experience Cloud and B2C Commerce in one place, by using single sign-on (SSO) protocols and standards to enable users to log in to both applications with the same credentials.

Option C is incorrect because leveraging B2C Commerce as the identity provider for both Storefront and the Service Portal is not possible or advisable. B2C Commerce does not support acting as an identity provider for other applications or systems, as it does not support SSO protocols or standards. Option D is incorrect because using Salesforce CDP, which automatically syncs profiles and authentication information across systems, is not a valid or available option. Salesforce CDP is a product that allows creating unified customer profiles from various data sources, but it does not sync or manage authentication information across systems. References:

• https://help.salesforce.com/s/articleView?id=sf.identity_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.identity_provider.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.sso_about.htm&type=5
• https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_interface_Auth_RegistrationHandler.htm

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

These answers are correct because they are recommendations that can help ensure that customer experiences are compliant with all domestic and international regulations related to data privacy and security. Providing shoppers a mechanism to download their data can help comply with the right to access and portability under GDPR and other laws. Implementing Customer Data Platform (CDP) can help comply with data protection laws by providing tools to manage consent, preferences, and identity resolution across multiple channels and touchpoints. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_gdpr.htm &type=5 https://www.salesforce.com/products/customer-data-platform/overview/

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.

These answers are correct because they are recommendations that can improve the success of the automated re-engagement campaign. Using SMS as a channel can increase the engagement rate as compared to email, as SMS messages have higher open and response rates. Configuring Einstein Recommendations in Marketing Cloud can automate segment generation for Journey Builder, which can help create personalized and relevant messages based on customer data and behavior. References: https://www.salesforce.com/products/marketing-cloud/best-practices/sms-marketing-statistics/ https://help.salesforce.com/s/articleView?id=sf.mc_pb_einstein_recommendations.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

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/

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

• Option A is correct because the Salesforce Platform can be used for customer master and consent management, or it can integrate with a third-party Master Data Management system. This is an important consideration for this scenario, as it affects the data quality, security, and governance of customer data across multiple Salesforce clouds and systems.
• Option C is correct because Order Management System (OMS) is a B2C Commerce product but it does not run natively on the core Salesforce Platform. This is an important consideration for this scenario, as it affects the integration, performance, and scalability of OMS with other Salesforce clouds and systems.
• Option D is correct because Marketing Cloud enables personalization, journey orchestration, and cross-channel messaging. This is an important consideration for this scenario, as it affects the marketing strategy, campaign design, and customer engagement of the company.
• Option B is incorrect because Tableau does not require MuleSoft in order to access data outside of the Salesforce Platform. Tableau can connect to various data sources using native connectors or custom connectors without relying on MuleSoft.

References:

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

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

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

This option allows you to use Apex code to make HTTP requests and receive HTTP responses from an external system, such as a pricing and quotation service. You can use the @future(callout=true) annotation to make asynchronous callouts from Apex triggers or invocable methods. The other options are either not feasible or not optimal for this use case. 

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

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

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 .

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

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/

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

The B2C Commerce to Service Cloud Connector is a solution that enables integration between B2C Commerce and Service Cloud. It allows displaying customer and order information in Service Cloud, creating orders on behalf of customers, and synchronizing customer data between the two systems. When introducing the Service Cloud Connector into an existing Salesforce Org, the following functionality considerations should be aware of:

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

Option C is incorrect because the Service Cloud Connector does not natively support accounts and contacts, households, and multi-brand customer models. It only supports person accounts as a customer model by default. Option D is incorrect because the Service Cloud Connector provides a collection of Lightning components that display customer and order information within Service Cloud, which do not need to be customized or deployed by a developer. References:

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

• Option D is correct because B2C Commerce creates a customer ID when a customer registers an account before making their first purchase, but the primary record should be created through Service Cloud using an external ID field that matches the customer ID from B2C Commerce. This way, Service Cloud can store additional customer information and provide a single source of truth for customer data across multiple Salesforce clouds.
• Option A is incorrect because Service Cloud does not create a customer ID when a customer registers an account on B2C Commerce, nor does it create an additional ID to be used as the primary record. Service Cloud uses an external ID field that matches the customer ID from B2C Commerce to create or update customer records.
• Option B is incorrect because B2C Commerce does not create an additional ID to be used as the primary record when a customer registers an account. B2C Commerce only creates a customer ID that can be matched with an external ID field in Service Cloud or other Salesforce clouds.
• Option C is incorrect because Marketing Cloud does not create a customer ID when a customer registers an account on B2C Commerce, nor does it create a primary ID that should be used by other Salesforce clouds. Marketing Cloud uses subscriber keys that can be mapped to customer IDs from B2C Commerce or other external systems.

References:

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

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

References:

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

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

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.

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

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