SAP-C02 Continuous Improvement for Existing Solutions Practice Question
This SAP-C02 practice question tests your understanding of continuous improvement for existing solutions. 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.
Exhibit
Refer to the exhibit.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:role/Admin"
},
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"kms:CallerAccount": "123456789012"
}
}
},
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:role/Admin"
},
"Action": [
"kms:Decrypt"
],
"Resource": "*"
}
]
}
```
A solutions architect is reviewing the above KMS key policy. The Admin role cannot decrypt data using the key. What is the MOST likely reason?
A solutions architect is reviewing the above KMS key policy. The Admin role cannot decrypt data using the key. What is the MOST likely reason?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Exhibit
Refer to the exhibit.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:role/Admin"
},
"Action": [
"kms:Decrypt",
"kms:GenerateDataKey"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"kms:CallerAccount": "123456789012"
}
}
},
{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::123456789012:role/Admin"
},
"Action": [
"kms:Decrypt"
],
"Resource": "*"
}
]
}
```
A solutions architect is reviewing the above KMS key policy. The Admin role cannot decrypt data using the key. What is the MOST likely reason?
A
The second statement does not include kms:GenerateDataKey, which is required for decryption.
Why wrong: The second statement does not need kms:GenerateDataKey for decryption; Decrypt alone is sufficient. So this is not the reason.
B
The condition in the first statement restricts decryption to requests coming from account 123456789012, but the role might be used by a user from a different account.
Why wrong: This is incorrect. The kms:CallerAccount condition checks the account of the principal making the request. When the Admin role is assumed, the caller account is the role's account (123456789012), not the user's account. Therefore, the condition would pass, and the first statement would allow decryption. Even if the condition failed, the second statement allows decryption unconditionally.
C
There is an explicit deny statement elsewhere in the policy.
This is the most likely reason. Since the shown policy allows decryption via both statements, but the role still cannot decrypt, there must be an explicit deny statement elsewhere in the key policy that overrides these allows. Such a deny could be for the same actions or same principal.
D
The condition key kms:CallerAccount is not a valid condition key for KMS key policies.
Why wrong: kms:CallerAccount is a valid condition key for KMS key policies. It is used to restrict access based on the caller's AWS account. So this is not the issue.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
There is an explicit deny statement elsewhere in the policy.
The correct answer is C. The key policy shown does not contain any explicit deny statements, so the inability to decrypt must be due to an explicit deny elsewhere in the key policy (possibly not shown) or in an IAM policy attached to the role. Option B is incorrect because the kms:CallerAccount condition checks the AWS account ID of the principal making the request; when a role from account 123456789012 is assumed, the caller account is 123456789012, regardless of the user's origin. Therefore, the condition would pass, and the first statement would apply. Since both statements allow decryption, the only remaining explanation is an explicit deny somewhere.
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.
✗
The second statement does not include kms:GenerateDataKey, which is required for decryption.
Why it's wrong here
The second statement does not need kms:GenerateDataKey for decryption; Decrypt alone is sufficient. So this is not the reason.
✗
The condition in the first statement restricts decryption to requests coming from account 123456789012, but the role might be used by a user from a different account.
Why it's wrong here
This is incorrect. The kms:CallerAccount condition checks the account of the principal making the request. When the Admin role is assumed, the caller account is the role's account (123456789012), not the user's account. Therefore, the condition would pass, and the first statement would allow decryption. Even if the condition failed, the second statement allows decryption unconditionally.
✓
There is an explicit deny statement elsewhere in the policy.
Why this is correct
This is the most likely reason. Since the shown policy allows decryption via both statements, but the role still cannot decrypt, there must be an explicit deny statement elsewhere in the key policy that overrides these allows. Such a deny could be for the same actions or same principal.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Standard ACLs match source addresses.
✗
The condition key kms:CallerAccount is not a valid condition key for KMS key policies.
Why it's wrong here
kms:CallerAccount is a valid condition key for KMS key policies. It is used to restrict access based on the caller's AWS account. So this is not the issue.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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 SAP-C02 ACL questions on filtering logic and placement.
Continuous Improvement for Existing Solutions — This question tests Continuous Improvement for Existing Solutions — Standard ACLs match source addresses..
What is the correct answer to this question?
The correct answer is: There is an explicit deny statement elsewhere in the policy. — The correct answer is C. The key policy shown does not contain any explicit deny statements, so the inability to decrypt must be due to an explicit deny elsewhere in the key policy (possibly not shown) or in an IAM policy attached to the role. Option B is incorrect because the kms:CallerAccount condition checks the AWS account ID of the principal making the request; when a role from account 123456789012 is assumed, the caller account is 123456789012, regardless of the user's origin. Therefore, the condition would pass, and the first statement would apply. Since both statements allow decryption, the only remaining explanation is an explicit deny somewhere.
What should I do if I get this SAP-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 SAP-C02 ACL questions on filtering logic and placement.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
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.
This SAP-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 SAP-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.