VCS-256 無料問題集「Veritas Administration of Veritas InfoScale Availability 7.1 for UNIX/Linux」

（A）The cluster moves all applications to node1.

（B）The cluster faults and the subcluster with node1 in it panics.

（C）The cluster continues to run without impact to the application.

（D）The cluster faults and the subcluster with node1 in it remains online.

（A）It defines the number of attempts to clear the Faulted state of a service group on all nodes.

（B）It defines the number of attempts to clear the Faulted state of a resource on all nodes.

（C）It defines the number of attempts to clear the AutoDisabled state of a service group on a node.

（D）It defines the number of attempts to clear Faulted state of a resource on a single node.

（A）VCS automatically rejects all hastop commands when the cluster configuration is open.

（B）VCS prompts the administrator to save the configuration when stopping HAD on all cluster nodes.

（C）VCS is stopped and any configuration changes made since the cluster configuration was saved are lost.

（D）VCS automatically writes the in-memory cluster configuration to the main.cf file then stops HAD.

（A）/etc/VRTSvcs/conf/config/main_A.log

（B）/var/VRTSvcs/log/engine_A.log

（C）/var/VRTSvcs/log/resources_A.log

（D）/var/VRTSvcs/log/messages_A.log

（A）by running the vxfenclearpre command

（B）by restarting HAD, fencing, and GAB

（C）by restarting fencing

（D）by rebooting all the cluster nodes

（A）NIC

（B）Mount

（C）DNS

（D）ElifNone

（E）IP

（A）The services continue to run on the active node while HAD is stopped.

（B）The services shut down on the active node and are brought up on the passive node.

（C）The online service groups on the active node are taken offline and remain offline until started manually.

（D）The passive node becomes the active node, and all service groups are automatically switched to the new active node.

（A）The in-memory configuration on the node is being updated to reflect configuration changes being made on a remote node.

（B）It is the last node to join the cluster and must wait to build the in-memory configuration until all other nodes have their in-memory configuration.

（C）The node is building the in-memory cluster configuration from the primary main.cf file on a remote node.

（D）The in-memory cluster configuration is being built by copying the in -memory configuration from another running cluster node.