SY0-701 Security Operations Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Reduce the restore point objective by storing more copies of the same backup.

  Why it's wrong here

  Storing additional copies of the same backup does not lower the recovery point objective (RPO) because RPO is defined by the maximum age of data that may be lost when recovery is performed. Duplicate copies all represent the same point-in-time snapshot, so the potential data-loss window remains unchanged. To reduce RPO, you must capture changes more frequently, such as via transaction log backups or more frequent snapshots, not simply replicate the same stale backup set.

• ✓

  Implement application-consistent backups or transaction log backups more frequently.

  Why this is correct

  Implementing application-consistent backups or transaction log backups more frequently directly reduces the recovery point objective (RPO) by shortening the interval between captured changes. Application-consistent backups ensure the database is in a valid state, while transaction log backups record every committed transaction, enabling point-in-time recovery to a precise moment. If the maximum tolerated data loss is one hour, capturing transaction logs every 15 minutes satisfies that target, whereas nightly full backups alone could lose up to 24 hours of data.

• ✗

  Extend the retention period so the full backup is kept for 90 days.

  Why it's wrong here

  Extending the retention period to 90 days affects how long backup data is available for restoration, but it does nothing to close the gap between backups. RPO is determined by the frequency of backups, not by how long they are kept; even a 90-day-old full backup offers the same recovery point as a 1-day-old backup if it is the latest one. Retention is relevant for compliance or disaster recovery from older corruption, but it cannot reduce the maximum data loss from a failure occurring just before the next scheduled backup.

• ✗

  Shorten the recovery time objective by using faster storage for the server.

  Why it's wrong here

  Using faster storage for the server can accelerate the restore process and thus help meet a recovery time objective (RTO), but it does not affect the recovery point objective (RPO). The issue described is data loss, which is measured by how recent the recovered data is, not by how quickly it can be restored. Shortening the RTO target itself is a design goal; faster hardware may assist in achieving it, but it has no impact on the frequency of backups or the amount of data that could be lost.

Go deeper

Related to this question