A customer has been using the AEM ContextHub feature Cut wants to extend it by adding an additional API. The additional API will be used to allow digital marketers to target banners based on CRM…

Question

Options

• AA ContextHub Ul module
• BA custom session store candidate
• CA custom persisted store candidate
• DA custom ISONP store candidate

• A
  84% (31)
• B
  5% (2)
• C
  3% (1)
• D
  8% (3)

Explanation

Option A is correct because a ContextHub UI Module is the component that exposes an interface - an "API surface" - through which digital marketers can interact with, simulate, and target based on data (like CRM data) within the current visit context. The UI Module is specifically designed to surface store data to business users (marketers), enabling them to see and manipulate targeting criteria directly in the ContextHub toolbar.

Why the distractors are wrong:

• B (Custom session store candidate) stores data only for the current browser session - useful for storing CRM data temporarily, but it's a developer-facing data layer, not a marketer-facing API or interface.
• C (Custom persisted store candidate) persists data across sessions (e.g., in localStorage), which contradicts the "current visit" requirement - CRM visit data should not carry over between sessions.
• D (Custom JSONP store candidate) fetches external data via JSONP calls - again a data retrieval mechanism for developers, not the marketers' targeting interface.

Memory tip: Think of the layers this way - stores (session, persisted, JSONP) are for developers to load and hold data, while UI Modules are for marketers to see and act on that data. The question says "digital marketers" need the API - that points directly to a UI Module.

No community discussion yet for this question.