What should the Solution Architect keep in mind to avoid data exchange issues after implementation?

Northern Trail Outfitters (NTO) recently implemented the Service Cloud Connector between B2C Commerce and Service Cloud. They released a new feature that allows customers to add their favorite National Park to their profile. After an attempt to help a customer, a service agent informs the Director of IT that they cannot see or update the new National Park value on the profile in the Service Cloud console.

What should the Solution Architect keep in mind to avoid data exchange issues after implementation?
A . Check the fieldMapping custom settings in Service Cloud to confirm the nationalParks attribute was mapped from the Commerce Profile to the Service Contact
B . Check the field-level security for nationalParks is set to read only
C . Check that the nationalParks value was added to the Profile Custom Object in B2C Commerce
D . Check that the nationalParks value is defined in the json of the B2C Commerce Customer Data API

View Answer

Answer: A

Explanation:

The fieldMapping custom settings in Service Cloud define how the attributes from the Commerce Profile are mapped to the fields on the Service Contact. If the nationalParks attribute was not mapped, then the service agent would not be able to see or update it in the Service Cloud console.

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