easymultiple choiceObjective-mapped

A containerized service needs to read exactly one secret value from AWS Secrets Manager. The secret’s ARN is already known, and the secret is encrypted with the AWS-managed KMS key for Secrets Manager, so no separate KMS permissions are needed for this question. The service does not need to list secrets, create secrets, rotate them, or write updates. What is the most least-privilege IAM permission statement to grant the service role?

Question 1easymultiple choice
Full question →

A containerized service needs to read exactly one secret value from AWS Secrets Manager. The secret’s ARN is already known, and the secret is encrypted with the AWS-managed KMS key for Secrets Manager, so no separate KMS permissions are needed for this question. The service does not need to list secrets, create secrets, rotate them, or write updates. What is the most least-privilege IAM permission statement to grant the service role?

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

Allow secretsmanager:GetSecretValue on the specific secret ARN only.

For a read-only use case where the secret ARN is already known, the minimum required Secrets Manager action is secretsmanager:GetSecretValue. Scoping the resource to only that secret ARN minimizes blast radius if the role is compromised.

B

Distractor review

Allow secretsmanager:* on all resources in the account.

Using secretsmanager:* grants broad permissions including administrative and write capabilities, violating least privilege and increasing the impact of credential compromise.

C

Distractor review

Allow secretsmanager:ListSecrets so the service can discover the secret ARN at runtime.

ListSecrets is unnecessary when the secret ARN is already configured. It also exposes additional secret metadata and expands the permission set beyond what the described behavior requires.

D

Distractor review

Allow secretsmanager:PutSecretValue so the service can retrieve and update the secret value.

PutSecretValue is a write permission and is not required for read-only retrieval. Granting it increases risk without supporting the stated requirement.

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: Allow secretsmanager:GetSecretValue on the specific secret ARN only. — Least privilege for a service that only needs to read a known secret is granting secretsmanager:GetSecretValue for only that secret’s ARN. In this repaired version, the secret is explicitly assumed to use the AWS-managed KMS key for Secrets Manager, so no separate KMS permission is required for the question. The service does not need ListSecrets for discovery and does not need any write or administrative permissions. Wildcard actions expand permissions far beyond reading and can enable administrative or write actions. ListSecrets is not required when the secret ARN is already provided, and it unnecessarily exposes secret metadata. PutSecretValue grants write capability that contradicts the stated read-only requirement.

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.