A Cloud Infrastructure Architect deploys a highly available Cloud Volumes ONTAP (CVO) pair across AWS Availability Zone A (Node 1) and Zone B (Node 2). An ONTAP Mediator is deployed in Zone C to provide tiebreaking quorum.
Due to a catastrophic AWS network routing failure, Zone A and Zone B completely lose the ability to communicate with each other over the inter-AZ VPC subnets. The high-speed synchronous HA interconnect drops.
However, both Zone A (Node 1) and Zone B (Node 2) maintain perfect, uninterrupted network connectivity to the ONTAP Mediator in Zone C.
Based on the architectural mechanics of CVO split-brain mitigation, exactly how does the ONTAP Mediator resolve this network partition to prevent data corruption?
A. Upon detecting the network partition, the Mediator triggers a coordinated graceful shutdown of both nodes via the AWS EC2 API (using the stop-instances command), bringing the entire cluster offline to eliminate concurrent write risks and guarantee zero data corruption.
B. The Mediator functions as an active data proxy, dynamically routing the synchronous NVRAM write journal between Node 1 and Node 2 over the management network via a secure tunnel established through the Mediator instance in Zone C, maintaining active-active mirror synchronization until the primary interconnect is restored.
C. The Mediator dynamically reconfigures the CVO cluster, downgrading the HA pair into two independent single-node clusters by splitting the shared namespace and aggregates, with each node assigned a distinct portion to preserve partial client access during the partition event.
D. The Mediator detects both nodes are alive but isolated. To prevent split-brain, it grants the quorum lock to the first node contacting it (Node 1), fences Node 2 to force release of floating IPs and halt services, and allows Node 1 to continue serving clients.