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 data for the current visit. What should the Business Practitioner recommend that the customer create?

To integrate external data, such as from a CRM, into AEM for targeting purposes, a ContextHub store must be created. The store is responsible for fetching the data via an API and making it available to the targeting engine. The requirement specifies that the data is for the "current visit," which directly corresponds to the lifecycle of a session store (ContextHub.Store.SessionStore). This type of store maintains data only for the duration of the browser session, which is the most appropriate and efficient method for this use case.

A. A ContextHub UI module: A UI module is a user interface component used to display data from a store in the ContextHub toolbar. It does not handle data fetching or storage for targeting.
C. A custom persisted store candidate: A persisted store saves data across browser sessions (e.g., using local storage). This is unnecessary as the requirement is only for the "current visit."
D. A custom JSONP store candidate: This is a specific type of store for cross-domain data retrieval. While the CRM API might require it, the fundamental component needed is a session store, making this answer too specific and potentially incorrect.

1. Adobe Experience Manager as a Cloud Service Documentation, "Extending ContextHub": This document outlines the process of extending ContextHub, stating, "Create ContextHub stores to persist user data... ContextHub provides the following types of stores that you can use as a basis for your store: ... ContextHub.Store.SessionStore." This confirms that creating a store is the correct approach for adding a new data source. The description of SessionStore aligns with the "current visit" requirement.

Source: Adobe Experience Manager Documentation > Sites > Personalizing Content > ContextHub > Extending ContextHub.

2. Adobe Experience Manager as a Cloud Service Documentation, "Adding a UI Module": This page clarifies the role of UI modules: "Add a UI module to the ContextHub toolbar to display data from a ContextHub store." This supports the reasoning that a UI module is for data presentation, not for data acquisition and management for targeting, which is the core task described in the question.

Source: Adobe Experience Manager Documentation > Sites > Personalizing Content > ContextHub > Adding a UI Module.