Changing DynamoDB Encryption Key Requires Table Recreation

A company uses Amazon DynamoDB to store sensitive user data. The security team wants to ensure that all data is encrypted at rest using a customer-managed AWS KMS key. The DynamoDB table was created with the default AWS managed key. What is the required action to change the encryption key?

Quick Answer

The correct answer is to create a new DynamoDB table with the desired customer-managed KMS key, export data from the old table, and import into the new table. This is required because DynamoDB encryption at rest is configured at table creation time, and the encryption key—whether AWS managed or customer managed—cannot be modified on an existing table; there is no UpdateTable API for this purpose. On the AWS Certified Database Specialty DBS-C01 exam, this question tests your understanding that DynamoDB treats the KMS encryption key as an immutable table property, a common trap where candidates mistakenly look for a key rotation or update option. Remember that key rotation in KMS does not change the key material used by DynamoDB, and the default key cannot be deleted if in use. Memory tip: "Create, copy, cut over"—you must build a new table to swap the key.

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

✓

Create a new DynamoDB table with the desired KMS key, export data from the old table, and import into the new table.

DynamoDB does not allow changing the encryption key on an existing table. To use a customer-managed KMS key, you must create a new table with the desired key, export data from the old table, and import it into the new table. Option A is incorrect because the UpdateTable API does not support changing the encryption key. Option C is incorrect because enabling automatic key rotation on the existing KMS key does not change the key used by DynamoDB; it rotates the key material but the table still uses the same key ID. Option D is incorrect because deleting the default AWS managed key would break encryption for any tables using it, and it does not allow you to change the key for the existing table.

Answer analysis

Option-by-option breakdown

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

✗
Use the UpdateTable API to specify the new KMS key.
Why it's wrong here
UpdateTable does not support changing encryption keys.
✓
Create a new DynamoDB table with the desired KMS key, export data from the old table, and import into the new table.
Why this is correct
Encryption key can only be set at table creation.
✗
Enable automatic key rotation on the existing KMS key.
Why it's wrong here
Rotation does not change the key used by DynamoDB.
✗
Delete the default AWS managed key and create a new customer managed key.
Why it's wrong here
Deleting the key would break access.

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

1 more way this is tested on DBS-C01

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 company uses Amazon DynamoDB to store user session data. The security team requires that all data be encrypted at rest using a customer-managed AWS KMS key. The DynamoDB table is already configured with AWS managed KMS encryption. How can the company meet the encryption requirement without recreating the table?

hard

A.Enable DynamoDB Streams and use a Lambda function to copy data to a new table with the desired encryption.
B.Export the table to Amazon S3 using the on-demand backup feature, then import it into a new table encrypted with the desired KMS key.
✓ C.Use the UpdateTable API to specify the new KMS key in the SSESpecification parameter.
D.Delete the table and recreate it with the new KMS key.

Why C: DynamoDB supports updating the server-side encryption settings on an existing table using the UpdateTable API with the SSESpecification parameter. This allows you to change from an AWS managed KMS key to a customer managed KMS key without recreating the table or causing downtime. Option A is incorrect because DynamoDB Streams are used for change data capture and cannot modify encryption settings. Option B is incorrect because exporting to S3 and importing into a new table is unnecessary and introduces additional complexity and potential downtime when an in-place update is available. Option D is incorrect because deleting and recreating the table would result in data loss and downtime, and is not required as the UpdateTable API can change encryption directly.

Last reviewed: Jun 20, 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…

This DBS-C01 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 DBS-C01 exam.