Which factor most directly affects RPO in cross-region replication?

Which factor most directly affects RPO in cross-region replication?

• A. The color of cables.
• B. The frequency of data replication.
• C. The size of CPU caches.
• D. The number of users.

Answer: (B)

Recovery Point Objective is about how much data you’re willing to lose in a failure. In cross-region replication, you keep a copy of data at a remote site by transferring updates at intervals. The interval between those replications directly sets how fresh the remote copy is, which determines the maximum potential data loss. If you replicate every minute, the worst you could lose is about a minute of data; if you replicate every hour, you could lose up to an hour. So the frequency of data replication is the lever that most directly controls the RPO. Other factors listed don’t determine the data-loss window: the color of cables doesn’t affect data integrity; CPU cache size impacts performance, not how much data might be lost; the number of users affects workload but not the recovery-point target itself. It's also useful to remember there’s a trade-off between replication style and RPO: synchronous replication can push RPO toward zero but may add latency, while asynchronous replication lowers performance overhead but increases potential data loss.

Recovery Point Objective is about how much data you’re willing to lose in a failure. In cross-region replication, you keep a copy of data at a remote site by transferring updates at intervals. The interval between those replications directly sets how fresh the remote copy is, which determines the maximum potential data loss.

If you replicate every minute, the worst you could lose is about a minute of data; if you replicate every hour, you could lose up to an hour. So the frequency of data replication is the lever that most directly controls the RPO.

Other factors listed don’t determine the data-loss window: the color of cables doesn’t affect data integrity; CPU cache size impacts performance, not how much data might be lost; the number of users affects workload but not the recovery-point target itself. It's also useful to remember there’s a trade-off between replication style and RPO: synchronous replication can push RPO toward zero but may add latency, while asynchronous replication lowers performance overhead but increases potential data loss.