A client's AEM environment contains a large repository of assets with inconsistent metadata. During the migration process, what should you prioritize to ensure asset compatibility in the cloud?

Question

Options

• AUse the default metadata configuration for all assets
• BAudit and standardize metadata before migration
• CTransfer assets without modifying metadata and address issues later
• DConfigure dispatcher rules to manage metadata inconsistencies

• A
  4% (1)
• B
  71% (17)
• C
  17% (4)
• D
  8% (2)

Explanation

Auditing and standardizing metadata before migration (B) is the right approach because inconsistent metadata causes broken references, failed renditions, and search/taxonomy issues once assets land in AEM as a Cloud Service - problems that are far harder to fix post-migration at scale. Option A is wrong because default metadata configurations won't reconcile existing inconsistencies; they simply apply a template going forward, leaving corrupt or mismatched fields intact. Option C defers technical debt into production, where fixing metadata on a live cloud repository is riskier and more disruptive than doing it in a controlled pre-migration window. Option D is a red herring - Dispatcher handles HTTP routing and caching, not asset metadata; it has no role in resolving metadata quality issues.

Memory tip: Think "clean before you carry" - just like you wouldn't move dirty dishes into a new kitchen, you don't migrate messy metadata into the cloud. The word standardize in option B maps directly to the word compatibility in the question stem.

No community discussion yet for this question.