Salesforce Certified B2C Solution Architect (Arch-302)

Working with stakeholders to create a customer journey map that improves conversions and running reports on the value of cart items and time since the last activity are two tactics that a Solution Architect could recommend to understand how to optimize the checkout process. A customer journey map is a visual representation of the steps and interactions that a customer goes through when engaging with a company or brand. It can help identify pain points, opportunities, and best practices for improving conversions. Running reports on the value of cart items and time since the last activity can help analyze the shopping behavior and preferences of customers, as well as identify potential reasons for cart abandonment.

Option A is correct because authentication credentials should be stored and managed by Experience Cloud as the system of record for this customer data. Experience Cloud acts as an identity provider (IDP) for commerce, meaning that it verifies the identity of customers who log in to ecommerce sites using their communities credentials. Experience Cloud can also leverage Salesforce Identity features to provide secure and seamless authentication across multiple Salesforce clouds and external systems.
Option B is incorrect because address book should not be stored and managed by Experience Cloud as the system of record for this customer data. Address book is mainly used for ecommerce purposes, such as shipping and billing addresses, and it should be stored and managed by B2C Commerce as the system of record. B2C Commerce can also integrate with Experience Cloud to provide a consistent user experience across ecommerce sites and communities.

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

Salesforce Shield Encryption is a feature that allows encrypting sensitive data at rest in Salesforce without compromising functionality or performance. Shield Encryption uses probabilistic encryption to protect data while preserving its format and length. Field-Level Encryption is a feature in Marketing Cloud that allows encrypting sensitive data at rest in Marketing Cloud using customer-managed keys. Field-Level Encryption uses deterministic encryption to protect data while preserving its format and length. When determining an appropriate solution for encrypting specific fields in Service Cloud as well as in data extensions in Marketing Cloud, the following considerations are relevant: With Shield, encrypted fields cannot be used to filter or sort in Process Builder and Flow Builder. Process Builder and Flow Builder are tools in Salesforce that allow creating automated workflows and processes based on certain criteria or conditions. However, Shield Encryption does not support filtering or sorting on encrypted fields in these tools, because probabilistic encryption does not allow exact matching or comparison of values.
Shield encryption can be done on any standard or custom field on all field types, but cannot be set to encrypt those fields in Marketing Cloud. Shield Encryption supports encrypting any standard or custom field on any field type in Salesforce, such as text, email, phone, date, etc. However, Shield Encryption does not apply to Marketing Cloud fields or data extensions, because they are stored in a separate database from Salesforce. To encrypt fields in Marketing Cloud, Field-Level Encryption must be used.
Option A is incorrect because with Shield, encrypted fields are visible to the user if they have the View Encrypted Data permission, but there are other feature impacts such as filtering, sorting, searching, etc.
Option C is incorrect because Field-Level Encryption is not required on Marketing Cloud to encrypt the custom fields if they are already encrypted by Shield Encryption in Service Cloud. However, Field-Level Encryption can be used on Marketing Cloud if additional encryption or customer-managed keys are needed.
References:
https://help.salesforce.com/s/articleView?id=sf.security_pe_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.security_pe_considerations_general.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.mc_overview_field_level_encryption.htm&type=5

Option A is correct because 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

A. The service console does not have a native integration with Einstein Web & Email Recommendations,
so a customized Lightning component is needed to display the recommendations based on the customer's browsing and purchase history. C. Each storefront should be linked to its own Marketing Cloud Business Unit to ensure relevant recommendations based on the product catalog and customer behavior of each market. This also provides data segregation and customization for each storefront.

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

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

B is correct because Marketing Cloud can be used for customer segmentation based on VIP status and cart abandonment behavior. B2C Commerce can be used for creation of coupon codes using promotion rules and coupon code restrictions. B2C Commerce and Marketing Cloud functionalities can be used to send abandoned cart emails using the Marketing Cloud Connector cartridge and the Abandoned Cart Journey template. Marketing Cloud can track email open and forward count using tracking metrics.
A is incorrect because Service Cloud is not used for customer segmentation or creation of coupon codes.
Service Cloud is used for customer service and case management.
C is incorrect because B2C Commerce is not used for customer segmentation or creation of coupon codes. B2C Commerce is used for online shopping and order management.
D is incorrect because Tableau CRM is not used to track email open and forward count. Tableau CRM is used for data analysis and visualization.
References:
https://help.salesforce.com/s/articleView?id=sf.mc_co_create_audience_segment.htm&type=5
https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/content/b2c_commerce/topics/coupons/b2c_creating_coupon_codes.html
https://help.salesforce.com/s/articleView?id=sf.mc_co_abandoned_cart_journey.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.mc_es_email_tracking_metrics.htm&type=5

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.

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