City leadership states that losing the last hour of 311 tickets after failover is unacceptable. How should that statement drive architecture?
Select an answer to reveal the explanation.
Short Explanation
“Don’t lose the last hour of 311 tickets” is plain-English RPO. Build replication or backups that can’t lag more than that. Pretending RPO is a warranty term—or planning on weekly loss—misses what leadership said.
Full Explanation
Business continuity language maps to measurable RTO and RPO targets. Declaring that the last hour of 311 tickets must not be lost after failover establishes an RPO stricter than one hour, which drives continuous replication or sufficiently frequent backups and validated failover. Treating RPO as irrelevant, stretching it to a week, or defining only RTO leaves data-loss risk outside the city’s stated tolerance.