Free and Premium Salesforce B2C-Solution-Architect Dumps Questions Answers

Marketing Cloud account hierarchy is the way of organizing Marketing Cloud accounts and business units to support different business needs and use cases. A Marketing Cloud tenant is a top-level account that contains one or more business units. A business unit is a sub-account that can have its own data, content, users, and permissions. To set up Marketing Cloud account hierarchy for a company that has ecommerce sites for three countries: Australia, New Zealand, and Singapore, a Solution Architect should recommend the following:

• Use a single Marketing Cloud tenant and map business units to each site irrespective of the realm. This option allows the company to have a centralized account that can manage all the sites across different countries and regions. It also allows the company to have separate business units for each site that can have their own data, content, users, and permissions. This way, the company can maintain consistency and compliance across all the sites, while also enabling personalization and segmentation for each site.

Option A is incorrect because using a separate Marketing Cloud tenant for each site is not necessary or advisable. It would create complexity and inefficiency in managing multiple accounts and duplicating data and content across them. It would also increase the cost and maintenance of the solution. Option B is incorrect because using a separate Marketing Cloud tenant for each realm and mapping business units to sites within each realm is not optimal or scalable. It would create inconsistency and fragmentation between the realms and limit the ability to share data and content across them. It would also increase the cost and maintenance of the solution. Option D is incorrect because using a single Marketing Cloud tenant and mapping business units to each realm is not sufficient or flexible. It would not allow the company to have separate data, content, users, and permissions for each site within a realm. It would also limit the ability to personalize and segment for each site. References:

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

• 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

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

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/

• 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

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

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:

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: &type=5&language=en_US

These are three considerations that the financial services firm should be aware of when limiting data processing across these clouds. Removing a data processing restricted contact within Marketing Cloud requires removing the restriction first before removing the contact, as deleting a restricted contact will result in an error message. Exporting relevant customer data on Salesforce Platform so it is retained first before deleting or providing any data is a best practice for complying with data requests or regulations. Restricting data within Marketing Cloud requires contacting a Marketing Cloud account representative, as this feature is not available in the user interface.

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: &type=5

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.

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 .

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

Recommending CDP to integrate with their existing marketing tools and create individual profiles into commerce with the Commerce CDP Connector is a recommendation that a Solution Architect can make that will work with their existing technology investments. CDP is a platform that allows companies to unify, segment, activate, and analyze their customer data from multiple sources, including their existing marketing tools. CDP can also integrate with B2C Commerce using the Commerce CDP Connector, which enables bi-directional synchronization of individual profiles and customer groups between CDP and B2C Commerce. This way, the company can have a single view of their customers across all their marketing systems and their commerce tool, and provide personalized and consistent experiences.

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:

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

• 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

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: &type=5

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. 

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

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

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

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

A support case is a record that tracks a customer’s question, problem, feedback, or request for service. A support case can be created manually by a user or automatically by an email, web form, chat, etc. A support case can be assigned to a user or a queue for further action or resolution. To automatically route incoming support cases to the correct team based on their tier level, a Solution Architect should configure the following:

• Assignment Rules: Assignment rules are rules that define how to assign cases to users or queues based on certain criteria or conditions. Assignment rules can help automate the case assignment process and ensure that cases are routed to the right people or teams based on their skills, availability, workload, etc.
• Queues: Queues are lists of records that need to be worked on by multiple users or teams. Queues can help organize and prioritize workloads and distribute cases among users or teams based on their capacity or expertise.

Option C is incorrect because support processes are processes that define the stages or statuses that a case goes through from creation to closure. Support processes do not affect how cases are assigned to users or queues based on tier level. Option D is incorrect because auto response rules are rules that define how to send automatic email responses to customers when cases are created or updated based on certain criteria or conditions. Auto response rules do not affect how cases are assigned to users or queues based on tier level. References:

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

B. Allowing agents to more easily access customer data to better support customers when they call in can add value to the company by improving customer satisfaction, loyalty, and retention. This can also enable agents to provide personalized recommendations, cross-sell or upsell opportunities, and proactive service based on the customer’s profile, preferences, and purchase history. C. Allowing agents to use SSO to log into B2C Commerce and Service Cloud using the same credentials can add value to the company by simplifying the login process, enhancing security, and reducing administrative overhead. This can also provide a seamless user experience for agents across different systems and platforms. References:

• https://www.salesforce.com/products/service-cloud/overview/
• https://www.salesforce.com/products/commerce-cloud/overview/
• https://help.salesforce.com/s/articleView?id=sf.identity_sso.htm&type=5

• A is correct because Salesforce Order Management does not have native support for multiple distribution centers and requires either an AppExchange package or custom Apex triggers to implement fulfillment rules based on custom attributes1.

This 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: &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

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.

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

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

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: &type=5

Leveraging collect.js on the B2C Commerce storefront allows the organization to track product page views and other web analytics data using Marketing Cloud’s Einstein Web Recommendations feature. This data can be used to segment customers in journeys using decision splits based on their product interests and behaviors.

This flow allows the customer to purchase online and pick up their order in the store using B2C Commerce, Salesforce Order Management, and Service Cloud. B2C Commerce exports the order to Salesforce Order Management, which handles the order orchestration and fulfillment. Salesforce Order Management passes the order information to Service Cloud, which can be used by the store staff to check the order details and availability. Once the order is picked up by the customer, Service Cloud updates the final status in Salesforce Order Management, which can trigger notifications or invoices. References: &type=5 &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]

• Option A is correct because configuring REST services in B2C Commerce is a necessary step to enable authentication and communication with Marketing Cloud via its API integration and to initiate transactional email delivery using Marketing Cloud’s Transactional Messaging REST API.
• Option C is correct because creating an API integration in Marketing Cloud using Installed Packages is a necessary step to provision access to Marketing Cloud APIs by external systems like B2C Commerce and to generate an API key and secret for authentication purposes.
• Option D is correct because customizing the B2C Commerce storefront to trigger Marketing Cloud Transactional Messages at strategic points in the customer’s experience is a necessary step to invoke Marketing Cloud’s Transactional Messaging REST API with a payload that informs message contents and recipients.
• Option B is incorrect because front-end development capabilities are not required to configure the Marketing Cloud Connector for triggered emails, but rather to customize the B2C Commerce storefront and the email templates in Marketing Cloud.
• Option E is incorrect because integrating Marketing Cloud and B2C Commerce to provide Marketing Cloud with B2C Commerce order and customer information on a nightly basis via SFTP is not required to configure the Marketing Cloud Connector for triggered emails, but rather to enable data synchronization and segmentation for marketing campaigns.

References:

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

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

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: &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

A. The Contact Data Portability report in Marketing Cloud is a feature that allows creating a report containing subscriber data related to a single contact, such as email address, name, phone number, preferences, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. B. The Customer Data Snapshots report in Commerce Cloud is a feature that allows creating a report containing purchaser data related to a single customer, such as order history, payment methods, addresses, etc. This report can be used to provide customers access to their own data or comply with data privacy regulations, such as GDPR or CCPA. References: &type=5

Tokenized Sending is a feature in Marketing Cloud that allows sending messages with data that is too sensitive to store in Salesforce due to laws, regulations, or security policies. Tokenized Sending uses an API call to exchange data from an external system with Marketing Cloud at send time, without storing the data in Salesforce. Marketing Cloud Connect is a feature that enables integration between Marketing Cloud and other Salesforce clouds such as Service Cloud. When using Tokenized Sending with Marketing Cloud Connect, the following implications should be considered:

• The synchronized data extensions will include the token and all PII attributes. Synchronized data extensions are tables in Marketing Cloud that store data from other Salesforce clouds using data synchronization in Marketing Cloud Connect. When using Tokenized Sending, the synchronized data extensions will include the token as well as all personally identifiable information (PII) attributes such as name, email, phone, etc. The token will serve as the subscriber key and contact key in Marketing Cloud, while the PII attributes will be used for personalization and segmentation.
• The standard email address field for contacts and leads needs to be populated with a token. When using Tokenized Sending, the standard email address field for contacts and leads in other Salesforce clouds needs to be populated with a token instead of an actual email address. The token resembles a standard email address but contains encrypted information about the subscriber. The token is used to exchange data with the external system at send time and send messages to the actual email address.

Option B is incorrect because not all emails need to be sent through Marketing Cloud or Marketing Cloud Connect to avoid disruptions when using Tokenized Sending. However, it is recommended to do so to ensure consistent tracking and deliverability data across clouds. Option D is incorrect because the token with all supporting attributes does not need to be stored in Service Cloud when using Tokenized Sending. The token and the attributes are stored in the external system and only exchanged with Marketing Cloud at send time. References:

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

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

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

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:

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