easymultiple choiceObjective-mapped

You use a customer managed AWS KMS key (CMK) to encrypt objects in an S3 bucket using SSE-KMS. A specific IAM role must be able to decrypt objects. Where should you grant kms:Decrypt permissions so that the role can decrypt data encrypted with that CMK?

Question 1easymultiple choice
Full question →

You use a customer managed AWS KMS key (CMK) to encrypt objects in an S3 bucket using SSE-KMS. A specific IAM role must be able to decrypt objects. Where should you grant kms:Decrypt permissions so that the role can decrypt data encrypted with that CMK?

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

In the KMS key policy, allowing kms:Decrypt (and any other required KMS permissions) for the role’s principal ARN.

With SSE-KMS, KMS decryption is authorized by KMS for the specific CMK. The CMK key policy is a primary authorization layer; if the key policy does not allow kms:Decrypt for the role (or a matching principal), S3 requests that require KMS decryption will fail even if the S3 or IAM identity policies allow s3:GetObject.

B

Distractor review

Only in the S3 bucket policy by granting s3:GetObject, because S3 bucket policy controls decryption.

An S3 bucket policy can authorize s3:GetObject, but it does not grant KMS permission to decrypt a KMS-encrypted data key. KMS will still require key-policy (and IAM) authorization for kms:Decrypt on the CMK.

C

Distractor review

Only in the IAM role identity policy; the KMS key policy does not need changes for SSE-KMS.

For customer-managed keys, a restrictive CMK key policy can deny or omit access. In that case, identity-policy kms:Decrypt permission alone is insufficient because the key policy is also evaluated and must allow the role to use the key for decryption.

D

Distractor review

By enabling S3 default encryption; KMS permissions are automatically granted to all IAM roles in the account.

Default encryption only ensures objects are encrypted with the specified CMK when written. It does not grant decrypt permissions to other principals. Roles must be explicitly authorized to use the CMK.

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: In the KMS key policy, allowing kms:Decrypt (and any other required KMS permissions) for the role’s principal ARN. — For SSE-KMS, decryption requires authorization in KMS for the specific CMK. The CMK key policy is a key authorization layer that must allow the role to use the key for decryption (at least kms:Decrypt, plus any additional required KMS permissions depending on configuration). While the IAM role also needs appropriate identity-policy permissions, the most important place to grant kms:Decrypt for SSE-KMS—so that KMS will permit decrypt—is the CMK key policy. Bucket policy alone cannot replace KMS authorization. Why others are wrong: Option B is incorrect because granting s3:GetObject in the bucket policy does not authorize kms:Decrypt on the CMK. Option C is incorrect because identity-policy permission may still be blocked by a restrictive key policy. Option D is incorrect because default encryption does not expand access; it only affects how new objects are encrypted.

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.