Point-in-time recovery is turned off on a DynamoDB table. The only recovery copy is a monthly export to S3, and the team must restore to a recent moment between those exports. What should be enabled?
Select an answer to reveal the explanation.
Short Explanation
A monthly export is one photograph, and you need the time between the photographs. You enable continuous backups so the table can be restored to a recent point in time. A cache in front of the table is not a backup you can restore.
Full Explanation
Point-in-time recovery for DynamoDB is its continuous backup. With that feature off, the table has no continuous restore window, and a monthly export can rebuild data only as of the export. Enabling continuous backups lets the team restore to a recent moment between those exports. Running the export more often on the same monthly job shortens a gap and still leaves every moment between exports uncovered. It is not continuous backup. A global table replicates a table to another Region. It is not a second backup copy inside the same Region, and replication is not a point-in-time restore. DynamoDB Accelerator is a cache that speeds reads. Items in that cache are not a backup, and losing them does not restore the table. Caveat: a point-in-time restore creates a new table. It does not rewind the existing table in place, so the application has to be pointed at the restored table when you cut over. Operational check: confirm continuous backups are enabled, restore a test table to a recent time, and read a known item from that new table.