Headless AEM – Fundamentals Quiz 1 Practice GraphQL, Content Fragments, persisted queries, caching, and API security. Passing score: 70% Questions per attempt: 20Question 1Filtering fragment resultsWhat GraphQL capability limits returned fragments based on field values? Context: Headless AEM Filter Subscription Alias MutationNext questionQuestion 2Localized fragment contentHow is language-specific headless content commonly organized in AEM? Context: Headless AEM Workflow inboxes Publish agents Separate image presets Language root foldersPrevious questionNext questionQuestion 3Why are Content Fragment Models important for headless delivery?What do Content Fragment Models primarily provide in a headless AEM setup? Context: Headless modeling A package deployment mechanism A replacement for dispatcher farms A way to define structured content types and fields for API delivery A binary-only asset workflowPrevious questionNext questionQuestion 4Large result setsWhich GraphQL approach retrieves a large fragment list in smaller portions? Context: Headless AEM Rendition generation Tagging Replication PaginationPrevious questionNext questionQuestion 5Referencing related contentWhich Content Fragment Model field type links one fragment to another? Context: Headless AEM Boolean Date and Time Single Line Text Fragment ReferencePrevious questionNext questionQuestion 6Classifying fragmentsWhich feature categorizes Content Fragments for discovery and filtering? Context: Headless AEM Launches Workflows Renditions TagsPrevious questionNext questionQuestion 7Controlled field valuesWhich model field type is suitable for a predefined set of editorial choices? Context: Headless AEM Enumeration Tab Placeholder Fragment Reference Multi Line TextPrevious questionNext questionQuestion 8Publishing referenced contentWhen publishing a fragment that references another fragment, what should also be considered? Context: Headless AEM Running a form workflow Publishing the referenced fragment Adding a page template Creating an image presetPrevious questionNext questionQuestion 9AEM approach to multilingual headless contentFor localized headless delivery, what is the common AEM strategy? Context: Localization Create localized fragment copies under language-aligned structures while reusing the same model Store translations only in Dispatcher headers Keep one fragment in one language and translate at request time Use separate codebases per languagePrevious questionNext questionQuestion 10Allowed fragment modelsWhat controls which Content Fragment Models can be used in an Assets folder? Context: Headless AEM GraphQL query Publish agent Folder content policy Dispatcher rulePrevious questionNext questionQuestion 11Why persisted GraphQL queries are preferredWhat is a major advantage of using persisted GraphQL queries in headless AEM? Context: API delivery They support cacheable GET endpoints and reduce exposure to uncontrolled query shapes They allow arbitrary client-side query text in production They bypass content modeling They work only on authorPrevious questionNext questionQuestion 12GraphQL schema sourceWhat primarily determines the fields available in AEM's GraphQL schema? Context: Headless AEM Content Fragment Models Asset processing profiles Forms themes Page templatesPrevious questionNext questionQuestion 13Requesting selected fieldsWhat lets a client request only the content fields it needs from AEM? Context: Headless AEM Replication queue Asset workflow GraphQL query selection Metadata schemaPrevious questionNext questionQuestion 14Using content fragment variationsWhy are Content Fragment variations useful in a headless implementation? Context: Structured content They provide alternate channel- or audience-specific content from the same base fragment They force synchronous publication They change Dispatcher invalidation rules They replace GraphQL schemasPrevious questionNext questionQuestion 15Securing content APIsWhat must be configured so a client can access protected headless content? Context: Headless AEM A document template A Smart Crop A form theme Appropriate API access permissionsPrevious questionNext questionQuestion 16Caching API responsesWhat can improve repeated headless API request performance at the delivery layer? Context: Headless AEM Using a workflow inbox Creating asset versions Adding more author users Caching query responsesPrevious questionNext questionQuestion 17Headless delivery formatWhat data format is typically returned by an AEM GraphQL API? Context: Headless AEM JSON PDF CSV XML onlyPrevious questionNext questionQuestion 18Why are persisted GraphQL queries commonly used in headless AEM?Which benefit best explains the use of persisted queries? Context: Headless AEM They provide controlled, cache-friendly query endpoints instead of sending arbitrary full query strings from clients They remove the need for Content Fragments They replace Sling Models on author They disable CDN usagePrevious questionNext questionQuestion 19Risk of renaming model fieldsWhat is a likely consequence of renaming a field in a Content Fragment Model used by GraphQL clients? Context: Schema evolution It only affects author UI colors It can change the generated schema and break existing client queries No client impact because GraphQL field names stay frozen It disables persisted queries permanentlyPrevious questionNext questionQuestion 20GraphQL endpointWhat does an AEM GraphQL endpoint provide? Context: Headless AEM A folder for DAM assets A form submission handler A workflow model An API location for executing GraphQL queriesPrevious questionSubmit test Related
Question 1Filtering fragment resultsWhat GraphQL capability limits returned fragments based on field values? Context: Headless AEM Filter Subscription Alias MutationNext question
Question 2Localized fragment contentHow is language-specific headless content commonly organized in AEM? Context: Headless AEM Workflow inboxes Publish agents Separate image presets Language root foldersPrevious questionNext question
Question 3Why are Content Fragment Models important for headless delivery?What do Content Fragment Models primarily provide in a headless AEM setup? Context: Headless modeling A package deployment mechanism A replacement for dispatcher farms A way to define structured content types and fields for API delivery A binary-only asset workflowPrevious questionNext question
Question 4Large result setsWhich GraphQL approach retrieves a large fragment list in smaller portions? Context: Headless AEM Rendition generation Tagging Replication PaginationPrevious questionNext question
Question 5Referencing related contentWhich Content Fragment Model field type links one fragment to another? Context: Headless AEM Boolean Date and Time Single Line Text Fragment ReferencePrevious questionNext question
Question 6Classifying fragmentsWhich feature categorizes Content Fragments for discovery and filtering? Context: Headless AEM Launches Workflows Renditions TagsPrevious questionNext question
Question 7Controlled field valuesWhich model field type is suitable for a predefined set of editorial choices? Context: Headless AEM Enumeration Tab Placeholder Fragment Reference Multi Line TextPrevious questionNext question
Question 8Publishing referenced contentWhen publishing a fragment that references another fragment, what should also be considered? Context: Headless AEM Running a form workflow Publishing the referenced fragment Adding a page template Creating an image presetPrevious questionNext question
Question 9AEM approach to multilingual headless contentFor localized headless delivery, what is the common AEM strategy? Context: Localization Create localized fragment copies under language-aligned structures while reusing the same model Store translations only in Dispatcher headers Keep one fragment in one language and translate at request time Use separate codebases per languagePrevious questionNext question
Question 10Allowed fragment modelsWhat controls which Content Fragment Models can be used in an Assets folder? Context: Headless AEM GraphQL query Publish agent Folder content policy Dispatcher rulePrevious questionNext question
Question 11Why persisted GraphQL queries are preferredWhat is a major advantage of using persisted GraphQL queries in headless AEM? Context: API delivery They support cacheable GET endpoints and reduce exposure to uncontrolled query shapes They allow arbitrary client-side query text in production They bypass content modeling They work only on authorPrevious questionNext question
Question 12GraphQL schema sourceWhat primarily determines the fields available in AEM's GraphQL schema? Context: Headless AEM Content Fragment Models Asset processing profiles Forms themes Page templatesPrevious questionNext question
Question 13Requesting selected fieldsWhat lets a client request only the content fields it needs from AEM? Context: Headless AEM Replication queue Asset workflow GraphQL query selection Metadata schemaPrevious questionNext question
Question 14Using content fragment variationsWhy are Content Fragment variations useful in a headless implementation? Context: Structured content They provide alternate channel- or audience-specific content from the same base fragment They force synchronous publication They change Dispatcher invalidation rules They replace GraphQL schemasPrevious questionNext question
Question 15Securing content APIsWhat must be configured so a client can access protected headless content? Context: Headless AEM A document template A Smart Crop A form theme Appropriate API access permissionsPrevious questionNext question
Question 16Caching API responsesWhat can improve repeated headless API request performance at the delivery layer? Context: Headless AEM Using a workflow inbox Creating asset versions Adding more author users Caching query responsesPrevious questionNext question
Question 17Headless delivery formatWhat data format is typically returned by an AEM GraphQL API? Context: Headless AEM JSON PDF CSV XML onlyPrevious questionNext question
Question 18Why are persisted GraphQL queries commonly used in headless AEM?Which benefit best explains the use of persisted queries? Context: Headless AEM They provide controlled, cache-friendly query endpoints instead of sending arbitrary full query strings from clients They remove the need for Content Fragments They replace Sling Models on author They disable CDN usagePrevious questionNext question
Question 19Risk of renaming model fieldsWhat is a likely consequence of renaming a field in a Content Fragment Model used by GraphQL clients? Context: Schema evolution It only affects author UI colors It can change the generated schema and break existing client queries No client impact because GraphQL field names stay frozen It disables persisted queries permanentlyPrevious questionNext question
Question 20GraphQL endpointWhat does an AEM GraphQL endpoint provide? Context: Headless AEM A folder for DAM assets A form submission handler A workflow model An API location for executing GraphQL queriesPrevious questionSubmit test
AEM CQ5 Tutorials