Q: 7
A Data Cloud consultant recently added a new data source and mapped some of the data to a new
custom data model object (DMO)
that they want to use for creating segments. However, they cannot view the newly created DMO
when trying to create a new segment.
What is the cause of this issue?
Options
Discussion
Option B If the DMO is not set as Profile category, segmentation won't see it. That specific setting is easy to miss.
C vs D for me. If the DMO isn't related to Individual, you sometimes can't segment on it, right? Think C could explain it if relationships are missing, but not 100% sure. Open to being wrong.
B is the right call since segmentation needs a DMO with the Profile category, not just any custom object. Even if data's ingested and relationships are set, wrong category keeps it hidden from segment builder. Pretty sure that's the catch but open if someone saw an exception.
Not D, it's B. The Profile category is needed for segmentation, A is a common mix-up here.
Had something like this in a mock, it's definitely B.
Saw this on a practice test, it's B. The custom DMO needs to be in the Profile category for segmentation.
B tbh. Official guide and practice exams both say DMOs must be Profile category for segmentation to work in Data Cloud.
Hard to say, B here. Only DMOs with the Profile category can be used for segmentation, the others just won't show up.
Hmm, I don't think it's D, that's a common trap. B is right, seen similar question before where only setting Profile category made the DMO show up.
B imo. In Data Cloud, you have to set the DMO as Profile category or it won't show up for segmentation, doesn't matter if the data is mapped or ingested. Saw this on official practice questions too, but open to other views.
Be respectful. No spam.
