Salesforce B2C-Solution-Architect - Salesforce Certified B2C Solution Architect

An abandoned cart solution is a solution that allows sending personalized and timely email reminders to customers who have added items to their shopping cart but have not completed the purchase. An abandoned cart solution can help increase conversion rates, revenue, and customer loyalty. To implement an abandoned cart solution for their ecommerce storefront in Marketing Cloud, a Solution Architect should follow the following process:

Implement collect.js in the ecommerce storefront. Collect.js is a JavaScript code that allows tracking customer behavior and interactions on the ecommerce website, such as browsing products, adding items to cart, etc. Collect.js sends this behavioral data to Marketing Cloud for further analysis and action.

Create a behavioral trigger. A behavioral trigger is a rule that defines how to map behavioral data to a target data extension when a customer takes a particular action, such as abandoning a cart or browser session. A behavioral trigger can help automate the data flow and segmentation process based on customer behavior.

Create an email in Marketing Cloud. An email is a message that contains text, images, links, and other content that can be sent to customers via email. An email can be created using Content Builder, a tool that allows designing and managing email content in Marketing Cloud.

Create a journey. A journey is a sequence of messages and actions that are triggered by customer events or attributes. A journey can be created using Journey Builder, a tool that allows designing and managing customer journeys in Marketing Cloud.

Option A is incorrect because exporting the purchase data from B2C Commerce, importing the data into Marketing Cloud, and creating an email in Content Builder is not a sufficient or efficient process for implementing an abandoned cart solution. This process does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. Option B is incorrect because setting up Marketing Cloud Connector, creating an email in Marketing Cloud, and creating a send trigger is not a suitable or scalable process for implementing an abandoned cart solution. Marketing Cloud Connector is a feature that allows integrating Marketing Cloud with other Salesforce products, such as Sales Cloud or Service Cloud. It is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. A send trigger is a rule that defines how to send an email to customers based on certain criteria or conditions. However, a send trigger does not capture or leverage the behavioral data collected by collect.js, which is crucial for creating an effective abandoned cart solution. Option D is incorrect because setting up Einstein Recommendations, setting up Marketing Cloud Connector, and creating an email in Marketing Cloud is not a relevant or optimal process for implementing an abandoned cart solution. Einstein Recommendations is a feature that allows generating personalized product recommendations based on customer behavior and preferences. It is not directly related to creating an abandoned cart solution, although it can be used to enhance the email content with relevant recommendations. As mentioned before, Marketing Cloud Connector is not necessary or relevant for integrating Marketing Cloud with B2C Commerce. This process also does not involve creating a behavioral trigger or a journey, which are essential for sending timely and personalized email reminders based on customer behavior. References:

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

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

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

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

These answers are correct because they are actions that a Solution Architect should take to help meet the need for improving lead generation metrics. Implementing Audience Studio and integrating it with Marketing Cloud can help bridge the divide between the known and the unknown customer by capturing and activating data from multiple sources and channels. Using analytics tools such as Datorama can help improve accountability on campaign spend for digital advertising and marketing campaigns by providing insights into performance, ROI, and optimization. Running a proof-of-concept of Customer 360 Data Manager can help build unified customer identities by ingesting and matching data from different systems and creating a single source of truth for customer data. References: https://help.salesforce.com/s/articleView?id=sf.mc_dmp_dmp.ht m&language=en_US&type=5 https://www.salesforce.com/products/marketing-cloud/best-practices/datorama-marketing-intelligence/ https://www.salesforce.com/blog/customer-360-dat a-personalization/

B2C Commerce and Service Cloud are not natively integrated and require custom development to enable data synchronization and API access between them. B2C Commerce and Marketing Cloud also require custom development to enable API access for customer engagement scenarios. References: https://help.salesforce.com/s/ar ticleView?id=sf.b2c_service_cloud_connector_overview.htm&type=5 https://developer.salesforce.com/docs/commerce/sfra/marketing-cloud/marketing-cloud-integration

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

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

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

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]

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

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

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