A vCenter Operations Manager 5.7 environment is upgraded to vRealize Operations. After the upgrade, the analytics services fail to start. Which three steps must be taken to resolve the problem?…

Taking the vRealize Operations cluster offline stops all running services in a controlled manner, which is a prerequisite before modifying internal state files to prevent data corruption during the cleanup.

Deleting the activity persistence files removes legacy state data written by vCenter Operations Manager that is structurally incompatible with the vRealize Operations analytics engine, which prevents those services from starting.

Bringing the cluster back online after the persistence files are deleted allows the analytics services to initialize with a clean state, resolving the startup failure caused by the incompatible upgrade artifacts.

Removing unresponsive nodes is a general cluster remediation action unrelated to analytics startup failures that are caused specifically by incompatible persistence files left over from the upgrade.

Stopping the CaSA (Certificate and Secure Store Authority) service addresses certificate management issues, not analytics service startup failures, and would disrupt authentication functions if stopped unnecessarily.