SOA-C03 - Reliability and Business Continuity - Section 2.6

Restore databases and storage to meet recovery time and recovery point objectives using point-in-time restore and versioning.

Restore databases and objects to meet a defined recovery time objective and recovery point objective using point-in-time restore for RDS and Amazon S3 versioning for object recovery. Distinguish which recovery mechanism to choose based on the tolerable data loss window and the target restore time.

Point-in-time restoreRecovery time objectiveRecovery point objectiveAmazon S3 versioning

Practice question for this objective

Free sampleReliability and Business Continuitymedium

During a disaster recovery test, an Amazon RDS for MySQL database must be restored from automated backups, and the team measures how long the restore takes before the application can reconnect. They find the elapsed restore-and-warm-up time exceeds the agreed limit. In recovery objective terms, which measure are they failing to satisfy?

  • AThe recovery point objective, which sets the maximum amount of data the business is willing to lose measured backwards from the failure.
  • BThe retention period, which defines how many days of automated backups RDS keeps available for restore operations.
  • CThe recovery time objective, which sets the maximum acceptable duration between the failure and the service being usable again. Correct
  • DThe backup window, which is the daily span during which RDS takes the automated snapshot of the database instance.
Distinguish recovery time objective as the limit on restore duration from recovery point objective as the limit on data loss. Recovery time objective measures duration: the wall-clock time from a failure until the service is usable again, which includes restoring backups and warming the instance. Recovery point objective measures data loss in time before the failure. Because the team is over budget on how long the restore takes rather than how much data was lost, the measure being missed is the recovery time objective.

Why A is wrong: Recovery point objective bounds data loss, not duration, so a slow restore does not breach it as long as the recovered data is recent enough to meet the loss limit.

Why B is wrong: Retention period controls how far back you can restore, not how long the restore itself runs, so it is unrelated to the elapsed restore-and-warm-up time being too long.

Why C is correct: Recovery time objective is the agreed ceiling on how long recovery may take, so an elapsed restore that exceeds the limit is precisely a breach of the recovery time objective.

Why D is wrong: The backup window only governs when snapshots are taken each day and has no bearing on the time a restore takes once a recovery has been triggered.

See more SOA-C03 practice questions, answers explained.

More in this domain

Back to all Reliability and Business Continuity objectives, or the SOA-C03 cert hub.

Examworthy is not affiliated with or endorsed by Amazon Web Services. Original, blueprint-aligned practice material only.