Which audience rule evaluates visitor conditions in real time during an mbox request?

The correct answer is C. Real-time audience rules. Real-time audience rules (C) are specifically designed to evaluate visitor conditions during the mbox request itself, meaning the evaluation happens live at the moment of the request before content is served - this is exactly what "real-time" means in this context. Profile script

Solution Design

Question

Options

AProfile scripts
BOffline segmentation
CReal-time audience rules
DBatch processing

How the community answered

(31 responses)

A
6% (2)
B
16% (5)
C
74% (23)
D
3% (1)

Explanation

Real-time audience rules (C) are specifically designed to evaluate visitor conditions during the mbox request itself, meaning the evaluation happens live at the moment of the request before content is served - this is exactly what "real-time" means in this context.

Profile scripts (A) run server-side to compute and store attributes on a visitor's profile, but they feed into audience evaluation rather than being the audience rule mechanism itself. Offline segmentation (B) processes data in batch outside of the live request cycle, making it inherently unsuitable for real-time decisions. Batch processing (D) is similarly asynchronous and scheduled - it cannot act on conditions present at the moment of an individual mbox call.

Memory tip: Think of the mbox as a checkpoint - only real-time rules are standing at that checkpoint to inspect the visitor as they pass through. Anything "batch" or "offline" already went home before the visitor arrived.

Topics

#real-time audience rules#mbox request#audience segmentation#visitor conditions

Community Discussion

No community discussion yet for this question.

Full AD0-E408 Practice