Performance – Fundamentals Quiz 1 Questions on caching, indexing, query tuning, clientlibs, and platform responsiveness. Passing score: 70% Questions per attempt: 20Question 1When a repository query is slow, what is usually better than simply increasing JVM memory?A slow query is traversing many nodes in AEM. Which action is typically more targeted? Context: Oak performance tuning Removing all OSGi configurations Adding or correcting an Oak index and refining the query Turning off author replication Disabling the dispatcher cacheNext questionQuestion 2Reducing unused front-end payloadWhich practice best reduces unused CSS and JavaScript on AEM pages? Context: Frontend optimization Disable minification Use smaller, page-appropriate clientlib categories and load only what is needed Serve author clientlibs on publish Put all site assets into one global categoryPrevious questionNext questionQuestion 3Text response compressionWhich technique reduces transfer size for text-based HTTP responses? Context: Web performance ACL inheritance JCR versioning Workflow termination Gzip or Brotli compressionPrevious questionNext questionQuestion 4Rendering above-the-fold contentWhat CSS strategy can improve initial rendering? Context: Web performance Put CSS in repository queries Load all styles after user input Inline minimal critical CSS Disable all stylesheetsPrevious questionNext questionQuestion 5Limiting query resultsWhy should repository queries specify a result limit? Context: AEM performance Flush dispatcher cache Create indexes automatically Avoid excessive result processing Enable authoring modePrevious questionNext questionQuestion 6Publishing changed contentWhat must occur when cached published content changes? Context: AEM performance Relevant cache entries are invalidated All users clear browser history Indexes are deleted Models are renamedPrevious questionNext questionQuestion 7Efficient image deliveryWhat should a page deliver for responsive image sizes? Context: AEM performance Appropriate image renditions The original asset always Base64 full-size images Uncompressed archivesPrevious questionNext questionQuestion 8Speeding up repeated repository queriesA component repeatedly runs the same constrained query and logs traversal warnings. What is the most effective improvement? Context: Repository performance Disable query logging Move the query to client-side JavaScript Increase JVM heap only Create or tune an appropriate Oak index for the query patternPrevious questionNext questionQuestion 9Diagnosing slow pagesWhich browser tool best reveals blocking network requests? Context: Web performance Workflow Inbox Package Manager Replication console Network waterfallPrevious questionNext questionQuestion 10Restricting query scopeWhich query constraint most directly narrows a repository search area? Context: AEM performance Clientlib category Replication agent Path restriction HTTP status codePrevious questionNext questionQuestion 11Protecting page response timeWhat is the best guidance for calling third-party services during page rendering in AEM? Context: Backend rendering Store them in CRXDE variables Avoid synchronous request-path dependencies; cache or decouple them Call them synchronously from HTL whenever possible Move them into Dispatcher filtersPrevious questionNext questionQuestion 12Why is dispatcher caching usually one of the first performance levers in AEM?What makes dispatcher caching so valuable for performance? Context: Caching strategy It disables client-side assets It reduces repeated rendering work by serving cacheable responses closer to the user It removes the need for content replication It replaces the publish tier entirelyPrevious questionNext questionQuestion 13Below-fold image loadingWhat loading strategy benefits images outside the initial viewport? Context: Web performance Disabling browser cache Synchronous preload of all images Lazy loading Base64 embedding every imagePrevious questionNext questionQuestion 14Cache freshness durationWhich HTTP directive communicates how long a response may be cached? Context: HTTP caching Location Content-Type max-age RefererPrevious questionNext questionQuestion 15Repeated model computationWhat can reduce repeated expensive computation within a request? Context: AEM performance Adding workflow steps Disabling compression Request-scoped caching More HTTP redirectsPrevious questionNext questionQuestion 16Capacity validationWhat testing approach measures behavior under expected concurrent traffic? Context: Performance engineering Content authoring Unit testing only Static code formatting Load testingPrevious questionNext questionQuestion 17Resolver lifecycleWhat must code do with a service resource resolver after use? Context: AEM performance Cache it globally Pass it to the browser Close it Serialize it to JCRPrevious questionNext questionQuestion 18Long-running request workHow should expensive noninteractive work usually be performed? Context: AEM performance During clientlib loading Asynchronously in a job Inside page rendering In a servlet response filterPrevious questionNext questionQuestion 19Repeated repository accessWhat pattern should be avoided when rendering a list of many items? Context: AEM performance A bounded bulk query One query per item Reusing request data Using a path restrictionPrevious questionNext questionQuestion 20Caching most of a page with dynamic fragmentsWhat problem does Sling Dynamic Include help solve? Context: Caching strategy It lets a cacheable page shell include separately rendered dynamic fragments It converts content fragments into HTML It replaces Dispatcher with browser caching It eliminates the need for Oak indexesPrevious questionSubmit test Related
Question 1When a repository query is slow, what is usually better than simply increasing JVM memory?A slow query is traversing many nodes in AEM. Which action is typically more targeted? Context: Oak performance tuning Removing all OSGi configurations Adding or correcting an Oak index and refining the query Turning off author replication Disabling the dispatcher cacheNext question
Question 2Reducing unused front-end payloadWhich practice best reduces unused CSS and JavaScript on AEM pages? Context: Frontend optimization Disable minification Use smaller, page-appropriate clientlib categories and load only what is needed Serve author clientlibs on publish Put all site assets into one global categoryPrevious questionNext question
Question 3Text response compressionWhich technique reduces transfer size for text-based HTTP responses? Context: Web performance ACL inheritance JCR versioning Workflow termination Gzip or Brotli compressionPrevious questionNext question
Question 4Rendering above-the-fold contentWhat CSS strategy can improve initial rendering? Context: Web performance Put CSS in repository queries Load all styles after user input Inline minimal critical CSS Disable all stylesheetsPrevious questionNext question
Question 5Limiting query resultsWhy should repository queries specify a result limit? Context: AEM performance Flush dispatcher cache Create indexes automatically Avoid excessive result processing Enable authoring modePrevious questionNext question
Question 6Publishing changed contentWhat must occur when cached published content changes? Context: AEM performance Relevant cache entries are invalidated All users clear browser history Indexes are deleted Models are renamedPrevious questionNext question
Question 7Efficient image deliveryWhat should a page deliver for responsive image sizes? Context: AEM performance Appropriate image renditions The original asset always Base64 full-size images Uncompressed archivesPrevious questionNext question
Question 8Speeding up repeated repository queriesA component repeatedly runs the same constrained query and logs traversal warnings. What is the most effective improvement? Context: Repository performance Disable query logging Move the query to client-side JavaScript Increase JVM heap only Create or tune an appropriate Oak index for the query patternPrevious questionNext question
Question 9Diagnosing slow pagesWhich browser tool best reveals blocking network requests? Context: Web performance Workflow Inbox Package Manager Replication console Network waterfallPrevious questionNext question
Question 10Restricting query scopeWhich query constraint most directly narrows a repository search area? Context: AEM performance Clientlib category Replication agent Path restriction HTTP status codePrevious questionNext question
Question 11Protecting page response timeWhat is the best guidance for calling third-party services during page rendering in AEM? Context: Backend rendering Store them in CRXDE variables Avoid synchronous request-path dependencies; cache or decouple them Call them synchronously from HTL whenever possible Move them into Dispatcher filtersPrevious questionNext question
Question 12Why is dispatcher caching usually one of the first performance levers in AEM?What makes dispatcher caching so valuable for performance? Context: Caching strategy It disables client-side assets It reduces repeated rendering work by serving cacheable responses closer to the user It removes the need for content replication It replaces the publish tier entirelyPrevious questionNext question
Question 13Below-fold image loadingWhat loading strategy benefits images outside the initial viewport? Context: Web performance Disabling browser cache Synchronous preload of all images Lazy loading Base64 embedding every imagePrevious questionNext question
Question 14Cache freshness durationWhich HTTP directive communicates how long a response may be cached? Context: HTTP caching Location Content-Type max-age RefererPrevious questionNext question
Question 15Repeated model computationWhat can reduce repeated expensive computation within a request? Context: AEM performance Adding workflow steps Disabling compression Request-scoped caching More HTTP redirectsPrevious questionNext question
Question 16Capacity validationWhat testing approach measures behavior under expected concurrent traffic? Context: Performance engineering Content authoring Unit testing only Static code formatting Load testingPrevious questionNext question
Question 17Resolver lifecycleWhat must code do with a service resource resolver after use? Context: AEM performance Cache it globally Pass it to the browser Close it Serialize it to JCRPrevious questionNext question
Question 18Long-running request workHow should expensive noninteractive work usually be performed? Context: AEM performance During clientlib loading Asynchronously in a job Inside page rendering In a servlet response filterPrevious questionNext question
Question 19Repeated repository accessWhat pattern should be avoided when rendering a list of many items? Context: AEM performance A bounded bulk query One query per item Reusing request data Using a path restrictionPrevious questionNext question
Question 20Caching most of a page with dynamic fragmentsWhat problem does Sling Dynamic Include help solve? Context: Caching strategy It lets a cacheable page shell include separately rendered dynamic fragments It converts content fragments into HTML It replaces Dispatcher with browser caching It eliminates the need for Oak indexesPrevious questionSubmit test
AEM CQ5 Tutorials