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

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

The Order on Behalf of functionality allows Service Cloud agents to create orders for customers on the B2C Commerce storefront. To enable this functionality, the following design and architecture considerations should be followed:

• Verify that the permissions used are Login_On_Behalf, Login_Agent, and Create_Order_On_BehaIf_Of business manager functional permissions. These permissions are required for the Service Cloud Connector user in B2C Commerce to perform the Order on Behalf of actions.
• The Order on Behalf of feature in the Service to B2C Commerce Connector only supports person accounts as a customer model by default. If the customers using the storefront are household accounts, additional customization is required to map the household account ID to the B2C Commerce customer ID.
• Verify that agents are Service Cloud and B2C Commerce users with Order on Behalf rights. Agents need to have both Service Cloud and B2C Commerce user accounts with the appropriate roles and permissions to access the Order on Behalf of feature.

Option C is incorrect because a default user is not required for anonymous storefront shoppers. Option D is incorrect because the REST calls between B2C Commerce and Service Cloud do count towards API governor limits. References:

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

Experience Cloud is a product that allows creating and managing digital experiences for customers, partners, employees, and communities. Experience Cloud can be integrated with external payment gateways and Pardot to offer secure and personalized experiences for members who want to set up recurring donations. To increase security for their existing users, a Solution Architect can recommend the following options:

• Implement high-assurance requirements for Experience Cloud profiles. High-assurance requirements are settings that define the level of security and identity verification needed for users to access certain pages or features in Experience Cloud. High-assurance requirements can help prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.
• Add a login flow that defines the scope of user access authorized by authentication providers. A login flow is a process that allows customizing the user login experience in Experience Cloud using various actions, such as collecting information, displaying messages, updating records, etc. A login flow can help define the scope of user access authorized by authentication providers, such as social media accounts or SAML-based identity providers. This can help limit or restrict the access of users based on their authentication method or credentials.
• Develop login flows to change the user’s session security level to initiate third-party identity verification. A session security level is a setting that determines the level of security and identity verification required for a user’s session in Experience Cloud. A session security level can be changed using login flows to initiate third-party identity verification, such as SMS verification, email verification, biometric verification, etc. This can help enhance the security and trust of the user’s session and prevent unauthorized or fraudulent access to sensitive or confidential data or transactions, such as recurring donations.

Option C is incorrect because replacing Pardot with Marketing Cloud to implement SMS for multi-factor authentication is not a valid or feasible option to increase security for their existing users. Pardot is a product that allows creating and managing B2B marketing campaigns and activities, such as email marketing, lead generation, lead nurturing, etc. Marketing Cloud is a product that allows creating and managing B2C marketing campaigns and activities, such as email marketing, mobile marketing, social media marketing, etc. Replacing Pardot with Marketing Cloud would not only be costly and complex, but also unnecessary and irrelevant for their use case of setting up recurring donations. Moreover, implementing SMS for multi-factor authentication does not require replacing Pardot with Marketing Cloud, as it can be done using other methods or tools, such as login flows or third-party identity verification services. Option D is incorrect because maintaining GAuth tokens for existing Experience Cloud profiles is not an option or a way to increase security for their existing users. GAuth tokens are tokens that are used by Google Authenticator, an app that generates one-time passwords for two-factor authentication. GAuth tokens are not related to Experience Cloud profiles or their security settings. References:

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

• 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

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

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

B2C Commerce Governance and Quotas are a set of rules and limits that apply to B2C Commerce instances to ensure the efficiency and stability of solutions built on the platform. The following considerations should be kept in mind when considering B2C Commerce Governance and Quotas:

• Object quotas status is updated with an up to 20-minute delay. Therefore, a Solution Architect must consider this delay when performing calculations related to traffic and limits. Object quotas are limits on the number of objects that can be created or stored in B2C Commerce, such as products, categories, customers, orders, etc. The object quotas status shows the current usage and remaining capacity of each object quota. However, the status is not updated in real time, but with an up to 20-minute delay. This means that the Solution Architect should account for this delay when estimating the traffic and limits for each object quota.
• If an enforced quota is exceeded, an exception is thrown, which prevents the current operation from completing. The Solution Architect should design the solution so that the exception can be caught within a customization. Enforced quotas are quotas that are strictly enforced by B2C Commerce and cannot be exceeded or changed by customers. Examples of enforced quotas are API calls per hour, script execution time, cache size, etc. If an enforced quota is exceeded, B2C Commerce throws an exception that stops the current operation from completing. This can result in errors or failures in the storefront or backend processes. The Solution Architect should design the solution so that the exception can be caught within a customization and handled gracefully.

Option B is incorrect because sandbox quotas cannot be softened by exporting them from a production instance and importing them onto a sandbox instance. Sandbox quotas are fixed and cannot be changed by customers. Option C is incorrect because the Solution Architect cannot assume that quota violations have not occurred unless a site is experiencing performance issues. Quota violations can occur without affecting the site performance, but they can still cause errors or failures in certain operations or processes. References:

• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/GovernanceOverview.html
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/ObjectQuotas.html
• https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/Governance/EnforcedQuotas.html

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.

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

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

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

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. 

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

Product Catalogs are a type of data extension that contain product information for generating product recommendations using Einstein in Marketing Cloud. Product Catalogs can be configured natively to sync from B2C Commerce to Marketing Cloud using a point and click configuration in the Marketing Cloud Business Manager. References: https://help.salesforce.com/s/articleView?id=sf.mc_pb_product_catalog.htm &type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

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

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.

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

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

Service Cloud is a product that allows managing customer service interactions across different channels and systems. To explain the value of Service Cloud to a retail company that currently uses B2C Commerce and Marketing Cloud, a Solution Architect can discuss the following functionalities:

• Ability to allow the agent to see purchase history to support case management. Service Cloud can integrate with B2C Commerce to display customer order history and details in the service console or omnichannel routing. This allows agents to have a complete view of customer transactions and provide faster and more personalized service.
• Ability to have a customer leave a journey when they have an escalated case. Service Cloud can integrate with Marketing Cloud to trigger customer journey changes based on case events. For example, if a customer has an escalated case, Service Cloud can send a signal to Marketing Cloud to pause or exit the customer from a marketing journey, and resume or re-enter the customer when the case is resolved.

Option A is incorrect because Service Cloud does not provide the ability to create a B2C storefront using Digital Experiences. Digital Experiences is a feature of Experience Cloud that allows creating branded websites and portals for customers, partners, or employees. Option B is incorrect because Service Cloud does not provide the ability to de-duplicate and create a single customer identity. This functionality can be achieved by using Customer 360 Data Manager or other data integration tools. References:

• https://help.salesforce.com/s/articleView?id=sf.service_overview.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_order_on_behalf_of.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.mc_co_journey_builder.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.networks_overview.htm&type=5
• https://www.salesforce.com/in/blog/2020/04/what-is-salesforce-customer-360.html

• 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 connected B2C Solution approach is an approach that allows integrating B2C Commerce and Service Cloud to provide a seamless and omnichannel experience for customers across different touchpoints. A connected B2C Solution approach can provide various benefits, such as increased customer satisfaction, loyalty, retention, and revenue. To convince the company to shift to a connected B2C Solution approach, a Solution Architect should say the following:

• Agents will have easy access to customer data to provide a better service experience when customers call in. By integrating B2C Commerce and Service Cloud using features such as Service Cloud Connector or Salesforce Order Management, agents will be able to access customer and order information from B2C Commerce directly in Service Console without switching between multiple systems. This will enable agents to answer customer questions more quickly and accurately, resolve issues more efficiently, and offer personalized recommendations or solutions.

Option B is incorrect because agents will not have a better interface using Service Cloud and B2C Commerce with Heroku. Heroku is a platform that allows building, running, and scaling custom web applications using various languages and frameworks. Heroku is not directly related to creating a connected B2C Solution approach, although it can be used to extend or customize the functionality of B2C Commerce or Service Cloud. Option C is incorrect because agents cannot utilize SSO to launch an ‘Order on Behalf of’ storefront experience within the B2C Commerce UI. SSO is a feature that allows users to log in to multiple applications or systems with the same credentials. SSO does not enable launching an ‘Order on Behalf of’ storefront experience within the B2C Commerce UI, which is a feature that allows agents to create orders on behalf of customers using the storefront login. To enable this feature, the company needs to use Service Cloud Connector or Salesforce Order Management to integrate B2C Commerce and Service Cloud. Option D is incorrect because agents’ success rates will not be better measured after helping the company define ROI KPIs together. Although this is a possible benefit of shifting to a connected B2C Solution approach, it is not the most convincing or compelling one for the company’s situation. The company’s main pain point is the lack of systems and access to customer and order data, which affects their service quality and customer satisfaction. Therefore, the most convincing argument for shifting to a connected B2C Solution approach is how it can improve the service experience for both agents and customers by providing easy access to customer data. References:

• https://help.salesforce.com/s/articleView?id=sf.icx_b2c_overview.htm&type=5
• https://www.salesforce.com/products/commerce-cloud/ecommerce/order-management/
• https://help.salesforce.com/s/articleView?id=sf.sso_about.htm&type=5

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

References:

• : https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm
• : https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/intro_api_tooling.htm
• : https://developer.salesforce.com/docs/atlas.en-us.mc-apis.meta/mc-apis/index-api.htm
• : https://developer.salesforce.com/docs/atlas.en-us.api_streaming.meta/api_streaming/intro_stream.htm

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

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

• 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

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

• Option A is correct because enabling SSO on both Service Cloud and Marketing Cloud is a necessary step to allow agents to authenticate and access all systems with the least possible clicks, as they only need to log in once with their credentials and then switch between systems seamlessly.
• Option B is correct because defining which system is acting as an identity provider (IDP) is a necessary step to configure SSO between Service Cloud and Marketing Cloud, as it determines which system will verify the identity of the agents and issue authentication tokens for the other system.
• Option E is correct because enabling MFA on the identity provider (IDP) is a necessary step to meet the company’s requirement of confirming the identity of the agents using multi-factor authentication (MFA) upon logging in to either system. MFA adds an extra layer of security by requiring agents to enter a verification code or use another device besides their username and password.
• Option C is incorrect because configuring Marketing Cloud Connect is not a necessary step to enable SSO between Service Cloud and Marketing Cloud, as it is used for data synchronization and integration purposes, not for authentication or access management.
• Option D is incorrect because enabling Active Directory Federation Services (ADFS) and Salesforce Event Monitoring on the identity provider (IDP) are not necessary steps to enable SSO between Service Cloud and Marketing Cloud, as they are used for different purposes. ADFS is used for federating identities across different domains or organizations, while Salesforce Event Monitoring is used for tracking user activity and performance within Salesforce.

References:

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

These answers are correct because they are systems that can meet the company’s requirements for delivering a full list of all customer orders throughout their engagement lifetime, providing lifetime engagement tracking and history of the customer, and calculating the lifetime value of customers based on their orders. Salesforce Order Management can manage order lifecycle from capture to fulfillment across multiple channels. Service Cloud can provide a complete view of customer interactions across sales, service, marketing, and commerce. Marketing Cloud can track customer engagement across email, mobile, social, web, and more. CRM Analytics can provide insights into customer lifetime value based on order data and engagement history. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_oms_integration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.icx_b2c_crosscloudengagement_connectors.htm &language=en_US&type=5 https://www.salesforce.com/products/marketing-cloud/what-is-marketing-cloud/

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

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

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

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

This answer is correct because core profile data (name, email) should be maintained within Experience Cloud as the primary system when using communities as an identity provider (IDP) for commerce. This ensures that customers have a consistent identity across both platforms and can access self-service support features in communities. References: https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_service_cloud_integration.htm &type=5

• A is correct because defining a new platform event in Salesforce and publishing it with Process Builder when the opportunity status changes to Closed-Won is a valid way to trigger an integration with the ESB using the CometD protocol.
• D is correct because enabling ESB to subscribe to the platform event using the CometD protocol and notifying the back-end ERP system to create the order asynchronously is a valid way to handle the integration with the ERP system using a publish-subscribe model.
• B is incorrect because publishing to a platform event using the CometD protocol requires an Apex trigger, not a Process Builder process. Also, creating the order synchronously would not be advisable as it would introduce latency and dependency on the ERP system’s availability.
• C is incorrect because defining a new platform event in the back-end system for the order details would not be possible as platform events are Salesforce-specific objects that can only be defined within Salesforce.

References:

• : https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro_emp.htm
• : https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_subscribe.htm
• : https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_publish_apex.htm
• : https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_define.htm

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.

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. 

• 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

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

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

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. 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: https://help.salesforce.com/s/articleView?id=sf.mc_overview_contact_data_portability.htm &type=5 https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/admin/b2c_customer_data_snapshots.html

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