B makes sense here since without 'View All' in the source CRM org, Data Cloud can't display the custom object when you're adding a new data stream. I've tripped over this before, so I think it's correct but happy to hear other takes.
I don’t think it’s B, gotta be A in this case. Unified Link Individual is key for connecting the unified profile to every related source record and grabbing all those Sales Orders. B skips that link which means you’d miss transactions from merged profiles. Pretty sure this sequence shows up a lot on exam prep sites.
Probably A, since Unified Link Individual is what connects the unified profile to all related source Individuals and their Sales Orders. Just to confirm, is the requirement specifically for all linked transactions across merged profiles? If they only needed direct transactions without accounting for linked identities I might pick B instead.
Formula fields tripped me up before, but for standard fields it's all about streaming. Had something like this in a mock-D fits because CDC lets the CRM Connector stream those changes almost instantly into Data Cloud. C is just formulas, not regular fields. Pretty sure D is the right call, but open to correction.
Streaming insight is the way to go here, so B. It tracks behavior in near real-time across a rolling window like 24 hours. Calculated insight (C) is more for batch/calculated stuff, not event triggers this tight. Pretty sure about B but open to pushback if I missed something.
I thought B made sense since geography can split up audiences in both systems, so filtering segments by regions should get the counts closer. Maybe I'm overthinking it, but I don't see why Business Units would matter as much. Open to pushback!
Yep, D is the way to go. Filtering by Business Units matches what MC picks up after activation, so your segment size and data extension count line up. Seen similar logic in review questions. Unless I missed something obvious here?