What is a characteristic of the Veritas Cluster Server communication stack?

The procedure for making changes to the Veritas Cluster Server (VCS) cluster communications involves stopping the components in the communications stack,
modifying the configuration files, and restarting the stack.
In what order should the components be stopped?

When configured as default, the Veritas Cluster Server Notifier receives queued messages on a schedule every how many minutes?

An additional email address was added to the Veritas Cluster Server notifier resource without any other actions being taken. All but one user is receiving
notifications.
How can this problem be solved?

Which Veritas Cluster Server utility can be used to prototype cluster logic using minimal hardware?

Which two are valid settings for FailoverPolicy? (Select two.)

In the event that all heartbeats are lost on all interfaces, what should be implemented to reduce the likelihood of a split brain condition?

What should be done before removing a resource named webdg from a running service group?

The service group named websg is currently online on the sym3 node. All other nodes are running.
Consider the following partial main.cf definition:
Group websg (
SystemList = { sym1=0, sym2=1, sym3=2 }
AutoStartList = {sym2, sym3 }
FailOverPolicy = Priority
)
The operator incorrectly shuts down a critical resource in the websg service group outside of Veritas Cluster Server.
Based on the information provided, what will happen to the websg service group?

Consider the following configuration:
group websg (
SystemList = { sym1 = 1, sym2 = 2 }
AutoStartList = { sym1 }
Frozen = 1
)
While websg is online, all of the systems in the cluster are rebooted simultaneously. All of the systems finish booting and successfully join the cluster.
What will happen to the websg service group?