What actions can be performed when building segments in Adobe RT-CDP? (Select two.)

Question

Options

• ACombine multiple data sources using unified schemas.
• BApply data governance policies during segment creation.
• CDefine custom attributes for segmentation criteria.
• DExport segments directly without activation workflows.

• A
  82% (37)
• B
  11% (5)
• D
  7% (3)

Explanation

When building segments in Adobe Real-Time CDP, you can combine multiple data sources using unified schemas (A) - RT-CDP's core value is its ability to merge data from disparate sources (CRM, web, mobile, etc.) into a unified customer profile via XDM (Experience Data Model), which is the foundation for segmentation. You can also define custom attributes as segmentation criteria (C), allowing marketers to build audiences based on profile attributes, behavioral events, or computed fields specific to their business.

Why B is wrong: Data governance policies in RT-CDP operate at the activation/export layer (via DULE - Data Usage Labeling and Enforcement), not during segment creation itself. The segment builder doesn't enforce governance inline.

Why D is wrong: RT-CDP requires segments to go through destinations and activation workflows to be exported - there is no direct export bypass. This is by design to ensure governance and consent controls are applied.

Memory tip: Think of RT-CDP's segment builder as a "who + what" tool - who the customer is (unified schema = A) and what defines them (custom attributes = C). Governance and export are downstream concerns that happen after you define your audience.

No community discussion yet for this question.