Answer
Lag is only one part of replication health. Teams also need visibility into stalled apply processes, missed objects, journal issues, communication failures, and exception queues that can leave the secondary environment looking current until a test proves otherwise.
Buyers should ask to see how the platform surfaces those conditions, who gets alerted, and how quickly the team can confirm whether continuity targets are still intact. A product that only says replication is running is not giving enough operational proof.