- A
Attach an SCP that denies kms:ScheduleKeyDeletion for all accounts.
Prevents scheduling key deletion.
- B
Enable CloudTrail to log key deletion events.
Why wrong: Detective, not preventive.
- C
Enable automatic key rotation.
Why wrong: Rotation does not prevent deletion.
- D
Modify the key policy to deny kms:ScheduleKeyDeletion for all principals.
Prevents deletion at the key level.
- E
Disable the key to prevent usage.
Why wrong: Disabling does not prevent deletion.
Quick Answer
The correct actions are to use a key policy that denies kms:ScheduleKeyDeletion for all principals and to apply a service control policy (SCP) that denies the same action at the organizational level. These two measures prevent accidental deletion of KMS keys by blocking the deletion scheduling process entirely, regardless of who attempts it. On the AWS Certified Security Specialty SCS-C02 exam, this question tests your understanding of preventive controls versus detective or reactive ones—many candidates mistakenly choose key rotation or disabling the key, but neither stops deletion. A common trap is confusing key rotation (which only refreshes cryptographic material) with deletion protection. Remember: to prevent deletion, you must explicitly deny the ScheduleKeyDeletion action, either in the resource-based key policy or through an SCP at the account or OU level. Memory tip: “Deny the schedule, keep the key.”
SCS-C02 Management and Security Governance Practice Question
This SCS-C02 practice question tests your understanding of management and security governance. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 uses AWS KMS to encrypt sensitive data. The security team needs to ensure that KMS keys cannot be deleted accidentally. Which TWO actions should be taken? (Choose TWO.)
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
Attach an SCP that denies kms:ScheduleKeyDeletion for all accounts.
Options A and C are correct. Enabling key rotation creates new cryptographic material but does not prevent deletion; however, the question asks about preventing deletion, so key rotation is not directly relevant. Actually, the correct answers are: enabling deletion protection on the key (Option B is correct if we consider that KMS now supports key deletion protection; but traditionally, the way to prevent deletion is to disable key deletion via key policy or using SCP. Option A: enabling automatic key rotation does not prevent deletion. Option B: disabling the key does not prevent deletion. Option C: using SCP to deny kms:ScheduleKeyDeletion is correct. Option D: using a key policy to deny deletion is correct. Option E: using CloudTrail is detective, not preventive. The correct two are C and D. I'll revise:
Key principle: ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Attach an SCP that denies kms:ScheduleKeyDeletion for all accounts.
Why this is correct
Prevents scheduling key deletion.
Related concept
Standard ACLs match source addresses.
- ✗
Enable CloudTrail to log key deletion events.
Why it's wrong here
Detective, not preventive.
- ✗
Enable automatic key rotation.
Why it's wrong here
Rotation does not prevent deletion.
- ✓
Modify the key policy to deny kms:ScheduleKeyDeletion for all principals.
Why this is correct
Prevents deletion at the key level.
Related concept
Standard ACLs match source addresses.
- ✗
Disable the key to prevent usage.
Why it's wrong here
Disabling does not prevent deletion.
Common exam traps
Common exam trap: ACLs stop at the first match
ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.
Detailed technical explanation
How to think about this question
ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.
KKey Concepts to Remember
- Standard ACLs match source addresses.
- Extended ACLs can match source, destination, protocol and ports.
- The first matching ACL entry is used.
- There is usually an implicit deny at the end.
TExam Day Tips
- Check inbound versus outbound direction.
- Read the ACL from top to bottom.
- Look for a broader permit or deny above the intended line.
Key takeaway
ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement.
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. ACLs process entries top to bottom and stop at the first match. Entry order and interface direction matter as much as the permit or deny statement. 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.
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SCS-C02 ACL questions on filtering logic and placement.
- →
Management and Security Governance — study guide chapter
Learn the concepts, then practise the questions
- →
Management and Security Governance practice questions
Targeted practice on this topic area only
- →
All SCS-C02 questions
1,738 questions across all exam domains
- →
AWS Certified Security Specialty SCS-C02 study guide
Full concept coverage aligned to exam objectives
- →
SCS-C02 practice test guide
How to use practice tests most effectively before exam day
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.
Threat Detection and Incident Response practice questions
Practise SCS-C02 questions linked to Threat Detection and Incident Response.
Security Logging and Monitoring practice questions
Practise SCS-C02 questions linked to Security Logging and Monitoring.
Identity and Access Management practice questions
Practise SCS-C02 questions linked to Identity and Access Management.
Management and Security Governance practice questions
Practise SCS-C02 questions linked to Management and Security Governance.
Infrastructure Security practice questions
Practise SCS-C02 questions linked to Infrastructure Security.
Data Protection practice questions
Practise SCS-C02 questions linked to Data Protection.
SCS-C02 fundamentals practice questions
Practise SCS-C02 questions linked to SCS-C02 fundamentals.
SCS-C02 scenario practice questions
Practise SCS-C02 questions linked to SCS-C02 scenario.
SCS-C02 troubleshooting practice questions
Practise SCS-C02 questions linked to SCS-C02 troubleshooting.
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?
Management and Security Governance — This question tests Management and Security Governance — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: Attach an SCP that denies kms:ScheduleKeyDeletion for all accounts. — Options A and C are correct. Enabling key rotation creates new cryptographic material but does not prevent deletion; however, the question asks about preventing deletion, so key rotation is not directly relevant. Actually, the correct answers are: enabling deletion protection on the key (Option B is correct if we consider that KMS now supports key deletion protection; but traditionally, the way to prevent deletion is to disable key deletion via key policy or using SCP. Option A: enabling automatic key rotation does not prevent deletion. Option B: disabling the key does not prevent deletion. Option C: using SCP to deny kms:ScheduleKeyDeletion is correct. Option D: using a key policy to deny deletion is correct. Option E: using CloudTrail is detective, not preventive. The correct two are C and D. I'll revise:
What should I do if I get this SCS-C02 question wrong?
Review ACL processing order, placement rules (standard near destination, extended near source), and inbound vs outbound direction. Study wildcard masks and implicit deny. Then practise related SCS-C02 ACL questions on filtering logic and placement.
What is the key concept behind this question?
Standard ACLs match source addresses.
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 →
Same concept, more angles
1 more ways this is tested on SCS-C02
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 AWS Key Management Service (KMS) to encrypt data. The security team needs to ensure that KMS keys cannot be deleted accidentally. Which action should be taken?
medium- A.Apply an SCP that denies kms:ScheduleKeyDeletion for all accounts.
- ✓ B.Create an IAM policy that denies kms:ScheduleKeyDeletion for the key.
- C.Enable automatic key rotation.
- D.Enable deletion protection on the key.
Why B: Enabling key rotation does not prevent deletion; disabling and scheduling deletion is the way to delete. To prevent accidental deletion, you must disable the option to schedule key deletion via an IAM policy or use a multi-region key? The best practice is to use an IAM policy that denies kms:ScheduleKeyDeletion for specific keys or to use a CloudWatch alarm. Among the options, setting a CloudWatch alarm on the deletion event is a detective control, but the question asks to prevent accidental deletion. The correct answer is to use an IAM policy to deny the schedule key deletion action. Option B (enabling deletion protection) does not exist for KMS. Option A (rotation) does not prevent deletion. Option D (SCP) can help but at org level. The best is IAM policy.
Keep practising
More SCS-C02 practice questions
- Drag and drop the steps to configure AWS WAF with rate-based rules in the correct order.
- Drag and drop the steps to set up AWS Shield Advanced with automatic application layer DDoS mitigation in the correct or…
- Drag and drop the steps to implement AWS KMS key rotation in the correct order.
- Drag and drop the steps to configure a VPC with private subnets and NAT gateway for outbound internet access in the corr…
- Drag and drop the steps to configure AWS CloudTrail for logging across all regions and accounts in the correct order.
- Drag and drop the steps to set up a secure S3 bucket with encryption and access control in the correct order.
Last reviewed: Jun 20, 2026
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.
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.