hardmultiple choiceObjective-mapped

Exhibit

Bucket configuration for arn:aws:s3:::corp-shared-data:
- S3 Block Public Access: enabled
- Object Ownership: BucketOwnerEnforced
- ACLs: disabled

Bucket policy excerpt:
- 17 separate statements grant GetObject and PutObject to different team roles
- Each statement uses a team-specific prefix condition

Audit note:
"A recent policy edit granted Team B access to Team C's uploads for 18 minutes before rollback."

Based on the exhibit, the company has one shared S3 bucket for many internal teams. Security wants each team to access only its own prefix, ACLs must remain disabled, and the current bucket policy has become too large and error-prone. What is the best redesign?

Question 1hardmultiple choice
Full question →

Based on the exhibit, the company has one shared S3 bucket for many internal teams. Security wants each team to access only its own prefix, ACLs must remain disabled, and the current bucket policy has become too large and error-prone. What is the best redesign?

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

Re-enable object ACLs and manage access by setting object-level ACLs for each team's prefix.

This reintroduces ACL management complexity and conflicts with the requirement to avoid ACLs. It also makes permissions harder to audit and easier to misconfigure.

B

Distractor review

Split the bucket into one bucket per team and keep using a single shared bucket policy for all of them.

Separate buckets can work, but they multiply operational overhead and still require policy management across many buckets. The question asks for a better redesign of the access model, not just more buckets.

C

Best answer

Create one S3 access point per team and attach an access point policy that limits that team to its own prefix.

S3 access points are designed for simplifying access management to shared buckets. A separate access point per team keeps the bucket private, avoids ACLs, and lets each team have a smaller, easier-to-review policy boundary. This reduces the blast radius of a policy mistake and scales far better than a single giant bucket policy with many prefix rules.

D

Distractor review

Make the bucket public and issue presigned URLs for team access so IAM policies are no longer needed.

Presigned URLs are useful for temporary access, but making the bucket public violates the security requirement. Public access would also expose the bucket beyond the intended internal teams.

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: Create one S3 access point per team and attach an access point policy that limits that team to its own prefix. — S3 access points are the cleanest way to segment access for many internal consumers of one shared bucket. Each team gets its own access point policy, which keeps permissions focused on that team's prefix and reduces the chance that one broad bucket policy change affects everyone. This design works well with BucketOwnerEnforced ownership and Block Public Access because ACLs stay disabled and access remains tightly controlled through IAM and access point policy evaluation. Why others are wrong: ACLs were explicitly ruled out, so re-enabling them violates the requirement. Splitting into many buckets can be workable, but it increases overhead and does not directly solve the policy sprawl problem described in the exhibit. Making the bucket public is an obvious security violation and does not fit an internal least-privilege design.

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.