A client's AEM environment uses a large number of custom workflows that involve deprecated functionality. What is the most effective approach to address this during assessment?

Question

Options

• ADisable all custom workflows before migration
• BReview and refactor custom workflows to align with supported capabilities
• CMigrate the workflows without any modifications
• DImplement temporary solutions for unsupported features

• A
  20% (6)
• B
  67% (20)
• C
  10% (3)
• D
  3% (1)

Explanation

Reviewing and refactoring custom workflows (B) is correct because it ensures continuity of business processes while modernizing them to use supported, stable APIs - this is the only approach that preserves functionality AND resolves the underlying technical debt before migration.

Why the distractors fail:

• A - Disabling workflows eliminates business processes entirely, which is rarely acceptable and solves nothing long-term.
• C - Migrating without modification carries deprecated functionality into the new environment, creating instability and future breakage.
• D - Temporary workarounds just defer the problem, accumulating more technical debt post-migration.

Memory tip: Think of it as "fix the foundation, not just the walls" - deprecated code is a structural issue that must be resolved (refactored) before you build on top of it, not patched or ignored.

No community discussion yet for this question.