During the assessment phase, you discover that the existing dispatcher configuration is highly customized. What should you prioritize?

Question

Options

• AUse default dispatcher settings for migration
• BOptimize and validate the current dispatcher rules for compatibility
• CMigrate dispatcher configurations directly without changes
• DReplace the dispatcher with an alternative caching mechanism

• A
  6% (1)
• B
  88% (14)
• D
  6% (1)

Explanation

Option B is correct because a highly customized dispatcher configuration represents significant business logic - rewrite rules, caching policies, access controls - that must be preserved and validated for compatibility with the target environment before any migration proceeds. Skipping this step risks broken caching behavior, security gaps, or performance regressions in production.

Why the distractors fail:

• A - Default settings would silently discard all customizations, potentially breaking routing, caching, or security rules that exist for a reason.
• C - Migrating directly without review assumes the existing config is already correct for the new environment, which is unsafe; syntax, paths, or feature support may differ.
• D - Swapping the dispatcher for an alternative caching layer is a major architectural decision that goes far beyond what an assessment phase should prescribe - and ignores the existing investment in the current setup.

Memory tip: Think of the assessment phase as a doctor's exam before surgery - you diagnose and stabilize first (optimize and validate), not operate blindly (C), start from scratch (A), or replace the organ entirely (D).

No community discussion yet for this question.