Digital Asset Management and Content Reuse
The Assets console is the DAM. Practitioners must understand folders vs. collections (folders are storage; collections are curated groupings across folders), metadata schemas (which fields appear on an asset), renditions (auto-generated sizes and formats), and processing profiles (applied on upload to generate renditions or smart crops). Know that tags provide taxonomy via the Tagging console and are used for search and personalization.
Smart Tags and Smart Crops use AI services (configured via Adobe I/O/IMS). Know that Smart Tags require configuration and do not appear automatically in a fresh instance. Dynamic Media serves responsive, optimized, and interactive media; without it, assets use standard renditions.
Reuse mechanisms to distinguish: Experience Fragments (page-level reusable content), Content Fragments (structured data, headless), Assets referenced via the Assets component or Content Fragment component, and Live Copies for multi-site reuse. A common trap is assuming editing an asset in one place updates every reference automatically - it does update references to the same asset, but copied assets are independent.
Worked example: a brand wants every image cropped consistently across desktop and mobile. The answer is a processing profile with smart crop renditions applied at upload, not manual cropping per asset. Another trap: confusing collections (curation) with folders (structure) when a question asks how to group assets for a campaign without moving them.