What should post-go-live monitoring focus on?

What should post-go-live monitoring focus on?

• A. Only monitor software version numbers.
• B. Ignore user feedback and wait.
• C. Post-go-live monitoring should include validating that changes behave as intended and monitoring for unintended access changes.
• D. Focus solely on hardware status.

Answer: (C)

In post-go-live monitoring, you verify that the deployed changes behave as intended and you watch for any unintended access changes. This approach ensures that the new functionality delivers the expected results while also protecting security by detecting permission or access-control issues early. You’d validate against acceptance criteria, monitor key performance and reliability signals, and review logs and user feedback for anomalies. For example, you’d check that a new feature works as planned, response times stay within baseline, and there are no new permissions granted or data access patterns that weren’t intended. Focusing only on software versions misses whether the changes actually function properly in production, ignoring user feedback risks unresolved usability problems, and concentrating solely on hardware status overlooks software behavior and security risks.

In post-go-live monitoring, you verify that the deployed changes behave as intended and you watch for any unintended access changes. This approach ensures that the new functionality delivers the expected results while also protecting security by detecting permission or access-control issues early. You’d validate against acceptance criteria, monitor key performance and reliability signals, and review logs and user feedback for anomalies. For example, you’d check that a new feature works as planned, response times stay within baseline, and there are no new permissions granted or data access patterns that weren’t intended. Focusing only on software versions misses whether the changes actually function properly in production, ignoring user feedback risks unresolved usability problems, and concentrating solely on hardware status overlooks software behavior and security risks.