Salesforce B2C-Solution-Architect Exam With Confidence Using Practice Dumps

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

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