Question 650
At fictional Granite Logistics, an HPE edge-to-cloud solution architect supporting distribution applications is assessing HPE end-to-end architecture and integration during a campus deployment design (HPE-HPE0-V27-DESIGN-163). The reported customer challenge is: A customer proposes active-active data centers across a high-latency WAN without a split-brain prevention design. Which underlying edge-to-cloud design or business principle best explains the appropriate response?
Explanation
Correct Answer
The governing principle is: Active data access requires coordinated write consistency and failure arbitration. For this problem, A customer proposes active-active data centers across a high-latency WAN without a split-brain prevention design, a suitable response is: Validate supported active-peer consistency, quorum and network delay characteristics. The expected result is: Site partition yields one authorized write owner and documented application behavior.
Incorrect Answers
“Hybrid connectivity requires consistent addressing, routing and name resolution” supports the separate task “Design controlled network translation or segmentation and coherent naming across environments”, not the reported problem: a customer proposes active-active data centers across a high-latency WAN without a split-brain prevention design. This case instead calls for “Validate supported active-peer consistency, quorum and network delay characteristics”.
“Encrypting data creates an operational dependency on key custody and recovery” concerns the separate step “Design storage encryption and KMS integration with ownership and recoverable key backup”. The reported issue is that a customer proposes active-active data centers across a high-latency WAN without a split-brain prevention design, so the direct response is to validate supported active-peer consistency, quorum and network delay characteristics.
The proposed “Governance boundaries should be reflected in tenant design” tests a different control: design separate project scopes, roles and data policies with controlled shared services. The reported condition is that a customer proposes active-active data centers across a high-latency WAN without a split-brain prevention design; the more direct action is to validate supported active-peer consistency, quorum and network delay characteristics.