A client has recently upgraded their Adobe Experience Manager (AEM) instance to version 6.5 and would like to utilize Experience Fragments (XFs) in Adobe Target. Which two actions are prerequisites fo

Question

Options

• AConfigure the AEM Link Externalizer.
• BConfigure at.js to load in the site header template in AEM.
• CEnable Response Tokens in Adobe Target.
• DAdd the Cloud Services for Adobe Target in AEM.
• EProvision Analytics for Target (A4T) Integration.

• A
  70% (26)
• B
  16% (6)
• C
  5% (2)
• E
  8% (3)

Explanation

Exporting Experience Fragments to Adobe Target requires two foundational setup steps: A (Link Externalizer) ensures all links within the XF are converted from relative to absolute URLs, since Target renders content outside AEM's domain and needs fully qualified paths to function correctly. D (Adobe Target Cloud Services) establishes the authenticated connection between AEM and Target - without it, AEM has no channel through which to publish XFs to Target at all.

Why the distractors are wrong:

• B (at.js in header): at.js handles Target activity delivery on the live site; it's irrelevant to the AEM-to-Target export pipeline.
• C (Response Tokens): These pass metadata back from Target to the browser for analytics/debugging - useful post-integration, but not a prerequisite.
• E (A4T): Analytics for Target is an optional reporting enhancement; it has no role in the XF export workflow.

Memory tip: Think "connect then correct" - you must connect AEM to Target (Cloud Services) and correct the URLs (Link Externalizer) before any XF can make the trip. Both are about making the export technically possible, not about what happens after delivery.

No community discussion yet for this question.