A company notices latency issues with delivering personalized offers through client-side delivery. What should they do to resolve this?

Question

Options

• AMove to server-side delivery.
• BOptimize mbox configurations.
• CIncrease CDN cache duration.
• DReduce profile attribute complexity.

• A
  82% (54)
• B
  3% (2)
• C
  6% (4)
• D
  9% (6)

Explanation

Moving to server-side delivery (A) resolves client-side latency because personalization logic executes on the server before the page loads, eliminating the visible flicker and render-blocking delays caused by waiting for the browser to request, receive, and apply offer content after page render.

Why the distractors fail:

• B (Optimize mbox configurations) - mboxes are client-side constructs; tuning them reduces some overhead but doesn't eliminate the fundamental latency of browser-based execution.
• C (Increase CDN cache duration) - CDN caching helps with static assets, but personalized offers are dynamic and user-specific, so they can't be meaningfully cached at the CDN layer.
• D (Reduce profile attribute complexity) - simplifying profiles may slightly speed up attribute lookups, but the bottleneck is the client-side delivery mechanism itself, not the profile data.

Memory tip: Think of client-side delivery as a waiter who brings you a blank menu and fills it in at your table - server-side delivery pre-fills the menu in the kitchen before it ever reaches you. When speed matters for personalization, move the work upstream to the server.

No community discussion yet for this question.