mediummultiple choiceObjective-mapped

A customer-managed KMS key (CMK) encrypts SQS messages. A consumer service uses an IAM role that includes kms:Decrypt permission for that CMK. After a security change, the consumer fails with: "AccessDeniedException: kms:Decrypt is not allowed" CloudTrail indicates the KMS request is reaching KMS, but the CMK key policy no longer includes the consumer role (or its principal). What is the best fix?

Question 1mediummultiple choice
Full question →

A customer-managed KMS key (CMK) encrypts SQS messages. A consumer service uses an IAM role that includes kms:Decrypt permission for that CMK. After a security change, the consumer fails with: "AccessDeniedException: kms:Decrypt is not allowed" CloudTrail indicates the KMS request is reaching KMS, but the CMK key policy no longer includes the consumer role (or its principal). What is the best fix?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Update the CMK key policy to allow the consumer role principal to perform kms:Decrypt on the CMK.

For customer-managed keys, the CMK key policy is the authoritative authorization control for KMS operations. Even if the role’s identity policy allows kms:Decrypt, KMS will still deny the request unless the key policy also permits the principal (or a grant permits it).

B

Distractor review

Update only the consumer role identity policy because identity policies always override key policies.

Identity policies do not override a restrictive KMS key policy. KMS evaluates key policy authorization for customer-managed keys in addition to (and in practice as the gate for) identity-based permissions.

C

Distractor review

Enable default encryption on SQS so that KMS permissions are no longer required.

SQS encryption settings do not remove the authorization requirement for decrypting with a CMK. If messages are encrypted using a CMK, kms:Decrypt must still be allowed.

D

Distractor review

Create an S3 bucket policy statement allowing kms:Decrypt because the messages are stored in S3.

SQS message decryption authorization is evaluated by KMS using the CMK key policy (and possible grants). S3 bucket policies are unrelated to KMS authorization for SQS decryption.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Update the CMK key policy to allow the consumer role principal to perform kms:Decrypt on the CMK. — With customer-managed KMS keys, the CMK key policy is the controlling authorization mechanism for cryptographic operations. Therefore, if KMS denies kms:Decrypt after a key policy change, the remediation is to update the CMK key policy (or create/adjust a grant) to permit the consumer role principal. Updating only the identity policy for the role cannot resolve a key policy omission. B is incorrect because KMS authorization for customer-managed keys is not satisfied by identity policy alone when the key policy denies. C is incorrect because the CMK is still used, so KMS authorization remains required. D is incorrect because S3 bucket policies do not affect KMS authorization decisions for SQS message decryption.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.