Content Modeling, Content Fragments, and Experience Fragments
Content modeling is about designing reusable, channel-agnostic content. A candidate must distinguish content fragments (structured data defined by a content fragment model, delivered via API) from experience fragments (reusable layout and presentation, exported as HTML or delivered as components). Understand the content fragment model editor, data types, variations, and the role of the fragment's master variation. Know the GraphQL and REST (Assets HTTP API) delivery paths, persisted queries, and how the fragment reference component embeds fragments in pages.
Key concepts include the relationship between content fragment models and the configuration (conf) folder, the difference between a fragment and a page, and how experience fragments support variations for personalization and multi-channel reuse. Understand that experience fragments carry presentation and can be exported to Adobe Target, while content fragments carry pure content and should not encode layout. Also know the JSON exporter and model-driven APIs for headless delivery.
Traps include questions that treat content fragments as page replacements, or that assume fragments can be authored without a model. Another common trap confuses fragment variations (content variations) with experience fragment variations (presentation variations). Expect questions on where models live (conf, not apps) and on why a fragment field does not appear in GraphQL (model not enabled or not published). Also watch for the misconception that experience fragments are ideal for large structured datasets; they are not.
Rule of thumb: if the content must be reused across channels and rendered by external systems, use content fragments and an API. If it must preserve layout and be reused as a block, use experience fragments. Worked example: an article body consumed by a mobile app should be a content fragment with a GraphQL persisted query, not an experience fragment.