Question 79 of 1,663
DBS-C01 Database Security Practice Question
Network Topology
A security auditor notices that the DynamoDB table 'UserData' is encrypted with a KMS key (exhibit). The company policy requires that all DynamoDB tables use an AWS managed key for encryption. What must be done to comply with the policy?
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 SSE enabled using the AWS managed key, then export data from the existing table and import into the new table.
DynamoDB does not support changing the KMS key or SSE configuration after table creation. To use the AWS managed key instead of a customer managed key, you must create a new table with SSE-KMS enabled using the AWS managed key (alias 'aws/dynamodb'), export the existing table data (via DynamoDB export to S3 or using a scan/write process), and import it into the new table. Option B is incorrect because a customer managed KMS key cannot be converted into an AWS managed key; they are distinct key types. Option C is incorrect because you cannot modify the SSE configuration of an existing DynamoDB table; encryption settings are immutable after creation. Option D is incorrect because the UpdateTable API does not allow changing the KMS key used for encryption; it only supports updating other table settings like billing mode or provisioned throughput.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a new DynamoDB table with SSE enabled using the AWS managed key, then export data from the existing table and import into the new table.
Why this is correct
Key can only be set at creation.
- ✗
Delete the customer managed KMS key and recreate it as an AWS managed key.
Why it's wrong here
AWS managed keys cannot be created by users.
- ✗
Modify the table's SSE configuration to use the AWS managed key.
Why it's wrong here
SSE configuration cannot be modified after table creation.
- ✗
Use the UpdateTable API to change the KMS key to the AWS managed key.
Why it's wrong here
UpdateTable does not support changing encryption key.
Quick reference
AWS S3 Storage Class Comparison
| Storage Class | Min Duration | Retrieval | Use Case |
|---|---|---|---|
| S3 Standard | None | Immediate | Frequently accessed data |
| S3 Standard-IA | 30 days | Immediate | Infrequent access, rapid retrieval |
| S3 One Zone-IA | 30 days | Immediate | Non-critical infrequent data |
| S3 Intelligent-Tiering | None | Immediate–hours | Unknown or changing access patterns |
| S3 Glacier Instant | 90 days | Milliseconds | Archive with instant retrieval |
| S3 Glacier Flexible | 90 days | Minutes–hours | Archive, flexible retrieval |
| S3 Glacier Deep Archive | 180 days | Hours | Long-term compliance archive |
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 →
Last reviewed: Jun 20, 2026
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.
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.
Sign in to join the discussion.