What should be prioritized when assessing workflow requirements for migration?

Question

Options

• AValidating custom workflows against AEM as a Cloud Service compatibility
• BRewriting workflows for better caching
• CArchiving deprecated workflows without review
• DAutomating dispatcher configurations

• A
  80% (28)
• B
  11% (4)
• C
  3% (1)
• D
  6% (2)

Explanation

When migrating to AEM as a Cloud Service, validating custom workflows against compatibility is the critical first step because AEM as a Cloud Service has specific restrictions and deprecated features that can break existing workflow implementations - identifying these gaps early prevents costly rework post-migration.

Why the distractors are wrong:

• B - Rewriting workflows for caching is a performance concern, not a migration prerequisite; caching is handled differently in AEM as a Cloud Service and is not the primary workflow concern.
• C - Archiving deprecated workflows without review is dangerous; you must assess them first to determine if they're actively used or have dependencies before any archival decision.
• D - Dispatcher configuration is an infrastructure/CDN concern, separate from workflow migration assessment; automating it doesn't address workflow compatibility at all.

Memory tip: Think "Validate before you migrate" - the word assessing in the question is your cue that this is a pre-migration audit step. Compatibility validation is always the answer when the question asks what to assess or prioritize first in an AEM Cloud migration context.

No community discussion yet for this question.