AEM Assets Developer Professional study guide
AEM Assets Developer Professional · Work through your exam, one topic at a time.
The AEM Assets Developer Professional credential is aimed at developers and technical practitioners who build and maintain digital asset management solutions on Adobe Experience Manager. Adobe positions Experience Manager as a system for "content management and digital asset management," and this exam tests whether you can work competently across that stack rather than just administer a UI. The blueprint is organized into four equally weighted domains: fundamentals and architecture (25%), ingestion, processing, and metadata (25%), organization, search, and collections (25%), and delivery, integrations, and customization (25%). Because the domains split evenly, there is no safe area to skip; a weak domain costs as much as any other. The AEM Assets Developer Professional study guide has 4 sections and about 1,174 words.
01AEM Assets Fundamentals and Architecture
AEM Assets is built on the JCR repository (Oak) and served through Sling, so every asset is a node with a jcr:primaryType of dam:Asset . The critical structural fact: an asset node contains a jcr:content child, which contains a metadata node and a renditions node.
276 words, about 1 min02Asset Ingestion, Processing, and Metadata
Ingestion has several entry points: the Assets UI upload, desktop app, API (HTTP/ /api/assets ), and bulk import. Each triggers processing.
303 words, about 2 min03Asset Organization, Search, and Collections
Organization happens through folder hierarchy, tags (the cq:tags taxonomy under /content/cq:tags ), and collections. Know the three collection types: static collections (manual membership, stored as sling:members or references), smart collections (dynamic, driven by a saved search query), and the distinction that smart collections re-evaluate membership at query time while static ones are fixed.
281 words, about 1 min04Asset Delivery, Integrations, and Customization
Delivery centers on renditions and the content delivery model. In standard Assets you reference a specific rendition URL (e.g., the web rendition) served through Sling or a dispatcher/CDN.
314 words, about 2 min