hardmultiple choiceObjective-mapped

Exhibit

{
  "role_arn": "arn:aws:iam::111122223333:role/InboundExportRole",
  "trust_policy": {
    "Version": "2012-10-17",
    "Statement": [
      {
        "Effect": "Allow",
        "Principal": {"AWS": "arn:aws:iam::222233334444:root"},
        "Action": "sts:AssumeRole",
        "Condition": {
          "StringEquals": {"sts:ExternalId": "acctB-export-91"}
        }
      }
    ]
  },
  "cloudtrail_event": {
    "eventName": "AssumeRole",
    "userIdentity": "arn:aws:iam::222233334444:role/BatchRunner",
    "errorCode": "AccessDenied",
    "errorMessage": "Not authorized to perform sts:AssumeRole on resource arn:aws:iam::111122223333:role/InboundExportRole"
  }
}

Based on the exhibit, a batch platform in Account B must assume a role in Account A. Only the specific role arn:aws:iam::222233334444:role/BatchRunner should be allowed to assume it, and the design must prevent any other role in Account B from reusing the same external ID. Which change best meets the requirement?

Question 1hardmultiple choice
Full question →

Based on the exhibit, a batch platform in Account B must assume a role in Account A. Only the specific role arn:aws:iam::222233334444:role/BatchRunner should be allowed to assume it, and the design must prevent any other role in Account B from reusing the same external ID. Which change best meets the requirement?

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

Add an identity-based policy to the BatchRunner role that allows sts:AssumeRole on the target role.

The caller still also needs the trust policy to allow the specific principal. Identity policy alone does not authorize cross-account role assumption.

B

Best answer

Change the trust policy principal from account root to arn:aws:iam::222233334444:role/BatchRunner and keep the ExternalId condition.

This limits assumption to the exact role in Account B while preserving the ExternalId defense against confused deputy attacks.

C

Distractor review

Replace the ExternalId condition with a role session name condition so only BatchRunner sessions are accepted.

Role session names are not a strong security boundary and are easily chosen by the caller.

D

Distractor review

Attach an SCP to Account B that denies sts:AssumeRole unless the request comes from BatchRunner.

SCPs can restrict actions in Account B, but they do not replace the required trust policy in Account A.

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: Change the trust policy principal from account root to arn:aws:iam::222233334444:role/BatchRunner and keep the ExternalId condition. — The trust policy in Account A is too broad because it trusts the entire Account B root. The best fix is to trust only the specific BatchRunner role ARN and keep the ExternalId condition. That way, only the intended workload can assume the role, and the external ID still protects against confused deputy problems when the role is used by an external system. An identity policy in Account B is necessary, but it cannot override a trust policy that allows too many principals. A role session name is not a reliable authorization control because the caller chooses it. An SCP in Account B cannot grant access to a role in Account A; the Account A trust policy still must explicitly allow the caller.

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.