A client wishes to serve Adobe Target content to their mobile application. They prefer to manage the content using the Adobe Target UI and have the mobile application developers apply the necessary…

Question

Options

• ABuild JSON Offers within Adobe Target.
• BAdd HTML offer using the Visual Experience Composer.
• CExpose Experience Fragments to the mobile application.
• DUse inline editing tools for mobile app development.

• A
  80% (39)
• B
  6% (3)
• C
  2% (1)
• D
  12% (6)

Explanation

JSON Offers (A) are the right recommendation because they allow content to be authored and managed entirely within the Adobe Target UI while delivering raw, format-agnostic data that mobile developers can consume and style however they choose - a clean separation of content from presentation.

B is wrong because the Visual Experience Composer (VEC) is designed for web browsers and generates HTML/CSS; it cannot render in a native mobile app environment and produces markup that ties content to a specific visual format.

C is wrong because Experience Fragments are structured AEM content components (typically HTML-based) intended for web delivery; while they can be exported, they bundle formatting with content, violating the client's requirement to let mobile developers handle all design.

D is wrong because inline editing tools are web-based authoring features within the VEC - they have no role in native mobile app development.

Memory tip: Think "JSON = just the skeleton." Mobile developers want raw data bones they can dress up themselves; JSON Offers deliver exactly that, while HTML/VEC/Fragments arrive pre-dressed for the web.

No community discussion yet for this question.