Your customer would like to implement Peer Persistence for their HPE Alletra 6000 remote replication...

The correct answer is D. HPE Alletra 6000 Peer Persistence is built on synchronous replication between two arrays and is designed for zero or near-zero RPO and fast recovery. HPE’s Peer Persistence technical white paper explains that synchronous replication uses LAN or WAN technologies to mirror data between sites and that data is copied across an IP address interface to the second array before the write is acknowledged. That makes high-speed IP connectivity the relevant design foundation for the replication path. Option A is incorrect because Peer Persistence does not require both arrays to operate as upstream for the same volume; source and destination roles are assigned per synchronously replicated volume collection, and different volume collections can reverse the source/destination role. Option B is imprecise because the replication mechanism is not “always iSCSI”; host access may involve iSCSI or FC, but synchronous replication traffic is array-to-array IP-based. Option C is wrong for the same reason: FC is not the mandatory transport for Alletra 6000 synchronous replication. Reference/topics: HPE Alletra 6000, NimbleOS Peer Persistence, synchronous replication, IP replication links, ASO design.