Courseiva

SCS-C02 Practice Question: Allow users from its corporate Active Directory to access AWS resources

A company wants to allow users from its corporate Active Directory to access AWS resources. The company has set up an IAM identity provider for SAML. What must be created in IAM to map users to permissions?

⚠ Common exam trap

Test-takers frequently confuse the IAM role trust policy with the SAML identity provider configuration itself, thinking the provider alone grants permissions, rather than understanding that the role bridges the SAML assertion to AWS permissions.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

An IAM role with a trust policy for the SAML provider

A is correct because when using SAML-based federation, IAM roles are the mechanism to grant permissions to federated users. The role must have a trust policy that specifies the SAML identity provider as the principal, allowing users authenticated by the corporate Active Directory to assume the role and obtain temporary AWS credentials. This maps the SAML assertion attributes (such as the user's group or role) to IAM permissions via the role's permissions policy.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    An IAM role with a trust policy for the SAML provider

    Why this is correct

    For SAML federation, the correct pattern is an IAM role with a trust policy that grants sts:AssumeRoleWithSAML to the SAML identity provider you create in IAM. The corporate Active Directory is the external IdP (for example, AD FS or Shibboleth), and the trust policy uses the IAM SAML provider's ARN as the principal, often with an audience condition of urn:amazon:webservices. When a user authenticates to AD, the IdP issues a SAML assertion, AWS validates it against the SAML provider, and the user receives temporary credentials scoped by that role's permissions. This achieves single sign-on without creating or maintaining AWS credentials for each AD user.

  • ✗

    An OIDC identity provider

    Why it's wrong here

    An OIDC identity provider is not a valid replacement for this scenario because AD and AD FS use SAML 2.0, not OpenID Connect's JWT-based flow. OIDC in IAM is meant for web identity federation with providers such as Amazon Cognito, Google, or GitHub, and it uses sts:AssumeRoleWithWebIdentity, not sts:AssumeRoleWithSAML. Creating an OIDC provider would not match the SAML protocol used by the corporate Active Directory. Even though OIDC is a modern federation protocol, AWS treats it as a separate integration path, so it cannot provide the same SAML assertion processing this workload requires.

  • ✗

    An IAM user for each Active Directory user

    Why it's wrong here

    Creating an IAM user for each Active Directory user is the antithesis of federation; it duplicates the entire corporate directory inside AWS and forces you to manage rotation, MFA, and disablement of long-term credentials for every identity. IAM has quotas on the number of users, and every user would need unique programmatic credentials or passwords, which creates significant operational overhead and a wider secret-management surface. Federation is meant to let users log in to the AWS Management Console and API using their existing AD credentials and receive short-lived role-based credentials. Doing it manually with IAM users sacrifices the single-sign-on and centralized lifecycle benefits of the SAML role-based approach.

  • ✗

    A federation role type

    Why it's wrong here

    IAM does not have a distinct role type called a 'federation role'; all IAM roles are the same set of permission and trust policy documents, and the label is only a trust policy template in the AWS console. In the role creation wizard, choices such as 'SAML 2.0 federation' merely pre-populate the trust policy with a placeholder for a SAML provider ARN, not with a different kind of role. If you need SAML access, you still create a regular IAM role, set its permissions using IAM policies, and put the SAML provider ARN in the trust policy. Selecting a 'federation role type' is therefore an invalid mental model and would not alter the actual IAM role behavior.

About these practice questions

This SCS-C02 question is part of Courseiva's 1,205-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

You might also like

Similar SCS-C02 questions

Written by Johnson Ajibi, MSc IT Security

Security Systems Architect · founder of Courseiva

This SCS-C02 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SCS-C02 exam.