What action should you perform to make sure the merged FullName field contains the most trusted data available?

You are a Customer Data Platform Specialist. The marketing team wants to send personalized marketing emails to customers, but the customer FullName attribute has not been correctly populated as part of the profile unification process.

You update the Map process to include the loyalty.member.fullname, ecom.member.fullname, and cclubcust.member.full_name fields. Then, you map the fields to the Person.FullName semantic type. Audience insights automatically merges these fields into the FullName attribute on the Merge page.

What action should you perform to make sure the merged FullName field contains the most trusted data available?
A . Edit the merged FullName field and combine fields by most recent based on timestamp in the source entity.
B . Edit the merged FullName field and combine fields by least recent based on timestamp in the source entity.
C . Separate the fields in the merged FullName field, create a new field, and add attributes in priority order.
D . Edit the merged FullName field, combine fields by importance, and manually rank the source entities.

Answer: D

Explanation:

Adding Full Name field to the unified customer record

Full Name is a merged field with the following merging policy

a. loyalty.member.fullname

b. ecom.member.fullname

c. cclubcust.csv.full_name

Reference: https://docs.microsoft.com/en-us/dynamics365/customer-insights/audience-insights/merge-entities

Latest MB-260 Dumps Valid Version with 50 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments