DynamoDB Point-in-Time Recovery vs Backup

SAA-C03 By islever Editorial Last updated

Determine appropriate data security controls.

Short answer

A Configure point-in-time recovery for the table to enable continuous backups and granular restoration with zero operational overhead.

Question

A company has a business-critical application that runs on Amazon EC2 instances. The application stores data in an Amazon DynamoDB table. The company must be able to revert the table to any point within the last 24 hours. Which solution meets these requirements with the LEAST operational overhead?
  1. Configure point-in-time recovery for the table. Correct Answer
  2. Use AWS Backup for the table.
  3. Use an AWS Lambda function to make an on-demand backup of the table every hour.
  4. Turn on streams on the table to capture a log of all changes to the table in the last 24 hours. Store a copy of the stream in an Amazon S3 bucket.

Key Takeaways

The question tests knowledge of DynamoDB native backup features; the trap is choosing AWS Backup or Lambda for tasks that PITR handles natively with zero management.

Point-in-time recovery (PITR) is the most efficient way to restore Amazon DynamoDB tables to any second within a retention window, minimizing operational overhead compared to manual backups.

Common mistake: Candidates often select AWS Backup (Option B) because it offers longer retention periods, but PITR is specifically designed for frequent, granular restores with less overhead.

Expert Analysis

Why the Answer Is Correct

Point-in-time recovery (PITR) continuously backs up your DynamoDB table data, allowing you to restore the table to any second from the time PITR was enabled up to the previous 35 minutes. For business-critical applications requiring restoration within a 24-hour window, PITR provides this granularity with absolutely no operational overhead, as it is a toggle setting rather than a scheduled process.

Why the Other Options Are Wrong

AWS Backup (Option B) supports DynamoDB but typically involves more complex policy definitions and may not offer the same seamless, continuous second-by-second restore capability without additional configuration. Using a Lambda function (Option C) introduces significant operational overhead by requiring code maintenance, error handling, and IAM permissions. Streams (Option D) capture change logs but do not provide a direct restore mechanism to a previous state; they are used for replication or analytics, not point-in-time recovery.

Community Comment Notes

Community consensus strongly favors Option A, noting that PITR is a "highlight feature" of DynamoDB specifically designed to avoid the complexity of maintaining on-demand backups. Comments highlight that PITR eliminates the need to worry about creating or scheduling backups, making it the ideal solution for accidental deletions or writes within the recent past.

Exam Strategy

Always prioritize managed service features over custom solutions (like Lambda) when the requirement is standard data protection. If a service offers a built-in 'toggle' for a feature, it almost always has less operational overhead than an external tool.

Frequently Asked Questions

Why not use AWS Backup for DynamoDB?

AWS Backup is valid but requires policy management. PITR is simpler, continuous, and optimized for frequent small restores.

Does PITR cover the full 24 hours automatically?

Yes, once enabled, PITR retains data for 35 days by default, easily covering the 24-hour requirement without extra setup.

More SAA-C03 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. MattBJ 👍 5 Answered A
    A is correct. One of the highlight features of DynamoDB.
  2. Scheldon 👍 3 Answered A
    AnswerA Point-in-time recovery helps protect your DynamoDB tables from accidental write or delete operations. With point-in-time recovery, you don't have to worry about creating, maintaining, or scheduling on-demand backups. For example, suppose that a test script writes accidentally to a production DynamoDB table. With point-in-time recovery, you can restore that table to any point in time during the last 35 days. After you enable point-in-time recovery, you can restore to any point in time from five minutes before the current time until 35 days ago. DynamoDB maintains incremental backups of your table. https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/PointInTimeRecovery.html
  3. Andy_09 👍 13
    Option A
  4. asdfcdsxdfc 👍 3 Answered A
    A looks correct

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

S3 Multi-Region Access Point and Replication Strategy

S-grade

Securing NLB with Security Groups for Minimal Change

S-grade

Most Cost-Effective 7-Year Retention for EBS Snapshots?

S-grade

AWS Forecast vs SageMaker for Time-Series Prediction

S-grade

Practice All SAA-C03 Questions

Access 120 questions with complete answers and detailed explanations.

View Full SAA-C03 Practice Test →

← Back to SAA-C03 Study Guide