What is the primary goal of reviewing deprecated capabilities in an AEM migration?

Question

Options

• ATo eliminate all legacy workflows
• BTo determine compatibility with AEM as a Cloud Service
• CTo reduce the overall migration timeline
• DTo prepare for caching optimizations

• A
  3% (1)
• B
  90% (36)
• C
  8% (3)

Explanation

Reviewing deprecated capabilities during an AEM migration exists specifically to identify features, APIs, or components that are no longer supported in AEM as a Cloud Service - making B the correct answer. Without this review, you risk deploying code that simply won't work in the cloud environment, causing runtime failures post-migration.

Why the distractors are wrong:

• A - Eliminating legacy workflows may be a byproduct of the review, but it's not the primary goal; you're assessing compatibility, not targeting workflows specifically.
• C - Compatibility analysis often extends timelines by uncovering required refactoring work, so this is nearly the opposite of reality.
• D - Caching optimizations are a separate concern (CDN/Dispatcher configuration) with no direct connection to deprecated capabilities.

Memory tip: Think "deprecated = deprecated from the target platform." The word "deprecated" is your clue - you're checking what the destination (AEM as a Cloud Service) no longer accepts, which is purely a compatibility question.

No community discussion yet for this question.