You are a marketing manager for a retail company that uses Dynamics 365 Customer Insights. You want to create a segment of customers who have not made a purchase in the last 90 days and who have a high predicted churn score. You have already set up a predictive churn model. However, when you try to create the segment using the churn score, you notice that the churn score field is not available in the segment builder. What is the most likely reason?
Model must be published to use outputs.
Why this answer
The churn score field is generated by the predictive churn model and only becomes available in the segment builder after the model has been published. Until the model is published, the churn score is not written to the customer entity, so the field does not appear as a selectable attribute. Publishing the model finalizes the scores and makes them available for segmentation.
Exam trap
The trap here is that candidates may assume the churn model is automatically available for segmentation once trained, but Microsoft Dynamics 365 requires an explicit publish action to make the output fields accessible in the segment builder.
How to eliminate wrong answers
Option B is wrong because a model that is still training would not produce scores, but the question states the model has already been set up, implying training is complete; the issue is that the field is missing, not that scores are pending. Option C is wrong because the churn model uses the same unified customer data within Customer Insights, and a different data source would not prevent the churn score field from appearing in the segment builder—it would simply use that source's data for scoring. Option D is wrong because data unification is a prerequisite for running the churn model, and if data were not unified, the model would not have been set up successfully; the field's absence is due to the publication step, not unification.