AD0-E117 · Question #21
A media company wants to use AEM as content hub for multiple customer touch points: - Brand-specific marketing websites hosted on AEM Sites - Single Page Applications using headless content - Native m
The correct answer is D. Brand Website and Single Page Application both connect to Content Services. Experience Fragment connects to Content Fragment. Content Services directly connects to Mobile Application. Content Fragment connects to Adobe Target.. Option D correctly centralizes all headless delivery through Content Services, which acts as the single delivery pipe to the Brand Website, SPA, and Mobile Application - ensuring content flows from one managed source. Experience Fragments reference Content Fragments (the "write-o
Question
A media company wants to use AEM as content hub for multiple customer touch points:
- Brand-specific marketing websites hosted on AEM Sites
- Single Page Applications using headless content
- Native mobile applications
- Content offers in Adobe Target
The company wants to manage its content efficiently with its small editor staff. Text should be entered and reviewed only once, then reused for all touch points. How should an Architect incorporate these requirements into a solution that leverages AEM Sites features? A. B. C. D.
Exhibits
Options
- ABrand Website connects to Experience Fragment, which also connects to Content Services. Single Page Application connects to Content Services. Experience Fragment connects to Content Fragment. Content Fragment connects to Mobile Application and Adobe Target.
- BBrand Website connects to Experience Fragment. Single Page Application connects to Content Services. Experience Fragment connects to Content Fragment. Content Fragment connects to Mobile Application and Adobe Target. No direct connection from Experience Fragment to Content Services.
- CBrand Website and Single Page Application both connect to Content Services. Experience Fragment connects to Content Fragment. Content Fragment connects to Mobile Application and Adobe Target. Content Services also connects directly to Mobile Application.
- DBrand Website and Single Page Application both connect to Content Services. Experience Fragment connects to Content Fragment. Content Services directly connects to Mobile Application. Content Fragment connects to Adobe Target.
How the community answered
(19 responses)- A5% (1)
- B21% (4)
- C26% (5)
- D47% (9)
Explanation
Option D correctly centralizes all headless delivery through Content Services, which acts as the single delivery pipe to the Brand Website, SPA, and Mobile Application - ensuring content flows from one managed source. Experience Fragments reference Content Fragments (the "write-once" structured content atoms), and Content Fragments integrate directly with Adobe Target for content offers, satisfying every touch point with a single authoring workflow.
Option A is wrong because it shows Experience Fragment → Content Services, but Experience Fragments are AEM Sites composition components, not headless delivery artifacts - they should not connect to Content Services.
Option B is wrong because it routes Content Fragment → Mobile App directly, bypassing Content Services entirely; all headless consumers (SPA, mobile) must go through Content Services, not raw Content Fragments.
Option C is wrong because it creates two redundant, conflicting paths to Mobile App - both Content Fragment → Mobile App and Content Services → Mobile App - which violates the clean headless architecture pattern where only Content Services delivers to mobile.
Memory tip: Think of Content Services as the "headless highway" - everything digital (SPA, Mobile) drives on it, and Content Fragments are the cargo. Experience Fragments only look down to Content Fragments (they consume them for page layout), never sideways to Content Services. Adobe Target is the one exception that connects directly to Content Fragments via its dedicated integration.
Topics
Community Discussion
No community discussion yet for this question.