You’re configuring a new application service group in a Veritas Cluster Server environment. The application requires a specific network interface to be brought online before the application binaries can start. However, you also need to ensure that if that network resource fails, the application attempts to restart locally before considering a failover. Which combination of VCS resource dependencies and attributes would most effectively model this behavior?

During a maintenance window, you need to migrate a highly-available database service from Node A to Node B. You want to perform a clean, administrative failover that ensures all resources are properly stopped on Node A before starting on Node B, and you want the cluster to manage the process without manual intervention on each resource. Which VCS command or approach should you use?

A system administrator accidentally deleted a critical configuration file for an application monitored by VCS. The VCS agent for that application is now failing its probe, reporting a fault. The file has been restored from backup. What is the most efficient way to clear the fault and return the service group to a stable, online state without causing an unnecessary failover or restart?

You are designing a VCS cluster for a new three-tier web application. The design calls for the web server tier and the database tier to be in separate service groups because they have different hardware requirements. However, for operational integrity, the web servers must never run unless the database is confirmed to be online. Which VCS feature should you implement between these two service groups?

While analyzing cluster performance, you notice that a particular disk group resource takes a very long time to import during service group startup, delaying the entire application. You’ve confirmed the storage is healthy. Which VCS resource attribute could you adjust to allow the application’s other resources to start in parallel with this lengthy disk group import, improving overall startup time?

Your VCS cluster uses agent-based monitoring for a custom application. The application has a known behavior where it may become temporarily unresponsive for up to 90 seconds during heavy batch processing, but it always recovers on its own. You need to prevent VCS from incorrectly faulting the application during these expected hangs. What is the best practice to handle this?

After a cluster node reboot, you observe that a service group is in an ‘UNKNOWN’ state on the primary node, and VCS is not attempting to start it. The ‘hastatus -summ’ command shows the node and cluster are running. What is the most likely first step to diagnose and resolve this issue?

You need to perform an operating system patch on a node in a two-node cluster. The patch requires a reboot. You want to ensure that during the reboot, the partner node does not interpret the loss of communication as a failure and attempt to acquire service groups that are still running on the patching node. What is the correct VCS procedure?

In a geographically stretched cluster, you have configured a witness server to avoid tie-breaking scenarios. Under which specific network failure condition will the witness server be polled to determine which cluster partition should remain operational?

You’re configuring a new application service group in a Veritas Cluster Server environment. The application requires a specific network interface to be brought online before the application binaries can start. However, you also need to ensure that if that network resource fails, the application attempts to restart locally before considering a failover. Which combination of VCS resource dependencies and attributes would most effectively model this behavior?0