mediummulti selectObjective-mapped

A startup runs an API on Amazon EC2. The instance must read items from one DynamoDB table and upload logs to one S3 bucket. Platform engineers also need a way to create new application roles, but those roles must never exceed a predefined set of permissions. Which three actions should the architect take? Select three.

Question 1mediummulti select
Full question →

A startup runs an API on Amazon EC2. The instance must read items from one DynamoDB table and upload logs to one S3 bucket. Platform engineers also need a way to create new application roles, but those roles must never exceed a predefined set of permissions. Which three actions should the architect take? Select three.

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

Attach an IAM role to the EC2 instance profile and remove long-lived access keys from the server.

This gives the workload temporary credentials through the instance metadata service and avoids storing secrets on the host. It is the standard least-privilege pattern for EC2-based applications.

B

Distractor review

Give the EC2 instance an IAM user with administrator access for simplicity.

An IAM user with broad permissions creates long-lived credentials and unnecessary blast radius. It is the opposite of least privilege and is hard to audit safely.

C

Best answer

Scope the application policy to the exact DynamoDB table ARN and S3 bucket prefix.

Restricting the policy to the specific table and bucket prefix limits what the application can reach. That keeps the workload functional while preventing access to unrelated data.

D

Distractor review

Store the access keys in the application configuration file and rotate them later.

Static keys in configuration files are easy to leak and are difficult to rotate cleanly. AWS roles are safer because temporary credentials are issued automatically.

E

Best answer

Use a permissions boundary for any IAM roles the platform team is allowed to create.

A permissions boundary caps the maximum permissions a created role can ever receive. It is ideal for delegated administration when teams can create roles but must stay within guardrails.

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: Attach an IAM role to the EC2 instance profile and remove long-lived access keys from the server. — The best design combines temporary credentials for the EC2 workload, tightly scoped resource permissions, and a permissions boundary for delegated role creation. That approach protects the application from credential leakage, limits the data it can access, and prevents platform engineers from accidentally or intentionally creating overly powerful IAM roles. This is a classic least-privilege pattern for both workloads and administrators. Why others are wrong: An IAM user with admin access and static access keys both create long-lived credentials and unnecessary privilege, which is unsafe and difficult to govern. They also undermine the purpose of using AWS-native temporary credentials. Those choices are common mistakes because they seem simpler, but they increase operational risk and audit burden without providing any architectural advantage.

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.