Question 645 of 1,040
Design Resilient ArchitectureshardMultiple SelectObjective-mapped

Quick Answer

The answer is enabling DynamoDB point-in-time recovery and deletion protection. Point-in-time recovery (PITR) provides continuous backups with 35-day granularity, allowing restoration to any second within that window without custom scripts, directly satisfying the recovery requirement. Deletion protection prevents accidental table drops by blocking delete operations at the API level, meeting the accidental-delete protection need without operational overhead. On the SAA-C03 exam, this pairing tests your understanding of native AWS safeguards versus custom scripting—a common trap is suggesting AWS Backup or lifecycle policies, which address different concerns. Remember the mnemonic “PITR saves data, Deletion saves the table” to keep both settings distinct and complementary.

SAA-C03 Design Resilient Architectures Practice Question

This SAA-C03 practice question tests your understanding of design resilient architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: dynamoDB Point-in-Time Recovery (PITR) provides continuous backups.. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A claims workflow requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable? The design must avoid adding custom operational scripts.

Question 1hardmulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Point-in-time recovery

Point-in-time recovery (PITR) for DynamoDB enables continuous backups with 35-day granularity, allowing restoration to any second within that window. This directly satisfies the point-in-time recovery requirement without custom scripts, as it is a native AWS feature.

Key principle: DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.

Answer analysis

Option-by-option breakdown

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

  • Point-in-time recovery

    Why this is correct

    PITR allows restoration to a specific second within the supported recovery window.

    Related concept

    DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.

  • DAX

    Why it's wrong here

    DAX improves read performance but does not provide recovery.

  • Deletion protection or tightly controlled delete permissions

    Why this is correct

    Deletion protection and least-privilege controls reduce accidental table removal risk.

    Related concept

    DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.

  • Global secondary indexes

    Why it's wrong here

    GSIs support query access patterns but do not protect against data loss.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse DAX with a data protection feature, but DAX only accelerates reads and has no role in backup or deletion prevention.

Detailed technical explanation

How to think about this question

PITR uses a continuous stream of changes to maintain a 35-day restore window, with a restore throughput limit of 100 MB/s per table. Accidental-delete protection is enforced at the table level via a deletion protection flag; when enabled, the table cannot be dropped via the console, CLI, or API without first disabling the flag, which itself requires appropriate IAM permissions.

KKey Concepts to Remember

  • DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.
  • PITR allows restoration to any second within the last 35 days.
  • PITR is enabled per table and is a fully managed service.
  • Restoring a table from PITR creates a new table with the recovered data.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review dynamoDB Point-in-Time Recovery (PITR) provides continuous backups., then practise related SAA-C03 questions on the same topic to reinforce the concept.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SAA-C03 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Design Resilient Architectures — This question tests Design Resilient Architectures — DynamoDB Point-in-Time Recovery (PITR) provides continuous backups..

What is the correct answer to this question?

The correct answer is: Point-in-time recovery — Point-in-time recovery (PITR) for DynamoDB enables continuous backups with 35-day granularity, allowing restoration to any second within that window. This directly satisfies the point-in-time recovery requirement without custom scripts, as it is a native AWS feature.

What should I do if I get this SAA-C03 question wrong?

Review dynamoDB Point-in-Time Recovery (PITR) provides continuous backups., then practise related SAA-C03 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

DynamoDB Point-in-Time Recovery (PITR) provides continuous backups.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

6 more ways this is tested on SAA-C03

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A claims workflow requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable?

hard
  • A.Point-in-time recovery
  • B.DAX
  • C.Deletion protection or tightly controlled delete permissions
  • D.Global secondary indexes

Why A: Point-in-time recovery (PITR) for DynamoDB enables continuous backups with 35-day granularity, allowing restoration to any second within that window. This directly satisfies the requirement for point-in-time recovery by providing the ability to restore the table to a specific state before a data corruption or accidental write event.

Variation 2. A claims workflow requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable? The architecture review board prefers a managed AWS-native control.

hard
  • A.Point-in-time recovery
  • B.DAX
  • C.Deletion protection or tightly controlled delete permissions
  • D.Global secondary indexes

Why A: Point-in-time recovery (PITR) for DynamoDB enables continuous backups with 35-day granularity, allowing restoration to any second within that window. This satisfies the point-in-time recovery requirement by providing a managed AWS-native control that automatically backs up table data without manual intervention.

Variation 3. A payments API requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable? The design must avoid adding custom operational scripts.

hard
  • A.Deletion protection or tightly controlled delete permissions
  • B.Point-in-time recovery
  • C.Global secondary indexes
  • D.DAX

Why A: Deletion protection (option A) prevents accidental deletion of the DynamoDB table itself, which is critical for the accidental-delete protection requirement. Point-in-time recovery (option B) enables restoring the table to any point within the last 35 days, satisfying the point-in-time recovery requirement. Both features are native DynamoDB capabilities that require no custom scripts.

Variation 4. A payments API requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable?

hard
  • A.Deletion protection or tightly controlled delete permissions
  • B.Point-in-time recovery
  • C.Global secondary indexes
  • D.DAX

Why A: Deletion protection (Option A) prevents accidental table deletion by blocking DropTable API calls unless explicitly disabled, which is essential for protecting the payments table from human error or automated scripts. Point-in-time recovery (Option B) enables continuous backups with 35-day granularity, allowing restoration to any second within that window to recover from accidental writes or data corruption. Together, these settings satisfy both the point-in-time recovery and accidental-delete protection requirements for the DynamoDB table.

Variation 5. A payments API requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable? The architecture review board prefers a managed AWS-native control.

hard
  • A.Deletion protection or tightly controlled delete permissions
  • B.Point-in-time recovery
  • C.Global secondary indexes
  • D.DAX

Why A: Point-in-time recovery (PITR) enables continuous backups of the DynamoDB table, allowing restoration to any point within the last 35 days, which satisfies the requirement for point-in-time recovery. Deletion protection prevents accidental deletion of the table by blocking drop-table operations, meeting the accidental-delete protection requirement. Both are managed AWS-native controls that require no custom scripting or external tooling.

Variation 6. A payments API requires point-in-time recovery and accidental-delete protection for a DynamoDB table. Which two settings should the architect enable? The team wants the control to be enforceable during normal operations.

hard
  • A.Deletion protection or tightly controlled delete permissions
  • B.Point-in-time recovery
  • C.Global secondary indexes
  • D.DAX

Why A: Deletion protection (Option A) prevents accidental table deletion by blocking drop-table operations, which is enforceable during normal operations. Point-in-time recovery (Option B) enables continuous backups with 35-day granularity, allowing restoration to any second within that window. Together, they satisfy the requirements for accidental-delete protection and point-in-time recovery.

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.