Pass the Salesforce Architect Exams B2C-Solution-Architect Questions and answers with ExamsMirror

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

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.

References:

[API Integration]

[Transactional Messaging API]

[Send Classifications]

To enable the ‘Order on Behalf of’ functionality, the B2C Commerce account must have the ‘Order on Behalf of’ permission enabled and the ‘Customer Service’ role assigned. The agents must also have a user record in Service Cloud and an account created in B2C Commerce with the same email address. References: https://help.salesforce.com/s/articleView?id=sf.b2c_service_cloud_connector_order_on_behalf_of.htm &type=5

Identity is a feature that allows managing user authentication and access across different applications and systems. Identity can be either internal or external to Salesforce, depending on where the user credentials are stored and verified. To cover NTOs identity needs, a Solution Architect should recommend the following:

Define a user registration handler to support user provisioning and authentication via social services like Google and Facebook. A user registration handler is a class in Apex code that defines the logic for creating and updating user accounts based on information from an external identity provider. A user registration handler can support user provisioning and authentication via social services like Google and Facebook, by using OAuth 2.0 protocols and OpenID Connect standards to exchange user information and tokens between Salesforce and the social services.

Leverage Salesforce Identity as the identity provider to centralize authentication for both Experience Cloud and B2C Commerce in one place. Salesforce Identity is a product that allows using Salesforce as an identity provider for other applications and systems. Salesforce Identity can centralize authentication for both Experience Cloud and B2C Commerce in one place, by using single sign-on (SSO) protocols and standards to enable users to log in to both applications with the same credentials.

Option C is incorrect because leveraging B2C Commerce as the identity provider for both Storefront and the Service Portal is not possible or advisable. B2C Commerce does not support acting as an identity provider for other applications or systems, as it does not support SSO protocols or standards. Option D is incorrect because using Salesforce CDP, which automatically syncs profiles and authentication information across systems, is not a valid or available option. Salesforce CDP is a product that allows creating unified customer profiles from various data sources, but it does not sync or manage authentication information across systems. References:

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

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

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

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_interface_Auth_RegistrationHandler.htm

This answer is correct because it is a way to respond to the management team’s request to help formulate a roadmap for these new capabilities using the relationship design process. The relationship design process is a method that centers relationships as the building blocks of business and social value. It is based on four mindsets that can help design products and services from a place of compassion: compassion, intention, courage, and reciprocity. By facilitating a workshop with the management team, applying the relationship design process, a Solution Architect can help create a roadmap that aligns with business objectives and builds customer trust. References: https://www.salesforce.com/blog/how-relationship-design-works/

A Technical Design Specification is a document that describes the technical architecture and design of a solution, including the data mapping/model and systems integration. This document can help the company understand the solution that is needed and how it will meet their requirements. References: https://trailhead.salesforce.com/content/learn/modules/solution-design-for-technical-architects/define-the-technical-architecture

Option A is correct because setting up the contact object with a specific record type ‘Lead’ that mimics the standard lead object to prevent the duplicate contact from being created in Marketing Cloud is a valid consideration for setting up this multi-cloud use case. This way, the service organization can avoid creating duplicate records in Marketing Cloud when leads are converted to contacts in Sales Cloud, as Marketing Cloud will recognize them as the same subscriber based on their record type and subscriber key.

Option D is correct because ensuring that when a lead is converted to a contact that the Lead ID is mapped to a custom field on the Contact to be used as the referenced with the Subscriber ID in Marketing Cloud and avoid duplicate records is a valid consideration for setting up this multi-cloud use case. This way, the service organization can avoid creating duplicate records in Marketing Cloud when leads are converted to contacts in Sales Cloud, as Marketing Cloud will recognize them as the same subscriber based on their Lead ID and Subscriber ID.

Option B is incorrect because allowing both the lead record to generate a contact in Marketing Cloud and the contact record to generate a contact in Marketing Cloud is not a valid consideration for setting up this multi-cloud use case, as it would create duplicate records in Marketing Cloud when leads are converted to contacts in Sales Cloud, unless they have matching subscriber keys.

Option C is incorrect because enabling the ‘Prevent Duplicates for Lead Conversion’ setting when configuring Marketing Cloud Connect to prevent converted contacts from generating a duplicate contact is not a valid consideration for setting up this multi-cloud use case, as this setting does not prevent duplicates from being created in Marketing Cloud, but rather prevents duplicates from being created in Sales Cloud when leads are converted.

References:

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

[Certification - B2C Solution Architect - Trailhead]

B2C Solution Architect Certification Guide | Salesforce Ben

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

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 sequence of events ensures that all customer data is integrated across the systems and that Marketing Cloud uses Service Cloud Contact IDs as the subscriber key. This allows for a consistent and unified view of the customer across the Salesforce products. References: https://help.salesforce.com/s/articleView?id=sf.mc_co_subscriber_key_migration.htm &type=5 https://help.salesforce.com/s/articleView?id=sf.mc_co_marketing_cloud_connect.htm &type=5