easymultiple choiceObjective-mapped

A microservice needs to read exactly one secret value from AWS Secrets Manager. Which IAM permission statement provides the best least-privilege approach to allow the microservice to retrieve that secret value?

Question 1easymultiple choice
Full question →

A microservice needs to read exactly one secret value from AWS Secrets Manager. Which IAM permission statement provides the best least-privilege approach to allow the microservice to retrieve that secret value?

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

Allow secretsmanager:GetSecretValue on all secrets using Resource: "*"

Using Resource "*" allows the microservice to read the value of any secret in the account (subject to other conditions), which violates least privilege and increases blast radius if the microservice is compromised.

B

Best answer

Allow secretsmanager:GetSecretValue only on the specific secret ARN required by the service

Restricting the Resource to the exact Secrets Manager secret ARN limits retrieval to only that secret. This minimizes exposure and follows least-privilege practices. (If the secret is encrypted with a customer-managed KMS key, additional KMS permissions may be required for decrypting the ciphertext, but the Secrets Manager permission itself should still be scoped tightly.)

C

Distractor review

Allow secretsmanager:* on the secret name prefix using a wildcard pattern

Granting secretsmanager:* is broader than needed and includes sensitive write/delete actions. A wildcard prefix can also match more secrets than required, expanding the blast radius beyond the single secret the microservice needs.

D

Distractor review

Allow secretsmanager:GetSecretValue on the AWS account root ARN

The AWS account root ARN is not the correct resource type for Secrets Manager secrets. Because IAM resource matching requires the action to be permitted on the correct Secrets Manager secret resource ARN, this statement would not provide the intended access to the secret value.

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 only on the specific secret ARN required by the service — The least-privilege approach is to grant secretsmanager:GetSecretValue permission only for the specific secret ARN that the microservice needs. This scopes access tightly to a single secret and reduces the impact of credential compromise. Other required permissions (such as KMS decrypt) should be handled separately and scoped as tightly as possible. Resource "*" is overly broad and violates least privilege. Using secretsmanager:* and wildcard prefixes grants unnecessary permissions and can include additional secrets. Using an incorrect resource ARN (such as the account root) does not match the Secrets Manager secret resource, so it won’t correctly authorize GetSecretValue for that secret.

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.