What is the purpose of preparing a post go-live support plan during migration?

Question

Options

• ATo reduce the need for user training
• BTo address unexpected issues and ensure smooth operations
• CTo migrate additional assets after go-live
• DTo configure dispatcher cache invalidation rules

• A
  8% (3)
• B
  87% (33)
• C
  3% (1)
• D
  3% (1)

Explanation

A post go-live support plan exists precisely to catch and resolve the problems that surface only once real users interact with the live system - things like performance bottlenecks, integration failures, or data inconsistencies that testing couldn't fully anticipate. Option B is correct because the entire purpose of this plan is to have a structured response ready for unexpected issues, minimizing downtime and business disruption.

Why the distractors are wrong:

• A is incorrect - user training is a pre-migration activity; the support plan deals with system stability, not training gaps.
• C is incorrect - migrating additional assets is a scope/planning concern handled before or during migration, not a post go-live support function.
• D is incorrect - dispatcher cache invalidation is a specific technical configuration task (common in CMS/CDN contexts) done during setup, not the purpose of a support plan.

Memory tip: Think of the post go-live support plan as an "emergency room" for your migration - it doesn't prevent problems, it ensures you can diagnose and treat them quickly once the system is live.

No community discussion yet for this question.