Question 370
An HPE storage integrator is investigating this issue: Zero-loss transaction failover is requested without checking synchronous distance constraints. Which corrective action best addresses the reported condition?
Explanation
Correct Answer
The selected operation addresses the actual dependency: Evaluate supported synchronous replication transport latency and witness design. The mechanism is synchronous protection can add write latency and imposes geographic constraints. Successful service validation requires: A controlled site outage preserves committed data without inconsistent ownership.
Incorrect Answers
That alternative could help with the separate condition: A branch needs a fifteen-minute RPO but copies data once per day. It would be checked by a failover retrieves data within the allowed age threshold. For the described case, the necessary correction is evaluate supported synchronous replication transport latency and witness design.
This choice concerns Multisite data availability, for example: A disaster failover design omits quorum arbitration and permits split brain. The current storage issue instead hinges on synchronous protection can add write latency and imposes geographic constraints. The appropriate evidence is a controlled site outage preserves committed data without inconsistent ownership.
Although this option is reasonable for 'A controller failover discards unprotected acknowledged write cache.', it is not the specific dependency in the stem. Its action is validate protected cache durability and failover behavior. The stem is resolved more directly by evaluate supported synchronous replication transport latency and witness design.