After the successful go-live of AEMaaCS, what should be the primary focus of the post go-live support plan?

Question

Options

• ARolling back to the previous version
• BTraining new users
• CEnhancing pre-go-live documentation
• DMonitoring and addressing issues promptly

• A
  4% (2)
• C
  2% (1)
• D
  93% (43)

Explanation

Monitoring and addressing issues promptly (D) is correct because the immediate post go-live period is the most critical window for stability - real users are now hitting the system, and any defects, performance degradation, or integration failures need rapid detection and resolution before they impact business operations. Option A (rollback) is a last-resort contingency, not a primary focus - planning to roll back assumes failure before it happens. Option B (training new users) is a pre-go-live or parallel activity, not the primary post go-live concern. Option C (enhancing pre-go-live documentation) is retroactive and lower priority; documentation improvements can happen after the system is stable.

Memory tip: Think of post go-live support like a rocket launch - once it's in the air, your job shifts entirely to monitoring telemetry and fixing anomalies in real time, not rewriting the launch manual or planning to abort.

No community discussion yet for this question.