Which scenario would indicate a low RPO?

Choosing frequent backups leading to minimal data loss as indicative of a low Recovery Point Objective (RPO) is accurate. RPO is a key aspect of data recovery planning that defines the maximum amount of data that can be lost, in terms of time, in the event of a system failure.

When backups are performed frequently, it means that the data is being captured and saved at short intervals. This minimizes the window during which data could be lost due to an outage or failure, aligning with the concept of a low RPO. Essentially, the more frequently the backups occur, the less data a business risks losing, which is critical for maintaining business continuity.

The other scenarios do not reflect a low RPO. Long downtimes during recovery, for instance, would suggest a higher RPO, as significant amounts of data could be lost if recovery is delayed. Infrequent checks on data integrity can lead to undetected issues, ultimately risking data loss, thus not supporting the criteria for a low RPO. A high tolerance for lost transactions also indicates a higher acceptable level of data loss, which directly contradicts the essence of having a low RPO.