A client is in the discovery process for building a React native app, which is a single codebase that runs natively on iOS and Android. The goal is to reduce development costs. The client wants to…

Question

Options

• AExperience Fragments
• BOSGi Bundles
• CSling Resource Resolution
• DContent Fragments

• A
  3% (1)
• B
  3% (1)
• C
  82% (27)
• D
  12% (4)

Explanation

Sling Resource Resolution enables AEM to expose existing content as structured JSON via URL-addressable endpoints, allowing the React Native app to consume marketing content from the AEM repository over HTTP without rebuilding or duplicating it - the app simply fetches the data it needs from AEM's Sling-resolved resource URLs, reusing content that already exists in the instance.

Experience Fragments (A) bundle content together with its presentation markup (HTML/layout) for web-based channels; a native app needs raw data, not pre-rendered HTML, making this the wrong fit. OSGi Bundles (B) are Java deployment units for server-side application logic and have no role in content delivery or reuse. Content Fragments (D) are structured, headless-friendly content pieces that are a strong candidate, but they represent new authored content rather than a mechanism for resolving and delivering the existing published marketing content already living in the AEM repository.

Memory tip: Think "Sling = Slingshot to any channel" - Sling fires existing AEM content as JSON to whatever client requests it, whether a website or a native app, with no content recreation required.

Note: Some AEM exam sources treat Content Fragments as equally or more valid for omnichannel/headless scenarios. If your study material emphasizes AEM Headless/Content Services, remember that Content Fragments + AEM's APIs is the modern recommended pattern - but for questions framing it as reusing existing published content via URL resolution, Sling Resource Resolution is the intended answer.

No community discussion yet for this question.