A data engineer is tasked with creating a streaming segment, and the segment definition must include existing audiences and a page view web event. After selecting the evaluation method, an error occur

Question

Options

• AThe segment definition includes a combination of an audience and multiple page view events (last
• BThe segment definition includes a combination of an audience, a page view event (any time), and
• CThe segment definition includes a combination of an audience and a page view event (last 24hrs).
• DThe segment definition includes a combination of an audience in multiple page view events (last

• A
  72% (18)
• C
  8% (2)
• D
  20% (5)

Explanation

Options A and B are correct because both describe segment definitions that violate the constraints of streaming evaluation. Streaming segmentation typically supports only a single incoming event with a bounded time window per segment definition - including multiple page view events (as in A) immediately disqualifies it from streaming. Option B introduces a page view event with an "any time" window (plus an additional element), which is unsupported by streaming because real-time evaluation cannot scan unbounded historical data; this forces the engine to fall back to batch.

Option C is incorrect because a single page view event scoped to "last 24 hours" combined with an audience is a valid streaming configuration - the time window is bounded and there is only one event, meeting streaming eligibility requirements. Option D, while superficially similar to A, describes a different structural combination (likely "audiences within multiple events" rather than "audience + multiple events") that may not represent a real constraint violation the way A does.

Memory tip: Think of streaming segmentation as a strict bouncer with two rules - one event only and no "any time" windows. If your definition breaks either rule (or adds something beyond those limits), you're kicked to batch.

No community discussion yet for this question.