mediummultiple choiceObjective-mapped

Exhibit

Application log excerpt:

2026-04-11T09:14:22Z ERROR S3 GetObject failed: AccessDenied
2026-04-11T09:14:22Z ERROR KMS Decrypt failed for key arn:aws:kms:us-east-1:111122223333:key/abcd-1234

Current setup:
- S3 bucket default encryption: SSE-KMS
- EC2 application role: AppServerRole
- Bucket policy allows s3:GetObject for AppServerRole
- KMS key policy currently allows only the account root principal
- No direct KMS permissions are attached to AppServerRole

Based on the exhibit, what is the most appropriate change to restore application access while keeping encryption at rest with customer-managed KMS controls?

Question 1mediummultiple choice
Full question →

Based on the exhibit, what is the most appropriate change to restore application access while keeping encryption at rest with customer-managed KMS controls?

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

Distractor review

Change the bucket to SSE-S3 so the application no longer depends on KMS permissions.

This would remove KMS from the path, but it also removes customer-managed key control, which the requirement explicitly wants to keep.

B

Best answer

Update the KMS key policy or add a grant so AppServerRole can use the key for decrypt and data key operations.

For SSE-KMS objects, the caller needs permission to use the KMS key as well as S3 permissions. The role already has S3 access, but KMS is denying Decrypt because the key policy does not allow the role. Adding the role through the key policy or a grant, together with the needed KMS actions, resolves the failure while preserving customer-managed encryption.

C

Distractor review

Move the EC2 instance into the same Availability Zone as the S3 bucket to reduce encryption errors.

S3 is a regional service and does not depend on the instance being in a specific Availability Zone for KMS access.

D

Distractor review

Attach AmazonS3FullAccess to the application role so S3 can bypass KMS authorization.

S3 permissions do not bypass KMS authorization for SSE-KMS objects. The decrypt call is still evaluated by KMS.

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 KMS key policy or add a grant so AppServerRole can use the key for decrypt and data key operations. — When S3 uses SSE-KMS, access requires both an S3 permission path and permission to use the KMS key. In the exhibit, S3 allows the role, but KMS denies Decrypt because the key policy is too restrictive. The proper fix is to allow AppServerRole through the key policy or a KMS grant, and ensure the role has the needed KMS actions. That preserves customer-managed encryption while restoring access. Why others are wrong: Switching to SSE-S3 removes the KMS dependency, but that changes the security model and gives up customer-managed key control. Availability Zone placement is irrelevant because KMS and S3 authorization are not AZ-scoped. AmazonS3FullAccess does not override KMS authorization, so it will not fix a KMS AccessDenied error for SSE-KMS objects.

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.