A regional utilities consortium tightened RPO for SCADA historian data replicated to AWS. The current design uses infrequent cross-Region snapshot copy that can lose many hours of telemetry. Which reliability change best matches the new RPO?
Select an answer to reveal the explanation.
Short Explanation
If the new RPO says “minutes,” a weekly suitcase of snapshots will not cut it. Pick a replication rhythm that actually matches how much telemetry the consortium can afford to lose.
Full Explanation
RPO drives replication frequency and method. When utilities tighten RPO, architects must move from infrequent snapshot copy toward continuous or more frequent cross-AZ/Region replication suited to the datastore. Stopping replication or using ephemeral instance store contradicts durability and recovery objectives.