An administrator unintentionally changed the name of an online resource group on one node of a 2-node cluster. The cluster has not been synchronized since the change was made.
How can the cluster configuration revert to the previous configuration without affecting the online resource group?
An administrator is configuring a PowerHA 6 cluster to use disk heartbeat as a non IP network. A shared volume group, dhbvg, has been configured using a single disk, hdisklO, on NodeA and NodeB.
The administrator believes that the prerequisites have been met, but would like to test connectivity of the disk heartbeat network before adding the network into the cluster.
How can the connectivity of this disk heartbeat network be tested?
PowerHA automatic error notification for shared data volume groups traps on which specific error?
A cluster resource group has following application server characteristics:
An application server start script starts process A and process B.
An application monitor with the following settings: long-running, monitor interval=60, stabilization interval=180
The monitor method checks process B. and if process B is down it restarts process B and exits with return code 0.
When the cluster is started, an administrator finds process A is down and output of cluster.mmddyyyy log file is as follows; What happened?

An administrator plans to migrate a PowerHA 6 cluster with AIX 7 nodes to PowerHA 7. Which migration method should be used to minimize downtime?
A 2-node cluster configuration has an application server named appl. The appl server has custom application monitors named appmon_a and appmon_b.
The setting of appmon_a and appmon_b follows:
appmon_a: monitoring process=A, monitor interval=20, stabilization interval=60, restart count=1 appmon_b: monitoring process=B, monitor interval=10, stabilization interval=60, restart count=0 If process B fails 30 seconds after process A fails and successfully restarts, what is the most amount of time it will take for a failover event to begin?
Which action can an administrator do when the cluster has mixed versions within a rolling migration?
An administrator is configuring a4-node cluster to host 3 instances of their production application in an N+1 fallover design. Each instance will be in a separate resource group, and all 4 nodes will be participating nodes in each resource group.
Under normal circumstances each node only hosts one instance of the application. Whichever are the first three nodes to join the cluster become production, and the fourth node will be the standby.
How must the resource group startup policy be configured to accomplish this?
An administrator is planning a PowerHA implementation for a database and application. The application is dependent on the database being available before the application is started.
If the database is moved from one node to another, the application will need to be re-started. The database and application will be in different resource groups.
How can this be achieved within PowerHA?