Which activities should be included in a post go-live support plan? (Choose two)

Question

Options

• AProactively monitor system performance
• BConduct metadata audits post-migration
• CMigrate additional content in the staging environment
• DEstablish escalation protocols for issues

• A
  81% (26)
• B
  6% (2)
• C
  13% (4)

Explanation

A post go-live support plan focuses on stabilizing and maintaining the live system, so proactively monitoring system performance (A) ensures issues are caught before users are impacted, and establishing escalation protocols (D) guarantees that when problems arise, there's a clear, fast path to resolution - both are core operational concerns after launch.

Why the distractors are wrong:

• B (metadata audits post-migration) is a data validation/migration quality activity, not a support plan activity - it belongs in the migration or cutover phase, not ongoing support.
• C (migrate additional content in staging) contradicts the "post go-live" context entirely; staging work happens before go-live, and migrating content in staging after launch doesn't support the live environment.

Memory tip: Think of post go-live support as "watch and respond" - Monitor (A) = watch, Escalation protocols (D) = respond. Anything that sounds like pre-launch prep (staging, audits, migration tasks) is a distractor.

No community discussion yet for this question.