A company stores critical data in Amazon DynamoDB tables in the company's AWS account. An IT administrator accidentally deleted a DynamoDB table, causing significant data loss and operational disruption. The company wants to prevent this disruption in the future with the LEAST operational overhead. Which solution meets this requirement?

Configuring deletion protection on DynamoDB tables is the most effective solution with the least operational overhead. This feature directly prevents accidental deletion of tables, addressing the root cause of the problem. Once enabled, a table cannot be deleted until deletion protection is explicitly disabled, requiring an intentional action. Other options are less suitable: Configuring CloudTrail, EventBridge, and Lambda for automatic restoration adds significant operational complexity and overhead. It's a reactive solution that attempts to fix a deletion after it occurs, rather than preventing it. Creating a manual backup and restore plan is reactive and requires human intervention, which is prone to errors and delays, increasing operational overhead. Enabling point-in-time recovery (PITR) is crucial for data recovery from accidental writes or deletions within a table, but it does not prevent the entire table from being deleted. If the table itself is deleted, PITR data for that table is also lost.