Free Salesforce B2C-Solution-Architect Practice Exam with Questions & Answers | Set: 2

Curating tiered experiences in Marketing Cloud allows the company to create personalized content and offers based on the loyalty level of the customers. Segmenting Journeys within CDP enables the company to use data from multiple sources to create customer segments and target them with relevant messages across channels. Creating Journeys by tiers in Marketing Cloud allows the company to design and execute customer journeys based on the loyalty program tiers and goals.

This answer is correct because it is a way to reduce the storage size in Salesforce and still beable 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: https://help.salesforce.com/s/articleView?id=sf.datacloud_connect.htm &type=5https://developer. salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_connector_intro.htm

A. Additional infrastructure (for example Heroku servers) may be required to host the application when using a headless approach. This can increase the complexity, cost, and maintenance of the solution. A Solution Architect should consider the trade-offs between flexibility and simplicity when choosing a headless approach. B. Features that are available by default inthe Storefront Reference Architecture (SFRA) app will need to be custom built in custom frameworks when using a headless approach. This can increase the development time, effort, and risk of the solution. A Solution Architect should consider the benefits and drawbacks of using SFRA versus custom frameworks when choosing a headless approach. D. Available Service, Marketing, and LINK accelerators may not work without modifications when using a headless approach. This can limit the integration capabilities andfunctionality of the solution. A Solution Architect should consider the compatibility and extensibility of the accelerators when choosing a headless approach. 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_sfra.htm&type=5
• https://help.salesforce.com/s/articleView?id=sf.b2c_commerce_link.htm&type=5

Contact, Order, and Product are the standard objects from Sales Cloud that a Solution Architect should map to B2C Commerce objects. Contact represents a person who is a customer or a potential customer of the company. Order represents an order placed by a customer for one or more products. Product represents an item or service that thecompany sells. These objects can be mapped to B2C Commerceobjects such as Customer, Order, and Product using the B2C Commerce APIs or the Commerce Cloud Connector. 

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.

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

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

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

A. Fixing the data quality issues in Service Cloud before migrating to Marketing Cloud can help avoidduplicate 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: https://help.salesforce.com/s /articleView?id=sf.mc_co_sync_leads_and_contacts.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5https://help.salesforce.com/s/articleView?id=sf.mc_co_map_salesforce_objects.htm&type=5

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 basedon 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.salesf orce.com/s/articleView?id=sf.icx_b2c_crosscloudengagement_connectors.htm&language=en_US&type=5https://www.salesforce.com/products/marketing-cloud/what-is-marketi ng-cloud/