Question 1,446 of 1,738
Data ProtectionmediumMultiple ChoiceObjective-mapped

Quick Answer

The correct procedure is to take a snapshot of the existing Redshift cluster, restore it to a new cluster with encryption enabled using an AWS KMS customer managed key, and then point applications to the new cluster. This is necessary because Amazon Redshift does not allow enabling encryption on an existing cluster directly; encryption settings are immutable after cluster creation, so the only way to encrypt data at rest is through the snapshot restore method. On the AWS Certified Security Specialty SCS-C02 exam, this question tests your understanding of Redshift’s encryption limitations and the proper migration workflow, often appearing as a trap where candidates mistakenly look for an “enable encryption” toggle in the console. A common memory tip is to remember that encryption is a “build-time” decision, not a “run-time” toggle—think “snapshot and swap” to avoid the trap of trying to modify the original cluster.

SCS-C02 Data Protection Practice Question

This SCS-C02 practice question tests your understanding of data protection. 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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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 company needs to encrypt data at rest in Amazon Redshift. They want to use an AWS KMS customer managed key. What is the correct procedure to enable encryption for an existing Redshift cluster?

Question 1mediummultiple choice
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

Take a snapshot of the cluster, restore it to a new cluster with encryption enabled, and point applications to the new cluster.

Amazon Redshift does not support enabling encryption on an existing cluster directly. The only way to transition an unencrypted cluster to an encrypted one is to take a snapshot of the cluster, restore it to a new cluster with encryption enabled using a KMS customer managed key, and then redirect applications to the new cluster. This is because encryption settings are immutable after cluster creation.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

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

  • Enable encryption using the Redshift console by selecting the KMS key.

    Why it's wrong here

    Console does not allow enabling encryption on existing cluster.

  • Use the AWS CLI command 'aws redshift modify-cluster' with --encrypted flag.

    Why it's wrong here

    Not supported for existing clusters.

  • Modify the cluster and enable encryption with the KMS key.

    Why it's wrong here

    Redshift does not allow modifying existing cluster to add encryption.

  • Take a snapshot of the cluster, restore it to a new cluster with encryption enabled, and point applications to the new cluster.

    Why this is correct

    Snapshots can be restored to encrypted clusters.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume encryption can be toggled on an existing cluster via console or CLI commands, similar to services like RDS or EBS, but Redshift enforces encryption as a cluster-level immutable property.

Detailed technical explanation

How to think about this question

Under the hood, Redshift encrypts data at rest using envelope encryption with a root key (either AWS managed or customer managed via KMS). The encryption is tied to the cluster's underlying hardware and storage volume, which cannot be altered post-provisioning. In real-world scenarios, this limitation means organizations must plan encryption at launch or use snapshot restore to migrate, which can incur downtime and require application reconfiguration.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

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

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related SCS-C02 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 SCS-C02 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 SCS-C02 question test?

Data Protection — This question tests Data Protection — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Take a snapshot of the cluster, restore it to a new cluster with encryption enabled, and point applications to the new cluster. — Amazon Redshift does not support enabling encryption on an existing cluster directly. The only way to transition an unencrypted cluster to an encrypted one is to take a snapshot of the cluster, restore it to a new cluster with encryption enabled using a KMS customer managed key, and then redirect applications to the new cluster. This is because encryption settings are immutable after cluster creation.

What should I do if I get this SCS-C02 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

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

Last reviewed: Jun 24, 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 SCS-C02 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 SCS-C02 exam.