Courseiva

CCNA Identity And Access Management Questions

51 questions · Identity And Access Management topic · All types, answers revealed

1
Multi-Selectmedium

A company is transitioning from a Role-Based Access Control (RBAC) model to an Attribute-Based Access Control (ABAC) model to manage their growing AWS environment. Which TWO benefits does ABAC provide over a traditional RBAC approach?

Select 2 answers
A.Permissions automatically scale as new resources are created with the correct tags without requiring policy updates.
B.ABAC allows for the use of Service Control Policies (SCPs) which are not supported in an RBAC model.
C.It reduces the total number of IAM roles needed because one role can grant different access based on attributes.
D.ABAC eliminates the need for IAM trust policies when performing cross-account access between organizational accounts.
E.ABAC provides a built-in mechanism for multi-factor authentication (MFA) enforcement that RBAC lacks.
AnswersA, C

In an ABAC model, policies are written to allow access based on matching tags between the user and the resource. This means that as long as new resources are tagged correctly upon creation, users with matching tags gain access immediately without any manual changes to IAM policies.

Why this answer

Option A is correct because ABAC policies evaluate resource tags (for example, aws:ResourceTag/Project) at request time, so when a new resource is created with the matching tags it is automatically covered by the existing policy without any policy modification. Option C is correct because a single IAM role can carry one attribute-driven policy that grants different permissions depending on the principal's and resource's tags, replacing the many narrowly scoped roles a comparable RBAC design would require. Option B is incorrect because SCPs are an AWS Organizations feature that restrict permissions in any account regardless of whether RBAC or ABAC is used, so they are not an ABAC-only benefit.

Option D is incorrect because cross-account access still relies on IAM trust policies in the role's trust relationship to allow the principal to assume the role, and ABAC does not remove that requirement. Option E is incorrect because MFA enforcement is handled through IAM policy conditions such as aws:MultiFactorAuthPresent and is available in both RBAC and ABAC models, not a unique ABAC capability.

Exam trap

The trap is confusing ABAC with other AWS features like SCPs or MFA. Candidates might think ABAC provides MFA or eliminates trust policies, but those are separate mechanisms. Also, they might overlook that ABAC still requires proper tagging.

2
Multi-Selecthard

A large enterprise wants to implement SAML 2.0-based federation to allow employees to access the AWS Management Console using their existing corporate credentials. Which TWO steps are required to establish this trust relationship and enable user access?

Select 2 answers
A.Create an IAM SAML identity provider in the AWS account using the metadata document provided by the corporate IdP.
B.Configure the corporate IdP to send SAML assertions that include the 'Role' and 'RoleSessionName' attributes.
C.Install the AWS CLI on each employee's local machine and configure it with their corporate username and password.
D.Enable Multi-Factor Authentication (MFA) on the AWS root user to allow SAML assertions to be processed securely.
E.Create individual IAM users for every employee and map them to their corresponding corporate identities using tags.
AnswersA, B

The IAM SAML identity provider is a resource that tells AWS about your external IdP. By uploading the XML metadata document from your IdP, AWS can verify the digital signatures on SAML assertions sent by your organization. This is the foundational step for establishing the cryptographic trust between both parties.

Why this answer

Option A is correct because establishing SAML 2.0 federation requires creating an IAM SAML identity provider in the AWS account using the IdP's metadata document, which contains the signing certificate and entity ID needed to validate assertions from the corporate IdP. Option B is correct because the corporate IdP must issue SAML assertions containing the https://aws.amazon.com/SAML/Attributes/Role and https://aws.amazon.com/SAML/Attributes/RoleSessionName attributes so AWS can determine which IAM role to assume and the session name for the federated user. Option C is incorrect because AWS CLI installation and corporate credentials are irrelevant to console federation via SAML.

Option D is incorrect because MFA on the root user is unrelated to processing SAML assertions and is not required for federation. Option E is incorrect because SAML federation uses IAM roles rather than individual IAM users mapped by tags.

Exam trap

SCS-C03 often tests the misconception that you need IAM users or MFA on root for SAML federation — the correct answer is always the SAML identity provider plus properly formatted Role/RoleSessionName assertions.

3
MCQmedium

A company wants to provide its on-premises servers with access to AWS resources without using long-term IAM user access keys. The servers have existing X.509 certificates issued by an internal Certificate Authority (CA). Which AWS service or feature is the BEST solution for this requirement?

A.AWS Directory Service for Microsoft Active Directory to create a trust relationship with the on-premises domain.
B.AWS PrivateLink to establish a private connection between the on-premises data center and IAM endpoints.
C.IAM Roles Anywhere using the internal CA as a trust anchor to exchange certificates for temporary credentials.
D.AWS Systems Manager Hybrid Activations to manage the on-premises servers as Managed Instances.
AnswerC

IAM Roles Anywhere is specifically designed for this scenario. It allows you to define a trust anchor using your own CA. On-premises servers can then use their certificates to authenticate and receive temporary IAM credentials from the AWS Security Token Service, eliminating the risk of long-term keys.

Why this answer

IAM Roles Anywhere is designed exactly for this scenario: it lets on-premises servers with X.509 certificates from an internal CA exchange those certificates for temporary AWS credentials via STS AssumeRole, eliminating long-term IAM user keys. The internal CA is registered as a trust anchor, and the server presents its certificate to obtain role credentials.

Exam trap

SCS-C03 often tests whether candidates confuse identity services (IAM Roles Anywhere, Directory Service) with management or networking services (Systems Manager, PrivateLink) — the trap is picking a service that 'sounds' like it handles on-premises access but doesn't issue AWS credentials.

How to eliminate wrong answers

Option A is wrong because AWS Directory Service for Microsoft AD is for domain-joined Windows workloads and does not provide a certificate-based credential exchange mechanism for arbitrary on-premises servers. Option B is wrong because AWS PrivateLink provides private network connectivity to AWS services but does not issue credentials or replace long-term keys — it's a networking feature, not an identity feature. Option D is wrong because Systems Manager Hybrid Activations registers on-premises servers as managed instances for patching and automation, but it does not provide AWS API credentials for accessing arbitrary AWS resources like S3 or DynamoDB.

4
MCQmedium

A security engineer needs to delegate the ability to create IAM roles to a junior administrator. However, the engineer must ensure that the junior administrator cannot create roles with more permissions than they themselves possess. Which IAM feature should be used to enforce this constraint?

A.IAM Access Analyzer
B.Resource-based policies
C.IAM Permissions Boundaries
D.Service Linked Roles
AnswerC

A permissions boundary is a managed policy that sets the maximum permissions that an identity-based policy can grant to an IAM entity. When a boundary is applied, the entity can only perform actions that are allowed by both the identity-based policy and the permissions boundary, effectively preventing privilege escalation.

Why this answer

While Permissions Boundaries are the correct feature, the explanation should clarify that the security engineer must use an IAM policy with a 'Condition' element (specifically 'iam:PermissionsBoundary') to force the junior administrator to attach a specific boundary to any role they create. Without this condition, the junior administrator could simply choose not to attach a boundary.

Exam trap

Candidates often confuse Permissions Boundaries with Service Control Policies (SCPs). SCPs apply to accounts, whereas Permissions Boundaries apply to IAM entities (users/roles) within an account.

5
MCQhard

A security engineer is configuring a permissions boundary for a new IAM role that will be used by a third-party application. The permissions boundary policy allows only s3:GetObject and s3:PutObject on a specific bucket. The role's identity-based policy allows s3:DeleteObject on the same bucket. What will be the effective permissions for this role?

A.The role can perform s3:GetObject and s3:PutObject, but cannot perform s3:DeleteObject.
B.The role cannot perform any of the actions because the permissions boundary and identity-based policy conflict.
C.The role can perform all three actions: s3:GetObject, s3:PutObject, and s3:DeleteObject.
D.The role can perform s3:DeleteObject only, because the identity-based policy explicitly allows it.
AnswerA

A permissions boundary sets the maximum permissions that an identity-based policy can grant. The effective permissions are the intersection of the identity-based policy and the permissions boundary. Here, the boundary allows only GetObject and PutObject, while the identity-based policy allows DeleteObject. Since DeleteObject is not allowed by the boundary, it is not granted. Thus, only GetObject and PutObject are effective. This is the correct outcome.

Why this answer

Effective permissions for an IAM principal with a permissions boundary are the intersection of the identity-based policies and the permissions boundary. The boundary defines the maximum permissions, and the identity-based policy must allow the action as well. In this scenario, the boundary allows only GetObject and PutObject, so DeleteObject is not permitted even though the identity-based policy allows it.

The role can perform only the actions allowed by both policies.

Exam trap

The trap here is assuming that the identity-based policy alone determines permissions, ignoring that a permissions boundary can only restrict, not grant, permissions.

6
Multi-Selecthard

Which THREE actions are best practices for managing root user account security? (Select THREE)

Select 3 answers
A.Enable multi-factor authentication (MFA) on the root account.
B.Store the root access keys in a secure, encrypted S3 bucket.
C.Use the root account for daily administrative tasks to simplify management.
D.Delete the root access keys and do not create new ones.
E.Set up a strong password and rotate it at least once every 90 days.
AnswersA, D, E

MFA is the most critical defense against compromised root credentials. Without MFA, a leaked password grants full control over the AWS account. Requiring a hardware or virtual MFA device adds a necessary layer of protection, ensuring that even if the password is stolen, the attacker cannot access the account.

Why this answer

The root user has unrestricted access to all resources. Therefore, it must be protected with the highest level of security. Enabling MFA, deleting access keys, and avoiding day-to-day tasks are essential.

These actions minimize the risk of a full account takeover. By following these, you ensure that the root account is reserved for critical tasks like closing the account or managing specific billing configurations that cannot be delegated through IAM.

Exam trap

Candidates mistakenly believe that keeping root access keys is necessary for programmatic API operations, overlooking severe account takeover risks.

7
MCQhard

A security engineer needs to allow a third-party application running on an Amazon EC2 instance in another AWS account to access an Amazon S3 bucket in the engineer's account. The third-party account ID is 111122223333, and the EC2 instance uses an IAM role named 'ThirdPartyRole'. The engineer wants to grant access using a bucket policy. Which condition should the engineer include in the bucket policy to ensure that only the specific role from the third-party account can access the bucket?

A.aws:PrincipalArn equals arn:aws:sts::111122223333:assumed-role/ThirdPartyRole/*
B.aws:PrincipalArn equals arn:aws:iam::111122223333:role/ThirdPartyRole
C.aws:userid equals AROAEXAMPLE:ThirdPartyRole
D.aws:SourceArn equals arn:aws:iam::111122223333:role/ThirdPartyRole
AnswerA

When an IAM role is assumed, the principal ARN takes the form arn:aws:sts::account-id:assumed-role/role-name/session-name. To match any session of the role, you can use a wildcard in the session name. This condition ensures that only sessions of the specified role from the third-party account can access the bucket. It is the correct way to restrict access to a specific role.

Why this answer

The correct condition is to use aws:PrincipalArn with the assumed-role ARN format and a wildcard for the session name. This ensures that only sessions of the specified role from the third-party account can access the bucket. Other condition keys either do not apply or would not match the assumed role principal correctly.

Exam trap

The trap here is assuming that the role ARN (arn:aws:iam::account:role/role-name) is the principal ARN, but when a role is assumed, the principal ARN changes to the assumed-role format, which must be used in the condition.

8
MCQmedium

Which AWS feature should be used to provide temporary, limited-privilege credentials to external applications?

A.IAM User Access Keys.
B.AWS Security Token Service (STS).
C.IAM Managed Policies.
D.AWS Secret Manager.
AnswerB

STS is the specific AWS service meant for generating short-lived credentials. It supports assume-role, get-federation-token, and other mechanisms that are ideal for temporary access requirements. By leveraging STS, you ensure that your security architecture remains dynamic and highly resistant to long-term credential compromise, adhering to modern cloud security best practices.

Why this answer

AWS Security Token Service (STS) provides temporary, limited-privilege credentials for IAM users or federated users. It is the standard way to grant external applications temporary access without embedding long-term credentials. STS credentials include an access key ID, secret access key, and session token, and they expire after a specified duration.

Exam trap

SCS-C03 often tests the misconception that IAM user access keys are suitable for external applications, but the key is that STS provides temporary, limited-privilege credentials, which is the recommended approach.

How to eliminate wrong answers

Option A is wrong because IAM User Access Keys are long-term credentials that do not expire automatically and pose a security risk if compromised. Option C is wrong because IAM Managed Policies are permission policies that can be attached to users, groups, or roles, but they do not provide temporary credentials themselves. Option D is wrong because AWS Secrets Manager is for storing and rotating secrets like database credentials, not for providing temporary AWS credentials to external applications.

9
Multi-Selecthard

A company is securing AWS Secrets Manager. Which THREE actions will improve the security posture of secrets management?

Select 3 answers
A.Disabling the automatic rotation of secrets to prevent accidental application downtime.
B.Enabling automatic rotation using an AWS Lambda function to update credentials in the target database.
C.Using a resource-based policy to restrict which IAM principals can retrieve the secret.
D.Encrypting the secret using a Customer Managed Key (CMK) in AWS KMS instead of the default AWS managed key.
E.Storing the secrets in an S3 bucket with versioning enabled and using that as the primary source.
AnswersB, C, D

Automatic rotation is a key security feature. It ensures that even if a secret is compromised, it will only be valid for a limited time. Using Lambda allows for custom rotation logic that can update the password in the database and the secret value in AWS simultaneously.

Why this answer

Option B is correct because configuring automatic rotation with an AWS Lambda rotation function ensures credentials are periodically changed and updated in the target database, drastically reducing the window of exposure if a secret is leaked. Option C is correct because attaching a resource-based policy to the secret lets you explicitly limit which IAM principals can perform secretsmanager:GetSecretValue, enforcing least privilege at the secret level. Option D is correct because encrypting secrets with a customer managed key (CMK) in AWS KMS gives you control over the key policy, rotation, and the ability to revoke access by disabling or deleting the key, unlike the default AWS managed key aws/secretsmanager.

Option A is wrong because disabling rotation leaves long-lived credentials in place, increasing risk rather than improving posture. Option E is wrong because S3 is not the native secrets store for Secrets Manager; storing secrets in an S3 bucket bypasses Secrets Manager's encryption, rotation, and fine-grained access controls.

Exam trap

The trap is thinking that disabling rotation or storing secrets in S3 improves security; candidates might overlook that resource-based policies and CMKs are key security controls.

10
MCQhard

A security engineer is reviewing IAM policies and notices that a role has the following trust policy: {"Version":"2012-10-17","Statement":[{"Effect":"Allow","Principal":{"AWS":"arn:aws:iam::111122223333:root"},"Action":"sts:AssumeRole","Condition":{"StringEquals":{"sts:ExternalId":"12345"}}}]}. The engineer wants to ensure that only a specific application in account 111122223333 can assume this role. What additional step should the engineer take?

A.Rotate the external ID regularly to prevent unauthorized access.
B.Add a condition to the trust policy that restricts assumption to a specific IP range.
C.Modify the trust policy to specify the exact IAM role ARN of the application instead of the account root.
D.Enable AWS CloudTrail to monitor AssumeRole calls and alert on unauthorized assumptions.
AnswerC

Specifying the account root in the Principal allows any IAM principal in that account with sts:AssumeRole permission to assume the role, provided they know the external ID. To restrict to a specific application, the Principal should be the exact IAM role ARN used by the application. This limits assumption to only that role, enhancing security.

Why this answer

The trust policy currently allows any principal in account 111122223333 to assume the role if they provide the external ID. To restrict to a specific application, the Principal should be changed to the exact IAM role ARN that the application uses. This ensures that only that role can assume the target role, aligning with the principle of least privilege.

Exam trap

The trap here is assuming that specifying the account root and an external ID is sufficient to restrict access to a specific application, when in fact it allows any principal in the account.

11
MCQmedium

A security engineer is reviewing an IAM policy that is attached to a role used by an application. The policy includes the following statement: {"Effect":"Allow","Action":"s3:GetObject","Resource":"arn:aws:s3:::example-bucket/*","Condition":{"StringEquals":{"aws:PrincipalTag/Department":"Finance"}}}. The role is assumed by an EC2 instance. The application is failing to retrieve objects from the bucket. The engineer has confirmed that the role has the correct permissions and the bucket policy allows access. What is the MOST likely reason for the failure?

A.The EC2 instance is not tagged with Department=Finance, and the policy requires the instance to have that tag.
B.The S3 bucket policy does not allow the s3:GetObject action for the role.
C.The EC2 instance's IAM role does not have the aws:PrincipalTag/Department tag with value Finance.
D.The condition key aws:PrincipalTag/Department is only supported for IAM users, not roles.
AnswerC

The policy condition requires that the principal (the IAM role) has the tag Department with value Finance. If the role does not have this tag, the condition evaluates to false, and the action is denied. Tags on the role are used for the aws:PrincipalTag condition key. The engineer must ensure the role is tagged appropriately.

Why this answer

The IAM policy condition requires the principal to have the tag Department=Finance. Since the principal is the IAM role assumed by the EC2 instance, the role must be tagged with that key-value pair. If the role lacks the tag, the condition fails, and access is denied.

The bucket policy is not the issue, as it allows access.

Exam trap

The trap here is confusing aws:PrincipalTag with aws:ResourceTag or EC2 instance tags; aws:PrincipalTag applies to the IAM principal (user or role) making the request, not the resource or the EC2 instance itself.

12
Multi-Selectmedium

A company is setting up SAML 2.0 federation to allow employees to log into the AWS Management Console using their corporate credentials. Which TWO components are required to establish this trust relationship in AWS?

Select 2 answers
A.An IAM User with programmatic access keys for the Identity Provider.
B.A CloudFront distribution to cache the SAML assertion responses.
C.An IAM SAML Identity Provider entity created in the AWS account.
D.An Amazon Cognito User Pool to store the federated user profiles.
E.An IAM Role with a trust policy that allows the 'sts:AssumeRoleWithSAML' action.
AnswersC, E

You must create a SAML Identity Provider entity in IAM to establish the trust between your AWS account and your external IdP. This entity is configured by uploading the SAML metadata document provided by your IdP, which contains the public keys and endpoints needed for secure communication.

Why this answer

SAML 2.0 federation allows users to use their existing corporate credentials to access the AWS Management Console. This centralizes identity management and reduces the need for multiple sets of credentials. Configuring the trust relationship involves exchanging metadata between the Identity Provider and AWS, ensuring that the assertion contains the necessary attributes for role mapping and session management.

Exam trap

Candidates often forget the role trust policy. They focus on the SAML provider entity but fail to realize the IAM role must explicitly permit the 'sts:AssumeRoleWithSAML' action to function.

13
Multi-Selectmedium

A security engineer is reviewing IAM policies and needs to identify which statements are true regarding the evaluation of IAM policies. (Choose three.)

Select 3 answers
A.An Allow in a permissions boundary can grant permissions even if no identity-based policy allows the action.
B.If no policy explicitly allows an action, the request is implicitly denied.
C.Resource-based policies are evaluated before identity-based policies.
D.Service control policies (SCPs) can restrict permissions for member accounts in AWS Organizations.
E.An explicit Deny in any applicable policy always overrides any Allow.
AnswersB, D, E

By default, all requests are implicitly denied unless there is an explicit Allow in an applicable policy. This is a fundamental principle of IAM: permissions must be granted, not assumed. Therefore, if no policy allows the action, it is denied.

Why this answer

The true statements are that an explicit Deny always overrides any Allow, that actions are implicitly denied if not explicitly allowed, and that SCPs can restrict permissions in member accounts. These principles are core to IAM policy evaluation. Resource-based policies do not have a strict evaluation order, and permissions boundaries do not grant permissions.

Exam trap

The trap here is assuming that resource-based policies are evaluated first or that permissions boundaries can grant permissions, when in fact IAM evaluation is a combination of all applicable policies with explicit deny taking precedence.

14
MCQeasy

A developer needs programmatic access to DynamoDB from an application running on an Amazon EC2 instance. The security team's policy prohibits storing long-term IAM user access keys on EC2 instances. Which mechanism should the developer use to supply credentials?

A.Create an IAM role with the required DynamoDB permissions and attach it to the instance as an instance profile.
B.Configure the application to authenticate with the EC2 key pair used for SSH access and call DynamoDB with SigV4 signing.
C.Generate a long-lived bearer token with AWS Security Token Service and hard-code it into the application configuration file.
D.Store an IAM user's access key and secret key in AWS Systems Manager Parameter Store as a SecureString and read them at application startup.
AnswerA

Attaching an IAM role through an instance profile lets the instance obtain temporary credentials from the instance metadata service, which the AWS SDKs retrieve and rotate automatically. No long-term keys exist on the instance, satisfying the security policy, and permissions are scoped to the role. This is the standard, recommended pattern for granting AWS API access to EC2 workloads.

Why this answer

An IAM role attached to the instance via an instance profile delivers temporary credentials through the instance metadata service, and the AWS SDK refreshes them automatically before expiry. Because no long-term access keys are stored on the instance, the security team's policy is satisfied while the application gains scoped DynamoDB permissions. This is the canonical approach for EC2 workloads.

Exam trap

The trap here is treating an encrypted parameter or an SSH key pair as equivalent to role-based temporary credentials, when only the instance profile removes long-term keys entirely.

15
Multi-Selecthard

A developer in Account A needs to use an AWS KMS customer managed key (CMK) located in Account B to encrypt data. Which TWO configuration steps are necessary to allow this cross-account access?

Select 2 answers
A.The KMS key policy in Account B must grant the developer's IAM ARN in Account A permission to use the key.
B.The developer's IAM policy in Account A must grant permission to use the KMS key ARN from Account B.
C.The developer must assume a role in Account B that has permissions to the KMS key.
D.The KMS key in Account B must be converted to a multi-Region key to be accessible from Account A.
E.An IAM Peering Connection must be established between Account A and Account B.
AnswersA, B

KMS key policies are the primary way to control access to keys. For cross-account access, the policy in the account that owns the key (Account B) must specifically list the external IAM principal from Account A and grant it the necessary actions like 'kms:Encrypt' or 'kms:GenerateDataKey'.

Why this answer

Cross-account KMS access requires permissions on both sides: the key policy in Account B must explicitly grant the developer's IAM principal ARN from Account A the kms:Encrypt (and related) permissions, since the key policy is the primary resource-based control for a CMK. Option A is correct because without this key policy statement, the Account A principal has no access regardless of its identity policy. Option B is also correct because the developer's identity-based IAM policy in Account A must allow the kms:Encrypt action against the specific key ARN in Account B, since IAM policies in the caller's account authorize the API call.

Option C is not required because the developer can be granted direct cross-account access via the key policy without assuming a role in Account B. Option D is unnecessary because multi-Region keys are for replicating keys across Regions, not for cross-account sharing. Option E is invalid because there is no such thing as an IAM Peering Connection; IAM is a global identity service and does not use network peering.

Exam trap

SCS-C03 often tests the dual-permission requirement for cross-account KMS access — candidates may forget that both the key policy in the key's account and the IAM policy in the caller's account must allow the action.

16
Multi-Selectmedium

An organization is using AWS Organizations to manage multiple accounts. The security team wants to use Service Control Policies (SCPs) to restrict certain actions. Which TWO statements accurately describe the behavior and limitations of SCPs?

Select 2 answers
A.SCPs affect all users and roles in a member account, including the root user.
B.SCPs applied to the Management Account restrict the actions of the Management Account's root user.
C.SCPs do not affect any service-linked roles used by AWS services to perform tasks.
D.SCPs can be used to grant permissions to a user who has no identity-based policies attached.
E.SCPs are the only way to enable cross-account access between member accounts in an organization.
AnswersA, C

Unlike identity-based policies, which do not apply to the root user of an account, SCPs set a hard limit that even the root user cannot bypass. This makes SCPs an essential tool for ensuring that member accounts comply with corporate security standards, regardless of the user's privilege level.

Why this answer

The explanation states that SCPs 'lack of effect on the management account', but Option B (which claims SCPs restrict the management account root user) is marked as wrong. Furthermore, option A and C are correct, and SCPs indeed do not affect service-linked roles. The explanation should be aligned to correctly justify why SCPs affect member accounts (including root) and do not affect service-linked roles.

Exam trap

Candidates often assume SCPs apply equally to the management account and service-linked roles, confusing organizational boundaries with standalone IAM permissions.

17
MCQhard

A security engineer is reviewing an IAM policy that grants access to an S3 bucket. The policy includes the condition "aws:SourceVpce": "vpce-1234567890abcdef0". The engineer wants to ensure that requests to the bucket only come from a specific VPC endpoint. However, some requests are still being allowed from other sources. What is the most likely reason for this?

A.The S3 bucket policy does not include a deny statement for requests that do not match the condition.
B.The S3 bucket is publicly accessible, so the condition is ignored.
C.The condition key should be "aws:SourceVpc" instead of "aws:SourceVpce".
D.The VPC endpoint policy is not configured to allow access to the S3 bucket.
AnswerA

In IAM policies, conditions are evaluated only when the policy is being evaluated for an allow. If a request does not match the condition, the allow statement is simply not applicable, but other policies might still allow the request. To enforce the condition, you need an explicit deny statement that denies requests when the condition is not met. Without a deny, the condition only restricts that specific allow, not the overall access.

Why this answer

IAM policy conditions in allow statements only restrict when that specific allow applies. If other policies or statements allow access without the condition, requests from other sources can still succeed. To enforce that requests must come from a specific VPC endpoint, you need an explicit deny statement that denies requests when the condition is not met, ensuring that no other allow can override it.

Exam trap

The trap here is assuming that adding a condition to an allow statement automatically blocks all other access, when in fact it only narrows that allow.

18
MCQmedium

A company has deployed a web application on Amazon EC2 that accesses an Amazon S3 bucket. The application currently uses an IAM user's long-term access keys stored in a configuration file. A security engineer must eliminate the use of long-term credentials and ensure that the application's permissions are automatically rotated. What should the engineer do?

A.Configure the application to use AWS Single Sign-On (SSO) credentials by integrating with the corporate identity provider.
B.Create an IAM role with the required S3 permissions and attach it to the EC2 instance profile.
C.Store the access keys in AWS Secrets Manager and configure automatic rotation every 90 days.
D.Generate a new IAM user access key pair and store it in AWS Systems Manager Parameter Store as a SecureString.
AnswerB

Attaching an IAM role to the EC2 instance profile provides temporary credentials that are automatically rotated by the instance metadata service. The application can retrieve these credentials without embedding long-term keys, meeting the requirement to eliminate static credentials and ensuring permissions are managed centrally via the role's policies.

Why this answer

The most secure and operationally efficient solution is to use an IAM role attached to the EC2 instance profile. This provides temporary credentials that are automatically rotated, eliminating the need for long-term access keys. The application can retrieve credentials from the instance metadata service, and permissions are controlled by the role's policies, simplifying management and improving security posture.

Exam trap

The trap here is assuming that storing long-term keys in a managed secret service like Secrets Manager or Parameter Store eliminates the security risk, when in fact it only masks the underlying issue of static credentials.

19
MCQmedium

A security engineer needs to allow an application running on an Amazon ECS task to access an Amazon DynamoDB table. The ECS task is hosted on an EC2 launch type. The engineer wants to follow the principle of least privilege and avoid storing AWS credentials in the task definition or container image. Which solution should the engineer implement?

A.Store the AWS credentials in AWS Secrets Manager and grant the ECS task permission to retrieve them using an IAM role attached to the EC2 instance.
B.Create an IAM role for the ECS task and specify it in the task definition; the ECS agent will provide temporary credentials to the containers.
C.Attach an IAM role to the EC2 instance hosting the ECS task and rely on the instance profile credentials for the application.
D.Generate a set of long-term IAM user credentials and inject them into the container as environment variables at runtime.
AnswerB

For ECS tasks on EC2, you can assign an IAM role to the task definition. The ECS agent retrieves temporary credentials from the Amazon ECS container agent and makes them available to the containers. This allows the application to access DynamoDB without embedding credentials, following least privilege and avoiding long-term keys.

Why this answer

The recommended approach is to create an IAM role for the ECS task and specify it in the task definition. The ECS agent then provides temporary credentials to the containers, allowing the application to access DynamoDB securely. This method adheres to least privilege because each task can have its own role with specific permissions, and it avoids storing long-term credentials in the task definition or container image.

Exam trap

The trap here is using the EC2 instance role instead of a task role, which grants all tasks on the instance the same permissions and violates least privilege.

20
MCQmedium

A company uses AWS Organizations with all features enabled. A security engineer has applied a Service Control Policy (SCP) at the Organizational Unit (OU) level that explicitly denies the 'iam:CreateUser' action. However, a specific IAM user in a member account within that OU has an administrator policy attached. What is the resulting behavior when this user attempts to create a new IAM user?

A.The user will successfully create the new IAM user because the administrator policy provides full access that overrides the SCP.
B.The request will fail because the SCP acts as a filter that restricts the maximum permissions available to any identity in the account.
C.The request will succeed only if the user uses the AWS Management Console, but it will fail if they use the AWS CLI or SDK.
D.The request will be sent to the master account for approval before the new IAM user is created in the member account.
AnswerB

Service Control Policies establish the permission boundaries for the entire account. Even if a user has an 'Allow' in their identity-based policy, the lack of an 'Allow' in the SCP or an 'Explicit Deny' in the SCP will result in the action being blocked during the evaluation.

Why this answer

SCPs in AWS Organizations act as permission guardrails that filter the maximum permissions available to identities in member accounts. Even if an IAM user has an administrator policy, an explicit Deny in an SCP overrides any Allow, so the iam:CreateUser action will be denied. SCPs do not grant permissions; they only restrict them.

Exam trap

SCS-C03 often tests the misconception that administrator policies override SCPs — candidates must remember that SCPs are guardrails that filter permissions, and an explicit Deny in an SCP always wins.

How to eliminate wrong answers

Option A is wrong because administrator policies cannot override an explicit Deny in an SCP; SCPs take precedence over identity-based policies. Option C is wrong because SCPs apply uniformly regardless of the access method (Console, CLI, SDK); there is no console-only bypass. Option D is wrong because AWS Organizations does not have an approval workflow for SCP-denied actions; the request simply fails with an AccessDenied error.

21
MCQeasy

A company is using AWS IAM Identity Center (successor to AWS Single Sign-On) to manage access to their AWS accounts. They want to automate the process of adding and removing users based on their status in an external identity provider. Which protocol should they use?

A.SAML 2.0 (Security Assertion Markup Language)
B.LDAP (Lightweight Directory Access Protocol)
C.OpenID Connect (OIDC)
D.SCIM (System for Cross-domain Identity Management)
AnswerD

SCIM is an open standard protocol specifically designed to automate the exchange of user identity information between identity domains or IT systems. AWS IAM Identity Center supports SCIM to allow external identity providers like Okta or Azure AD to automatically provision and deprovision users and groups.

Why this answer

Option D is correct because SCIM (System for Cross-domain Identity Management) is specifically designed for automating user provisioning and deprovisioning between identity providers and service providers like AWS IAM Identity Center. SCIM enables automatic synchronization of user and group information, ensuring that when a user is added or removed in the external IdP, the change is reflected in AWS IAM Identity Center.

Exam trap

SCS-C03 often tests the confusion between authentication protocols (SAML, OIDC) and provisioning protocols (SCIM). Candidates may incorrectly choose SAML or OIDC for automation, but only SCIM handles user lifecycle management.

How to eliminate wrong answers

Option A is wrong because SAML 2.0 is used for federated authentication (single sign-on) but does not handle automated user provisioning. Option B is wrong because LDAP is a directory access protocol, not a provisioning standard, and AWS IAM Identity Center does not use LDAP for user synchronization. Option C is wrong because OpenID Connect is an authentication protocol built on OAuth 2.0, used for SSO, but it does not automate user lifecycle management.

22
MCQhard

A security engineer needs to prevent IAM users from disabling CloudTrail. Which policy element is most appropriate?

A.Create an IAM policy that denies 'cloudtrail:StopLogging' to all users.
B.Use an SCP to explicitly deny 'cloudtrail:StopLogging' for the organization.
C.Enable MFA Delete on all CloudTrail S3 buckets.
D.Restrict access to the CloudTrail console via IAM groups.
AnswerB

SCPs are the perfect tool for organizational-wide guardrails. By applying a 'Deny' on 'cloudtrail:StopLogging' at the organization level, you ensure that no user or role, including administrative roles, can disable CloudTrail. This provides a central, immutable security control that meets stringent regulatory requirements for consistent logging across the entire enterprise.

Why this answer

Using an explicit 'Deny' on the 'cloudtrail:StopLogging' action in a Service Control Policy (SCP) or a Permission Boundary is the most effective way to prevent even administrators from disabling logging. By applying this as a guardrail, you ensure that audit integrity is maintained regardless of individual user privileges. This is crucial for compliance, as it creates an immutable audit trail that security teams can rely on during incident investigations.

Exam trap

Candidates often choose IAM policies instead of SCPs. While an IAM policy can deny actions, it can be bypassed by an administrator, whereas an SCP acts as a guardrail that even administrators cannot override.

23
MCQmedium

A company wants to allow project leads to create IAM roles for their team members but must ensure that these new roles cannot exceed a specific set of permissions, such as access to S3 and DynamoDB only. Which IAM feature should be used to enforce this limit?

A.IAM Groups with managed policies attached.
B.IAM Permissions Boundary.
C.Service Control Policies (SCPs) at the OU level.
D.Resource-based policies on S3 and DynamoDB.
AnswerB

A permissions boundary is an advanced feature where you set the maximum permissions that an identity-based policy can grant to an IAM entity. When a lead creates a role, they must attach this boundary, ensuring the role's effective permissions never exceed what is defined in the boundary policy.

Why this answer

IAM Permissions Boundary is used to set the maximum permissions that an identity-based policy can grant to an IAM entity. By attaching a permissions boundary to the roles that project leads create, you ensure that those roles cannot exceed the specified permissions (e.g., S3 and DynamoDB only). This allows project leads to create roles but within the boundary.

Exam trap

SCS-C03 often tests the misconception that SCPs or IAM groups can enforce permission limits on created roles, but the key is that permissions boundaries are specifically designed for this delegation scenario.

How to eliminate wrong answers

Option A is wrong because IAM Groups with managed policies do not limit the permissions of roles that project leads create; they only apply to users in the group. Option C is wrong because SCPs at the OU level apply to all accounts in the OU and are used for organization-wide restrictions, not for limiting permissions of roles created by specific users. Option D is wrong because resource-based policies on S3 and DynamoDB control access to those resources but do not limit the permissions of newly created roles.

24
Multi-Selecthard

A security engineer is configuring AWS IAM Identity Center (successor to AWS Single Sign-On) for a multi-account AWS organization. The engineer needs to ensure that users can access AWS accounts with permissions defined by their group membership. Which two actions should the engineer take to meet these requirements? (Choose two.)

Select 2 answers
A.Create IAM users in each AWS account and add them to IAM groups with the required policies.
B.Enable multi-factor authentication (MFA) for all users in the identity store.
C.Create permission sets that define the policies to be applied to users and groups in IAM Identity Center.
D.Configure an identity provider (IdP) in IAM Identity Center to synchronize users and groups from an external directory.
E.Assign users to groups in the IAM Identity Center identity store and assign permission sets to those groups for specific AWS accounts.
AnswersC, E

Permission sets are the primary way to define the level of access that users and groups have to AWS accounts in IAM Identity Center. They are templates that contain IAM policies and are assigned to users or groups for specific accounts. Creating appropriate permission sets is essential to grant the correct permissions based on group membership.

Why this answer

To enable access to AWS accounts based on group membership in IAM Identity Center, you must create permission sets that define the permissions, and then assign those permission sets to groups for specific AWS accounts. Users are placed in groups, and the group assignments determine the effective permissions. This approach centralizes access management and ensures that users receive the correct level of access when they sign in.

Exam trap

The trap here is focusing on authentication mechanisms like MFA or external IdP synchronization, which are important but do not directly address the requirement to define permissions based on group membership.

25
MCQmedium

Refer to the exhibit. A user with this policy cannot download files from the bucket. What is the most likely reason?

A.The policy is missing the 's3:ListAllMyBuckets' action.
B.The user lacks the 'kms:Decrypt' permission for the KMS key used by the bucket.
C.The resource ARN for 's3:GetObject' is incorrect.
D.The policy is missing an 'Effect: Deny' statement.
AnswerB

When an S3 bucket uses KMS-managed encryption, the user must have permission to use the KMS key to decrypt the data. Even with full S3 permissions, the request will fail if the user cannot access the KMS key. This is a frequent cause of 'Access Denied' errors in secure environments.

Why this answer

The most likely reason the user cannot download files is that the S3 bucket is encrypted with SSE-KMS, and the user's policy lacks the necessary `kms:Decrypt` permission on the KMS key. Even if the S3 policy allows `s3:GetObject`, KMS encryption requires explicit decrypt permissions. Without it, access is denied.

Exam trap

SCS-C03 often tests the misconception that S3 permissions alone are sufficient for encrypted objects; candidates forget that KMS permissions are also required for SSE-KMS encrypted objects.

How to eliminate wrong answers

Option A is wrong because `s3:ListAllMyBuckets` is only needed to list all buckets in the account, not to download objects from a specific bucket. Option C is wrong because if the resource ARN for `s3:GetObject` were incorrect, the policy would not grant access at all, but the question implies the policy is otherwise correct; the missing KMS permission is a more common cause. Option D is wrong because an explicit deny would override any allow, but the scenario describes a user who cannot download despite a policy that presumably allows it; the absence of a deny is not the issue.

26
MCQmedium

An auditor needs to verify which IAM policies are attached to a specific user. Which command provides this information?

A.aws iam list-user-policies --user-name <username>
B.aws iam list-attached-user-policies --user-name <username>
C.aws iam get-user-policy --user-name <username>
D.aws iam describe-user --user-name <username>
AnswerB

This is the correct CLI command to list all managed policies attached to an IAM user. Managed policies are the most common way to grant permissions, so listing them is the first step in assessing a user's permission set. This command provides a clear, concise list for audit reporting.

Why this answer

The AWS CLI is the primary tool for querying IAM metadata. The 'list-attached-user-policies' command specifically returns a list of all managed policies attached to the specified user. This is critical for security audits, where verifying the effective permissions of a principal is essential to ensure they match the requirements of their role and that no excessive privileges have been granted accidentally over time.

Exam trap

Candidates often confuse 'list-attached-user-policies' with 'list-user-policies'. The former shows managed policies, while the latter shows inline policies, leading to incomplete audit results if the wrong command is chosen.

27
MCQhard

A security engineer manages a workload where an IAM role in Account A assumes a role in Account B to call an AWS KMS API. The trust policy of the role in Account B contains a Condition element that requires aws:PrincipalArn to equal arn:aws:iam::111122223333:role/DataProcessor. During an incident review, the engineer observes that a different role in Account A, arn:aws:iam::111122223333:role/DataProcessorTemp, successfully assumed the role in Account B. Which statement best explains how the condition was satisfied?

A.The condition likely used a wildcard or partial-match operator such as StringLike with a pattern that DataProcessorTemp also satisfies, so the policy was written too permissively.
B.The condition matched because aws:PrincipalArn for an assumed-role session returns the ARN of the role that was assumed, not the role that initiated the AssumeRole call.
C.The role DataProcessorTemp inherited permissions from DataProcessor through a permissions boundary, so the condition matched the boundary ARN rather than the calling role ARN.
D.The aws:PrincipalArn condition key was ignored because a cross-account role assumption does not evaluate the principal's ARN in the target account trust policy.
AnswerA

If the trust policy used a partial-match operator like StringLike with a pattern such as arn:aws:iam::111122223333:role/DataProcessor*, both DataProcessor and DataProcessorTemp satisfy the condition. The observed successful assumption is consistent with a wildcard or prefix match. A strict StringEquals condition on the exact ARN would have denied the DataProcessorTemp role.

Why this answer

The key is that the condition was satisfied because the policy used a partial-match or wildcard form rather than an exact match. A strict StringEquals on the exact role ARN would allow only DataProcessor to assume the role. The observed success by DataProcessorTemp indicates the condition was broader than intended, which is a common least-privilege defect in cross-account trust policies.

Exam trap

The trap here is assuming that a condition referencing a specific role ARN always enforces an exact match, when a wildcard or partial-match operator can allow similarly named principals to satisfy it.

28
MCQmedium

An enterprise wants to grant an external partner secure, programmatic access to specific Amazon S3 buckets within their AWS account without creating individual IAM users. The solution must enforce rotating temporary credentials and adhere to the principle of least privilege. Which approach should a security engineer implement?

A.Create an IAM user for the partner with programmatic access keys, and attach an inline policy restricted to the specific S3 buckets.
B.Provision an IAM role in the partner account and configure an S3 bucket policy in the enterprise account trusting the external account.
C.Establish an IAM role in the enterprise account with a trust policy requiring an external ID, and grant permissions to the S3 buckets.
D.Configure cross-account resource sharing using AWS Resource Access Manager to directly share the S3 buckets with the partner AWS account.
AnswerC

IAM roles with trust policies specifying external IDs allow secure cross-account access. The external ID acts as a secret token known only to the authorized partner and the identity provider, preventing unauthorized assumption even if the role ARN is known.

Why this answer

The correct approach is to establish an IAM role in the enterprise account with a trust policy that requires an external ID, and grant permissions to the specific S3 buckets. This allows the external partner to assume the role and receive temporary credentials, adhering to least privilege and avoiding individual IAM users. The external ID adds security by preventing the confused deputy problem.

Exam trap

SCS-C03 often tests the difference between IAM roles and IAM users for cross-account access; candidates may choose IAM users for simplicity, but roles with external IDs are the secure best practice.

How to eliminate wrong answers

Option A is wrong because creating an IAM user with long-term access keys does not enforce rotating temporary credentials and violates least privilege by potentially granting broader access. Option B is wrong because provisioning an IAM role in the partner account and configuring a bucket policy trusting the external account does not enforce the use of an external ID and may not provide the necessary least privilege control from the enterprise side. Option D is wrong because AWS RAM is used to share resources like VPC subnets, not S3 buckets; S3 buckets are shared via bucket policies and IAM roles.

29
MCQmedium

A security engineer is configuring permissions boundaries to enforce least privilege. A developer has an IAM policy attached directly that allows s3:GetObject on all buckets, but a permissions boundary attached to the developer's IAM user only allows s3:GetObject on the 'public' bucket. The developer attempts to access an object in the 'private' bucket and receives an Access Denied error. What is the most likely cause?

A.The permissions boundary must be attached to the S3 bucket policy instead of the IAM user to restrict access, so the current configuration has no effect and the error is caused by an SCP.
B.The identity-based policy takes precedence over the permissions boundary, so access should be allowed; the error must be due to an S3 bucket policy denying access.
C.The permissions boundary is evaluated only when the IAM user assumes a role, so the direct IAM user permissions are unaffected, and the error is likely due to a missing s3:ListBucket permission.
D.The permissions boundary restricts the effective permissions to only what is allowed by both the identity-based policy and the boundary, so access to the 'private' bucket is denied.
AnswerD

Permissions boundaries set the maximum permissions an identity-based policy can grant. The effective permissions are the intersection of the identity-based policy and the boundary. Since the boundary only allows GetObject on the 'public' bucket, the developer cannot access the 'private' bucket even though the identity-based policy allows it.

Why this answer

Permissions boundaries define the maximum permissions that an identity-based policy can grant. The effective permissions are the intersection of the identity-based policy and the boundary. Here, the boundary only allows GetObject on the 'public' bucket, so even though the identity-based policy allows GetObject on all buckets, access to the 'private' bucket is denied.

Exam trap

The trap here is assuming that an identity-based policy that allows broader access will override a permissions boundary, when in fact the boundary acts as a filter that restricts the effective permissions.

30
Multi-Selecthard

A company is building a mobile application that requires users to authenticate before accessing private data stored in Amazon S3 and Amazon DynamoDB. Which THREE components or features of Amazon Cognito should be used to implement this securely?

Select 3 answers
A.Cognito User Pools to provide a sign-in and sign-up directory for the application users.
B.Cognito Identity Pools to exchange authentication tokens for temporary AWS credentials.
C.IAM roles with trust policies that allow the Cognito Identity Pool service principal to assume them.
D.Cognito Sync to store all user files directly from the mobile device to the cloud.
E.AWS Secrets Manager to store the Cognito User Pool Client Secret on the mobile device.
AnswersA, B, C

User Pools act as your identity provider, managing the user directory, authentication, and security features like MFA and password policies. They issue JSON Web Tokens (JWTs) upon successful login, which are then used by the application to prove the user's identity to other services or backends.

Why this answer

Option A is correct because Cognito User Pools act as the user directory that handles sign-up and sign-in, authenticating users and issuing JSON Web Tokens (ID, access, and refresh tokens) that the mobile app can present. Option B is correct because Cognito Identity Pools (federated identities) accept those User Pool tokens and exchange them for temporary, scoped AWS credentials via STS (AssumeRoleWithWebIdentity), which the app uses to call S3 and DynamoDB. Option C is correct because the Identity Pool must be configured with an IAM role whose trust policy allows cognito-identity.amazonaws.com to assume it, and that role's permissions policy grants access to the specific S3 buckets and DynamoDB tables, enforcing least privilege.

Option D is not needed because Cognito Sync is a deprecated data-synchronization service for user data, not an authentication or authorization component for accessing S3/DynamoDB. Option E is wrong because Secrets Manager is a server-side secret store and embedding a User Pool client secret on a mobile device would expose it; public mobile clients should use a client without a secret plus PKCE.

Exam trap

SCS-C03 often tests confusion between User Pools (authentication) and Identity Pools (authorization/credentials), and the misconception that Cognito Sync or Secrets Manager play a role in securing S3/DynamoDB access from mobile apps.

31
MCQhard

A company uses a centralized identity account to manage users who assume roles in various production accounts. They want to pass the user's department name as a session tag during the 'sts:AssumeRole' call to enforce fine-grained access control in the production accounts. What must be configured to support this?

A.The production account's role must have a resource-based policy allowing the 'iam:TagSession' action.
B.The user in the identity account must have the 'iam:AddUserToGroup' permission for the production group.
C.The role's trust policy in the production account must allow the 'sts:TagSession' action for the identity account principal.
D.The department name must be added as a permanent tag to the IAM role itself in the production account.
AnswerC

To pass session tags, the trust policy of the role being assumed must explicitly grant the 'sts:TagSession' permission to the principal that is assuming the role. This ensures the production account trusts the identity account to provide valid and authorized attributes for the session.

Why this answer

To pass session tags during an sts:AssumeRole call, the IAM role's trust policy must include the 'sts:TagSession' action. Additionally, the caller must have the 'sts:TagSession' permission. The explanation should explicitly mention that the trust policy must allow the 'sts:TagSession' action to authorize the passing of tags during the assumption process.

Exam trap

Candidates often confuse resource-based tags (IAM role tags) with session tags. Session tags are transient and passed at runtime, whereas role tags are permanent attributes of the IAM role resource.

32
MCQmedium

A security engineer is configuring AWS IAM Identity Center for a company that uses Microsoft Active Directory on-premises. The company wants to use their existing AD credentials to access AWS accounts and applications. The engineer needs to set up the identity source. Which configuration should the engineer choose to meet these requirements?

A.Configure AD Connector to connect to the on-premises Active Directory, and then set AD Connector as the identity source for IAM Identity Center.
B.Create IAM users for each employee and enable AWS Single Sign-On with a custom identity broker.
C.Configure an external identity provider using SAML 2.0 and connect it to AWS IAM Identity Center.
D.Set up AWS Directory Service for Microsoft Active Directory (AWS Managed Microsoft AD) and connect it as the identity source for IAM Identity Center.
AnswerA

AD Connector is a proxy service that redirects directory requests to your on-premises Microsoft Active Directory. By configuring AD Connector and setting it as the identity source for IAM Identity Center, users can sign in with their existing AD credentials. This meets the requirement to use on-premises AD without replicating directory data to AWS.

Why this answer

AD Connector is a proxy that connects IAM Identity Center to on-premises Active Directory, allowing users to authenticate with their existing AD credentials. It avoids the need to replicate directory data or manage separate identities. This is the recommended approach for integrating on-premises AD with IAM Identity Center for AWS access.

Exam trap

The trap here is confusing AWS Managed Microsoft AD with AD Connector; AD Connector proxies to on-premises AD, while AWS Managed Microsoft AD is a standalone directory in AWS that requires a trust relationship to use on-premises credentials.

33
MCQeasy

A company wants to identify any S3 buckets or IAM roles in their AWS account that are accessible by external AWS accounts or public users. Which AWS service provides this functionality by analyzing resource-based policies?

A.AWS Trusted Advisor
B.Amazon GuardDuty
C.AWS Config
D.AWS IAM Access Analyzer
AnswerD

IAM Access Analyzer is designed to identify resources shared with external principals. It uses mathematical proof-based reasoning to analyze resource-based policies and provides findings for S3 buckets, IAM roles, KMS keys, Lambda functions, and SQS queues that are accessible from outside your account or organization.

Why this answer

AWS IAM Access Analyzer is specifically designed to analyze resource-based policies (such as S3 bucket policies, IAM role trust policies, KMS key policies, etc.) and identify resources that are shared with external entities, including other AWS accounts, organizations, or public users. It uses automated reasoning to determine if a resource policy grants access to principals outside your zone of trust (your AWS account or organization). This directly matches the requirement to find S3 buckets or IAM roles accessible externally.

Exam trap

SCS-C03 often tests the distinction between services that monitor for threats (GuardDuty) versus those that analyze policies for external access (Access Analyzer), and candidates may confuse AWS Config's compliance checks with Access Analyzer's external access analysis.

How to eliminate wrong answers

Option A is wrong because AWS Trusted Advisor provides best-practice checks and recommendations across cost, security, performance, and fault tolerance, but it does not perform deep analysis of resource-based policies to identify external access; its security checks are limited to common misconfigurations like open S3 buckets but not IAM roles or comprehensive external access analysis. Option B is wrong because Amazon GuardDuty is a threat detection service that continuously monitors for malicious activity and unauthorized behavior using machine learning and threat intelligence, but it does not analyze resource-based policies to identify resources shared externally. Option C is wrong because AWS Config is a configuration recording and compliance service that evaluates resource configurations against desired policies, but it does not natively analyze resource-based policies to determine external accessibility; it can track changes but requires custom rules or manual analysis to identify external access.

34
MCQmedium

Which IAM configuration helps prevent the 'confused deputy' problem when accessing cross-account resources?

A.MFA requirement on the role.
B.External ID.
C.Role session name.
D.Source IP condition.
AnswerB

The External ID is the primary mechanism for preventing the confused deputy problem in cross-account role assumptions. It serves as a secret value shared only between the trustor and the trustee, ensuring that the trust relationship is validated correctly during the assume-role process and preventing unauthorized access to resources.

Why this answer

The 'External ID' is specifically designed to mitigate the confused deputy problem. When a third party assumes a role in your account, they must provide a unique identifier that you have pre-shared with them. This ensures that the third party is acting on behalf of the correct customer, preventing an attacker from tricking the service into accessing the wrong account's resources.

It is a critical security control for cross-account integrations.

Exam trap

Candidates confuse multi-factor authentication with cross-account protection, selecting MFA instead of the specific identifier needed for third-party access.

35
MCQmedium

A security engineer is tasked with granting a developer in Account A access to an Amazon S3 bucket located in Account B. The developer needs to perform PutObject and GetObject operations. According to security best practices for cross-account access, which configuration provides the most secure and manageable solution?

A.Create an IAM user in Account B for the developer and provide the static access keys to the developer in Account A.
B.Define a resource-based policy on the S3 bucket in Account B that grants the developer's IAM ARN in Account A direct access.
C.Create an IAM role in Account B with the required S3 permissions and a trust policy allowing Account A, then let the developer assume it.
D.Configure a VPC Peering connection between Account A and Account B to allow the developer to access the S3 bucket privately.
AnswerC

This method follows the principle of least privilege and uses AWS Security Token Service for temporary access. The trust policy defines who can assume the role, and the identity-based policy defines what they can do. This architecture is scalable and aligns with the AWS Well-Architected Framework security pillar.

Why this answer

Cross-account access is best managed by assuming an IAM role in the destination account. This approach generates temporary security credentials via AWS STS, reducing the risk associated with long-term credentials. It centralizes permission management within the account owning the resource while allowing the source account to control which identities can initiate the switch.

Exam trap

Candidates often suggest using resource-based policies directly for the user. However, assuming a role is the standard security best practice for cross-account access as it uses temporary credentials.

36
MCQmedium

An application running on EC2 needs to access DynamoDB tables. What is the most secure way to provide these permissions?

A.Embed IAM access keys directly into the application code.
B.Store IAM access keys in a configuration file on the EC2 instance.
C.Assign an IAM role to the EC2 instance via an instance profile.
D.Create a public DynamoDB table to allow unauthenticated access.
AnswerC

Using IAM roles with instance profiles is the gold standard for EC2 security. It provides temporary, short-lived credentials that are automatically rotated by the AWS environment. The application uses the AWS SDK to retrieve these credentials, ensuring no sensitive data is stored on the disk or exposed in the code.

Why this answer

Assigning an IAM role to the EC2 instance via an instance profile is the most secure method because it provides temporary, automatically rotated credentials to the instance without embedding long-term access keys. The instance profile allows the EC2 instance to assume the role and retrieve temporary security credentials from the Instance Metadata Service (IMDS), which the AWS SDK uses automatically. This eliminates the risk of hardcoded keys being exposed or leaked, and permissions are managed centrally through IAM policies attached to the role.

Exam trap

SCS-C03 often tests the misconception that storing access keys in a secure location (like a configuration file) is acceptable, but the exam expects you to recognize that any use of long-term credentials is less secure than IAM roles with temporary credentials.

How to eliminate wrong answers

Option A is wrong because embedding IAM access keys directly into application code exposes long-term credentials that can be accidentally committed to version control, logged, or extracted by attackers, and they do not rotate automatically. Option B is wrong because storing IAM access keys in a configuration file on the EC2 instance still uses long-term credentials that can be compromised if the instance is breached, and it requires manual rotation. Option D is wrong because DynamoDB does not support public, unauthenticated access; all requests must be signed with valid AWS credentials, and making a table public is not a supported feature and would violate security best practices.

37
MCQmedium

A security engineer must provide temporary read-only access to an S3 bucket for an external auditor without creating IAM users. Which method adheres to the principle of least privilege?

A.Create an IAM user with read-only permissions and provide the auditor with the access keys.
B.Attach a bucket policy that grants access to the auditor's specific IP address range.
C.Configure a cross-account IAM role with an external ID and read-only permissions.
D.Generate a pre-signed URL for every object in the bucket and share them with the auditor.
AnswerC

Cross-account roles with an External ID provide a secure, scalable way to grant access. The External ID prevents the confused deputy problem, ensuring that the trust relationship is validated during the assume-role request. This temporary access mechanism is the safest way to authorize external parties without managing permanent user accounts.

Why this answer

Configuring a cross-account IAM role with an external ID and read-only permissions allows the external auditor to assume the role and obtain temporary credentials, adhering to least privilege without creating IAM users. The external ID is used to prevent the confused deputy problem, ensuring that only the intended auditor can assume the role.

Exam trap

SCS-C03 often tests the misconception that creating IAM users with access keys is acceptable for external parties, but the key is that cross-account roles with external IDs provide temporary, least-privilege access.

How to eliminate wrong answers

Option A is wrong because creating an IAM user with access keys provides long-term credentials, which violates least privilege and increases security risk. Option B is wrong because a bucket policy granting access to a specific IP range does not authenticate the auditor and can be bypassed if the IP changes; it also does not provide temporary credentials. Option D is wrong because generating pre-signed URLs for every object is impractical for a large bucket, and pre-signed URLs are temporary but do not provide a comprehensive access mechanism; they also require sharing many URLs and do not enforce least privilege at the bucket level.

38
MCQmedium

A security auditor from a third-party company needs to access your AWS account to review CloudTrail logs stored in an S3 bucket. They suggest using a cross-account IAM role. Which mechanism should you implement to specifically mitigate the 'confused deputy' security risk during this cross-account access?

A.Require an ExternalID in the IAM role's trust policy and ensure the auditor provides it when assuming the role.
B.Create a new IAM user with an access key and secret key specifically for the third-party auditor's use.
C.Add a resource-based policy to the S3 bucket that allows the third-party's AWS account ID directly.
D.Restrict the trust policy of the IAM role to only allow the specific IP address of the auditor's office.
AnswerA

The ExternalID condition in the trust policy ensures that the STS service validates a unique string provided by the third party. This specifically addresses the confused deputy issue by requiring a secret known only to the auditor and the account owner before granting temporary credentials to the session.

Why this answer

The confused deputy problem occurs when a third party (the auditor) uses their legitimate access to a role to trick the role into acting on behalf of another customer who also uses that same third party. Requiring a unique ExternalID in the role's trust policy ensures the third party can only assume the role when explicitly acting on behalf of your specific account, because the ExternalID is a shared secret between you and the auditor. This is the AWS-documented mitigation for cross-account third-party access.

Exam trap

SCS-C03 often tests the confusion between authentication mechanisms (IP restrictions, account IDs) and the specific confused deputy mitigation — candidates pick IP allowlisting or direct bucket policies, missing that ExternalID is the canonical answer for third-party cross-account access.

How to eliminate wrong answers

Option B is wrong because creating long-lived IAM users with access keys for a third party violates least privilege and best practice — keys can leak, are hard to rotate, and don't address the confused deputy problem at all. Option C is wrong because a resource-based S3 bucket policy granting the third party's account ID directly still allows any principal in that account (or anyone who compromises it) to access the bucket, and it doesn't use role assumption or ExternalID. Option D is wrong because IP-based trust policy conditions are brittle (auditor IPs change, NAT, remote work) and do not mitigate the confused deputy problem — the deputy is still a legitimate caller from an allowed IP.

39
MCQhard

Refer to the exhibit. This S3 bucket policy is applied to a bucket named 'marketing-data'. What is the effect of this policy regarding access to the objects in the bucket?

A.It allows any IAM user or role within any account belonging to the AWS Organization 'o-1234567890' to read objects.
B.It makes the bucket public to anyone on the internet as long as they are using an AWS account.
C.It allows access only if the S3 bucket itself is owned by the organization 'o-1234567890'.
D.It requires that the request must originate from a VPC endpoint that is tagged with the organization ID.
AnswerA

The 'aws:PrincipalOrgID' condition key filters the 'Principal: *' to only include identities that are part of the specified AWS Organization. This effectively restricts access to all members of the organization while granting them the 's3:GetObject' permission for the objects in the 'marketing-data' bucket.

Why this answer

The bucket policy condition uses 'aws:PrincipalOrgID' to restrict access to principals that belong to the specified AWS Organization. This means any IAM user or role in any account within that organization can read objects, assuming they have the necessary IAM permissions. The policy does not make the bucket public to the internet; it only grants access to authenticated principals within the organization.

Exam trap

SCS-C03 often tests the confusion between 'aws:PrincipalOrgID' and public access; candidates may mistakenly think that any organization-based condition makes the bucket public, but it only grants access to authenticated principals within that organization.

How to eliminate wrong answers

Option B is wrong because the policy does not grant public access; it requires the principal to be part of the specified AWS Organization, so anonymous internet users are excluded. Option C is wrong because the condition checks the principal's organization membership, not the bucket's ownership; the bucket owner is irrelevant to the 'aws:PrincipalOrgID' condition. Option D is wrong because the policy does not reference VPC endpoints or tags; it uses the organization ID condition key, which is evaluated based on the principal's account's organization membership.

40
MCQmedium

A security engineer needs to grant an application running on an Amazon EC2 instance access to an Amazon S3 bucket. The application must not store any long-term credentials. The engineer has created an IAM role with the necessary S3 permissions. Which step should the engineer take to allow the EC2 instance to assume the role?

A.Generate an access key for the role and store it in AWS Systems Manager Parameter Store, then retrieve it from the instance.
B.Create an instance profile, add the role to it, and associate the instance profile with the EC2 instance.
C.Attach the IAM role directly to the EC2 instance using the AWS Management Console.
D.Configure the EC2 instance to use AWS IAM Identity Center (successor to AWS Single Sign-On) for temporary credentials.
AnswerB

An instance profile is a container for an IAM role that EC2 uses to pass role information to the instance. When you create a role for EC2, the console automatically creates an instance profile with the same name. Associating the instance profile with the instance allows the application to retrieve temporary credentials via the instance metadata service. This is the correct method to grant the EC2 instance access without long-term credentials.

Why this answer

To grant an EC2 instance access to AWS services without long-term credentials, you must use an IAM role. The role is delivered to the instance through an instance profile. The instance profile is associated with the instance, allowing the application to obtain temporary credentials from the instance metadata service.

This approach adheres to security best practices by eliminating the need to embed or distribute static credentials.

Exam trap

The trap here is assuming that an IAM role can be attached directly to an EC2 instance without an instance profile, overlooking the required container.

41
MCQhard

A security engineer is configuring a permissions boundary for a new IAM role that will be used by a third-party application. The engineer wants to ensure that the role can never perform any action that is not explicitly allowed by the permissions boundary, even if an administrator later attaches a more permissive identity-based policy. Which statement accurately describes how permissions boundaries affect effective permissions?

A.The permissions boundary is only enforced for actions that are not allowed by any identity-based policy, serving as a fallback deny.
B.The permissions boundary is evaluated after identity-based policies, and if an action is allowed by either, it is permitted.
C.The permissions boundary overrides any identity-based policy, ensuring that only actions allowed by the boundary are permitted, regardless of other policies.
D.The permissions boundary acts as a filter that limits the maximum permissions the role can have, but it does not grant permissions on its own.
AnswerD

A permissions boundary defines the maximum permissions an identity-based policy can grant, but it does not grant any permissions itself. The effective permissions are the intersection of the identity-based policies and the permissions boundary. Therefore, even if a more permissive policy is attached later, the role cannot exceed the boundary's allowed actions.

Why this answer

Permissions boundaries are an advanced IAM feature that sets the maximum permissions an identity-based policy can grant. They do not grant permissions themselves; the effective permissions are the intersection of the boundary and the identity-based policies. This ensures that even if a more permissive policy is attached, the role cannot exceed the boundary's limits, providing a guardrail against privilege escalation.

Exam trap

The trap here is thinking that a permissions boundary can grant permissions or override other policies, when it only limits the maximum permissions that identity-based policies can provide.

42
Multi-Selecthard

An organization is migrating to AWS and needs to enforce security guardrails across multiple accounts. Which TWO actions should the security team perform to ensure compliance? (Select TWO)

Select 2 answers
A.Apply SCPs at the root level to restrict specific AWS services in member accounts.
B.Assign IAM policies directly to the root user of every member account.
C.Use IAM Permission Boundaries on all developer-created roles.
D.Configure individual IAM users in every account to ensure fine-grained control.
E.Enable AWS CloudTrail only in the primary management account.
AnswersA, C

SCPs applied at the root or organizational unit level are effective at enforcing global compliance standards. They restrict the maximum permissions available to any user or role within the account, ensuring that sensitive services or regions are off-limits, which is fundamental for maintaining a secure and compliant AWS multi-account environment.

Why this answer

Implementing AWS Organizations allows for centralized management and governance. Service Control Policies (SCPs) act as guardrails, defining the maximum permissions allowed within an account, regardless of user identity. Combining SCPs with IAM Permission Boundaries provides a robust multi-layered defense strategy.

This setup ensures that even if an administrator mistakenly grants broad permissions, the guardrails remain in effect, effectively preventing accidental or malicious privilege escalation across the entire AWS organization.

Exam trap

Candidates rely solely on standard IAM user policies, forgetting that developers can self-escalate privileges unless constrained by guardrails.

43
MCQhard

Refer to the exhibit. What is the effective permission for a user with this policy regarding 'production-bucket'?

A.The user can perform all actions, including deleting the production bucket.
B.The user cannot delete the production bucket, but can perform all other S3 actions.
C.The user cannot perform any S3 actions because the Deny statement takes precedence.
D.The policy is invalid due to conflicting statements.
AnswerB

The explicit Deny on 's3:DeleteBucket' for the specific bucket resource overrides the broad 's3:*' allowance. However, the Allow statement still applies to all other S3 actions and resources. This demonstrates how to combine broad permissions with specific, granular denials to achieve a secure yet flexible configuration.

Why this answer

The policy contains an Allow for all S3 actions on the production bucket and an explicit Deny for s3:DeleteBucket on that same bucket. In AWS IAM, an explicit Deny always overrides any Allow. Therefore, the user can perform all S3 actions except deleting the production bucket.

The policy is valid because Allow and Deny statements can coexist; the Deny simply takes precedence for the specified action.

Exam trap

SCS-C03 often tests the misconception that conflicting Allow and Deny statements invalidate a policy, when in fact explicit Deny always wins and the policy remains valid.

How to eliminate wrong answers

Option A is wrong because the explicit Deny for s3:DeleteBucket overrides the Allow, so the user cannot delete the bucket. Option C is wrong because the Deny only applies to s3:DeleteBucket, not to all S3 actions — the Allow still permits other actions. Option D is wrong because conflicting statements are not invalid; AWS IAM evaluates them with Deny taking precedence, and the policy remains syntactically and semantically valid.

44
Multi-Selecthard

Which THREE conditions are required for a user to assume an IAM role in another account? (Select THREE)

Select 3 answers
A.The trusting account must have a role with a trust policy allowing the trusted account ID.
B.The user in the trusted account must have a policy allowing 'sts:AssumeRole' for the role ARN.
C.The user must have the AdministratorAccess managed policy attached.
D.The user must call the 'sts:AssumeRole' API with the correct Role ARN.
E.The trusting account must share the root user password with the trusted account.
AnswersA, B, D

The trust policy acts as the resource-based policy for the role. It defines who is allowed to assume the role. Without the trust account ID explicitly listed, the cross-account request will be rejected by the AWS STS service, preventing unauthorized cross-account access attempts.

Why this answer

To assume a role in another account, three conditions must be met: 1) The trusting account's role must have a trust policy that permits the trusted account (or specific principal) to assume it. 2) The identity in the trusted account must have an IAM policy that grants the 'sts:AssumeRole' permission for the target role ARN. 3) The identity must programmatically call the 'sts:AssumeRole' API with the target role ARN.

Exam trap

Candidates often confuse the trust policy (on the role) with the permissions policy (on the user). Both are required.

45
MCQhard

Refer to the exhibit. An administrator applied the given S3 bucket policy to allow secure retrieval of objects. However, users connecting through a NAT gateway with an Elastic IP inside the specified CIDR block are still receiving Access Denied errors. What is the most likely cause of this behavior?

A.The bucket policy lacks a corresponding explicit deny statement to override implicit denies from other global accounts.
B.The aws:SourceIp condition key evaluates the public IP of the client rather than the NAT gateway when traversing an internet gateway.
C.Requests routed through Interface VPC Endpoints for Amazon S3 preserve the original client private IP, causing the public IP condition to fail.
D.The action s3:GetObject requires additional list permissions on the bucket level that are absent from the provided policy statement.
AnswerB

Traffic traversing a NAT gateway has its private source IP translated to the public Elastic IP of the NAT gateway. Therefore, AWS evaluates the NAT gateway public IP as the source IP, not the private IP of the originating client instance.

Why this answer

When traffic passes through a NAT gateway to reach an S3 bucket over the public internet, the source IP address seen by S3 is the public Elastic IP of the NAT gateway, not the client's private IP. If the bucket policy's aws:SourceIp condition is configured with the client's internal CIDR block, the condition will fail because the request originates from the NAT gateway's public IP. Option B correctly identifies that the condition evaluates the NAT gateway's public IP rather than the client's internal IP.

Exam trap

Assuming that a NAT gateway preserves the original client IP address in the packet header for AWS global condition keys like aws:SourceIp.

46
MCQmedium

A security engineer at a financial services company manages 40 AWS accounts under AWS Organizations. Auditors must be able to review IAM policies in every member account, but the company's policy forbids creating individual IAM users in member accounts. The auditors already authenticate to a corporate SAML 2.0 identity provider. Which approach allows the auditors to review IAM policies in all member accounts with the LEAST administrative overhead?

A.Share the management account root credentials with the auditors and instruct them to use the IAM console's account switcher to review each member account.
B.Enable AWS IAM Identity Center in the management account, connect the corporate SAML 2.0 IdP, and assign the auditors a permission set with the ReadOnlyAccess policy to all member accounts.
C.Create an IAM user in each member account, attach the ReadOnlyAccess managed policy, and distribute access keys to the auditors.
D.Create one IAM role in each member account with a SAML 2.0 trust policy referencing the corporate IdP, then give auditors the role ARNs to assume manually.
AnswerB

IAM Identity Center federates the existing corporate IdP, and a single permission set with ReadOnlyAccess can be assigned across all 40 accounts through AWS Organizations, so no IAM users are created anywhere. Auditors sign in with their corporate credentials and receive temporary role sessions, which satisfies the no-IAM-user policy while minimizing per-account administration to one assignment.

Why this answer

AWS IAM Identity Center centralized permission sets let one assignment grant consistent read-only access to every account in the organization, and its SAML 2.0 connection reuses the corporate IdP so no new credentials are issued. Because no IAM users are provisioned in member accounts and administration happens once at the organization level, this option satisfies both the policy constraint and the least-overhead requirement.

Exam trap

The trap here is assuming that federation requires creating an IAM role with a SAML trust policy in every account, when Identity Center can propagate a single permission set organization-wide.

47
MCQhard

Refer to the exhibit. A developer is attempting to upload a file to 'my-secure-bucket' using the S3 console but receives an Access Denied error. The developer is not specifying any encryption settings during the upload. Based on the provided IAM policy, what is the reason for the failure?

A.The S3 bucket lacks a bucket policy that explicitly allows the PutObject action for the developer.
B.The explicit Deny statement takes precedence because the upload request does not include the required KMS encryption header.
C.The developer's IAM user does not have the 'kms:GenerateDataKey' permission required to encrypt the object.
D.The resource ARN in the policy is incorrect because it should include the bucket name without the trailing slash.
AnswerB

In AWS IAM, an explicit deny always overrides an allow. The policy denies 'PutObject' if the encryption header is not 'aws:kms'. Since the developer did not specify encryption, the condition evaluates to true for the deny statement, resulting in an Access Denied error for the operation.

Why this answer

The IAM policy contains an explicit Deny statement that requires the upload request to include a specific KMS encryption header (e.g., x-amz-server-side-encryption-aws-kms-key-id). Since the developer is not specifying any encryption settings, the condition for the Deny is met, and the explicit Deny overrides any Allow. Therefore, the upload fails with Access Denied.

Exam trap

SCS-C03 often tests the precedence of explicit Deny over Allow and the conditions that trigger Deny; candidates may focus on missing Allow statements or KMS permissions instead of recognizing the Deny condition.

How to eliminate wrong answers

Option A is wrong because the bucket policy is not the issue; the IAM policy itself has an explicit Deny that takes precedence. Option C is wrong because the developer may have kms:GenerateDataKey permission, but the Deny is triggered by the missing header, not by lack of KMS permissions. Option D is wrong because the resource ARN in the policy is correct; the trailing slash is not the cause of the failure.

48
MCQeasy

An application running on an Amazon EC2 instance needs to access files in an Amazon S3 bucket. What is the most secure way to provide the application with the necessary credentials?

A.Store AWS access keys in a configuration file within the application's source code.
B.Assign an IAM role to the EC2 instance using an instance profile.
C.Use the root user's access keys to ensure the application has uninterrupted access to all resources.
D.Create an IAM user with S3 permissions and hardcode its credentials in the EC2 User Data script.
AnswerB

Using an IAM role allows the application to retrieve temporary security credentials from the Instance Metadata Service (IMDS). This is the most secure method because the credentials are automatically rotated by AWS and are never stored permanently on the instance or in the application code.

Why this answer

AWS recommends using IAM roles for EC2 instances to provide temporary credentials. This avoids the need to store sensitive access keys in application code or configuration files. The EC2 instance profile automatically manages the rotation and delivery of these credentials to the instance via the metadata service.

Exam trap

Test-takers often recommend storing access keys in environment variables or configuration files on the instance, forgetting that IAM roles via instance profiles provide secure, automatically rotated temporary credentials.

49
MCQeasy

Which of the following is considered a security best practice for managing the AWS account root user?

A.Enable Multi-Factor Authentication (MFA) and only use the root user for tasks that specifically require it.
B.Create an IAM policy that denies all actions for the root user to prevent accidental changes.
C.Share the root user credentials with all senior administrators so that there is always a backup available.
D.Generate an access key for the root user and use it for automated scripts that require high privileges.
AnswerA

Enabling MFA is the single most important step for securing the root user. Since the root user cannot be restricted by IAM policies, its security relies entirely on strong credentials and a second factor of authentication to prevent unauthorized access to the most sensitive account functions.

Why this answer

The AWS account root user has unrestricted access to all resources and services in the account. Protecting this identity is the highest priority in AWS security. Best practices include avoiding the use of the root user for daily tasks, enabling multi-factor authentication, and securely storing the credentials.

Most administrative tasks should be performed using IAM roles with the AdministratorAccess policy.

Exam trap

Candidates might mistakenly believe that the root user can be disabled or restricted via IAM policies, or that sharing credentials is a valid 'backup' strategy.

50
MCQmedium

A security engineer is configuring AWS IAM Identity Center to grant a group of developers access to multiple AWS accounts. The engineer wants to ensure that permissions are assigned based on the developers' job functions without modifying each account's IAM policies individually. Which IAM Identity Center component should the engineer use to achieve this?

A.Permission sets
B.IAM policies attached to each IAM user in the management account
C.SAML 2.0 identity provider configuration in each AWS account
D.AWS Organizations service control policies (SCPs)
AnswerA

Permission sets are templates in IAM Identity Center that define the level of access for users and groups across AWS accounts. They allow centralized management of permissions without editing individual account IAM policies. By assigning a permission set to a group, the engineer ensures consistent access based on job function, and the permission set is provisioned as an IAM role in each target account.

Why this answer

Permission sets in IAM Identity Center allow administrators to define and assign permissions to users and groups centrally, and these permissions are applied across multiple AWS accounts without manual IAM policy changes in each account. This meets the requirement of job-function-based access and minimizes administrative effort.

Exam trap

The trap here is confusing permission sets with IAM policies or SCPs, which do not directly grant cross-account access based on group membership.

51
MCQeasy

A security team wants to identify which IAM roles in their AWS account have been granted permissions that allow access from external AWS accounts or public entities. Which AWS service should they use to automate this audit?

A.AWS Secrets Manager
B.IAM Access Analyzer
C.AWS Shield
D.Amazon Inspector
AnswerB

IAM Access Analyzer helps you identify the resources in your account, such as Amazon S3 buckets or IAM roles, that are shared with an external entity. This lets you identify unintended access to your resources and data, which is a critical part of the security auditing process.

Why this answer

IAM Access Analyzer is designed to analyze resource policies and identify resources that are shared with external entities, including IAM roles that can be assumed by principals from other AWS accounts or public entities. It automates the audit of external access, making it the correct tool for this task.

Exam trap

SCS-C03 often tests the confusion between services like Amazon Inspector (vulnerability scanning) and IAM Access Analyzer (access auditing); candidates may pick Inspector thinking it covers IAM, but it does not.

How to eliminate wrong answers

Option A is wrong because AWS Secrets Manager is for managing secrets, not for auditing IAM permissions. Option C is wrong because AWS Shield is a DDoS protection service, not an IAM auditing tool. Option D is wrong because Amazon Inspector is a vulnerability management service that scans workloads for software vulnerabilities and network exposure, but it does not analyze IAM role trust policies for external access.

Ready to test yourself?

Try a timed practice session using only Identity And Access Management questions.