Which steps should be taken to prepare an asset migration strategy? (Choose three)

Question

Options

• AAudit the current asset repository for metadata completeness
• BOptimize asset renditions for cloud processing
• CAutomate asset ingestion workflows
• DValidate dispatcher configurations before migration
• EDevelop a fallback plan for incompatible assets

• A
  81% (13)
• C
  6% (1)
• D
  13% (2)

Explanation

Preparing an asset migration strategy requires auditing current metadata (A) to understand what exists and identify gaps before moving anything - you can't migrate what you don't understand. Optimizing renditions for cloud processing (B) ensures assets are in the right formats and sizes for the target environment, preventing post-migration rework. Developing a fallback plan for incompatible assets (E) is essential risk management - some assets will inevitably not migrate cleanly, and a strategy needs to account for that.

C is wrong because automating ingestion workflows is a post-migration operational concern, not a preparation step for the migration itself. D is wrong because dispatcher configuration (a CDN/caching layer concept in AEM) is an infrastructure concern unrelated to planning the asset migration strategy - it's a deployment concern, not a data migration one.

Memory tip: Think A-B-E = Assess, Build-ready, Escape-hatch - audit what you have, make it ready for the destination, and plan your way out if things break. Any answer about automation or infrastructure config is a distractor because strategy prep is about data quality and risk, not operational tooling.

No community discussion yet for this question.