What actions should be taken if a critical component is identified as deprecated during the review process in AEM Cloud Service migration?

Question

Options

• AExclude the deprecated component from the migration plan and proceed without it.
• BPostpone the migration until Adobe releases an update for the deprecated component.
• CReport the deprecated component and recommend an alternative or upgraded solution.
• DAutomatically replace the deprecated component with the latest version during migration.

• A
  5% (2)
• B
  7% (3)
• C
  71% (30)
• D
  17% (7)

Explanation

Option C is correct because during a migration review, the appropriate professional response is to document deprecated components and recommend alternatives - this ensures stakeholders are informed and can make decisions, rather than silently ignoring, delaying, or blindly replacing components.

• A is wrong because excluding a deprecated component without reporting it hides a known risk and could break functionality that depends on it.
• B is wrong because postponing migration indefinitely for an Adobe update is impractical and outside the migration team's control - migration planning shouldn't be held hostage to an uncertain release timeline.
• D is wrong because automatically replacing a deprecated component assumes a safe 1:1 swap exists, which may not be true; replacement decisions require human review and testing to avoid regressions.

Memory tip: Think of the migration team's role as a consultant, not an autocrat - you report and recommend (C), you don't unilaterally exclude (A), delay indefinitely (B), or auto-replace (D).

No community discussion yet for this question.