Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 4
Question 30
A team assumes an S3 bucket Allow automatically grants a cross-account IAM role all access in its home account. What is missing?
- Evaluate both the cross-account resource policy and the caller's applicable identity authorization.
- Grant the sending account permission on the destination log subscription receiver policy.
- Write a scoped SNS topic resource policy permitting the specified service with source conditions.
- Authorize the cross-account role to use the KMS key through its key policy and IAM policy.
Explanation
Correct Answer
A:Cross-account authorization often needs grants on both sides and no overriding explicit Deny. Test a principal with no matching identity permissions.
Incorrect Answers
B:Cross-account service integrations need correct destination resource permissions. Evaluate both the cross-account resource policy and the caller's applicable identity authorization. Test a principal with no matching identity permissions.
C:Resource policies can grant service principals controlled cross-account publication. Evaluate both the cross-account resource policy and the caller's applicable identity authorization. Test a principal with no matching identity permissions.
D:Cross-account encrypted object access requires both S3 access and applicable KMS authorization. Evaluate both the cross-account resource policy and the caller's applicable identity authorization. Test a principal with no matching identity permissions.
Question 31
An AWS service principal needs to publish events to an SNS topic owned by another account. What secures publishing?
- Grant sns:Publish in a caller-side identity policy without changing the destination topic policy.
- Write a scoped SNS topic resource policy permitting the specified service with source conditions.
- Grant the sending account permission on the destination log subscription receiver policy.
- Allow the application role to assume a scoped role in account A.
Explanation
Correct Answer
B:Resource policies can grant service principals controlled cross-account publication. Publish an authorized service event and deny an unrelated source ARN.
Incorrect Answers
A:An identity-based Allow does not automatically authorize an AWS service principal to publish to another account’s SNS topic. The destination topic must explicitly permit the service principal and scope the source in its resource policy.
C:Cross-account service integrations need correct destination resource permissions. Write a scoped SNS topic resource policy permitting the specified service with source conditions. Publish an authorized service event and deny an unrelated source ARN.
D:Cross-account IAM role assumption provides temporary credentials subject to trust and permissions. Write a scoped SNS topic resource policy permitting the specified service with source conditions. Publish an authorized service event and deny an unrelated source ARN.
Question 32
A CloudWatch Logs subscription in one account sends events to another account's receiver. Which policy boundary is required?
- Grant the sending account permission on the destination log subscription receiver policy.
- Write a scoped SNS topic resource policy permitting the specified service with source conditions.
- Evaluate both the cross-account resource policy and the caller's applicable identity authorization.
- Use per-customer role ARNs with expected external IDs in trust conditions.
Explanation
Correct Answer
A:Cross-account service integrations need correct destination resource permissions. Validate deliveries from the approved source account only.
Incorrect Answers
B:Resource policies can grant service principals controlled cross-account publication. Grant the sending account permission on the destination log subscription receiver policy. Validate deliveries from the approved source account only.
C:Cross-account authorization often needs grants on both sides and no overriding explicit Deny. Grant the sending account permission on the destination log subscription receiver policy. Validate deliveries from the approved source account only.
D:Third-party role trust should bind the intended principal and customer identifier. Cross-account service integrations need correct destination resource permissions.
Question 33
A business needs its corporate SAML identity provider to issue AWS console sessions. What should the security team establish?
- Remove the person's IAM Identity Center account assignment or identity-source group membership.
- Federate the IdP to IAM Identity Center and assign permission sets.
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
- Assign distinct IAM Identity Center permission sets to each account.
Explanation
Correct Answer
B:Federated sign-in avoids distributing unrelated local IAM user passwords. Sign in with the corporate account and verify the assigned AWS account role.
Incorrect Answers
A:Central identity assignments reduce orphaned per-account human credentials. Federate the IdP to IAM Identity Center and assign permission sets. Sign in with the corporate account and verify the assigned AWS account role.
C:Web identity federation can provide ephemeral permissions to eligible workloads. Federate the IdP to IAM Identity Center and assign permission sets. Sign in with the corporate account and verify the assigned AWS account role.
D:Permission sets apply account-specific IAM permissions to authorized workforce identities. Federate the IdP to IAM Identity Center and assign permission sets. Sign in with the corporate account and verify the assigned AWS account role.
Question 34
A workforce user needs read-only access to account A but developer access to account B. How should assignments differ?
- Assign distinct IAM Identity Center permission sets to each account.
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
- Remove the person's IAM Identity Center account assignment or identity-source group membership.
- Federate all workforce users into one unrestricted administrator permission set across both accounts.
Explanation
Correct Answer
A:Permission sets apply account-specific IAM permissions to authorized workforce identities. Inspect both account assignments under the same user.
Incorrect Answers
B:Web identity federation can provide ephemeral permissions to eligible workloads. Assign distinct IAM Identity Center permission sets to each account. Inspect both account assignments under the same user.
C:Central identity assignments reduce orphaned per-account human credentials. Assign distinct IAM Identity Center permission sets to each account. Inspect both account assignments under the same user.
D:Identity federation centralizes sign-in but does not justify the same administrative permissions in both accounts. The user needs read-only in account A and developer in B; assign distinct scoped permission sets to each account.
Question 35
A company removes a consultant from its identity provider yet their AWS CLI role credentials remain valid briefly. What explains the behavior?
- Federate the IdP to IAM Identity Center and assign permission sets.
- Use STS AssumeRoleWithSAML with the approved SAML provider and role.
- Assign distinct IAM Identity Center permission sets to each account.
- Account for temporary session expiration and revocation controls after identity removal.
Explanation
Correct Answer
D:Existing STS sessions have finite lifetimes independent of later IdP access changes. Confirm new session issuance fails and monitor existing expiration.
Incorrect Answers
A:Federated sign-in avoids distributing unrelated local IAM user passwords. Account for temporary session expiration and revocation controls after identity removal. Confirm new session issuance fails and monitor existing expiration.
B:STS exchanges signed assertions for temporary AWS role credentials. Account for temporary session expiration and revocation controls after identity removal. Confirm new session issuance fails and monitor existing expiration.
C:Permission sets apply account-specific IAM permissions to authorized workforce identities. Account for temporary session expiration and revocation controls after identity removal. Confirm new session issuance fails and monitor existing expiration.
Question 36
An application wants its own customers to sign in with social identities, not AWS operator workforce roles. Which service better fits?
- Account for temporary session expiration and revocation controls after identity removal.
- Assign distinct IAM Identity Center permission sets to each account.
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
- Use Amazon Cognito user pools for customer application authentication.
Explanation
Correct Answer
D:Cognito supports application-user directories and federation rather than staff account administration. Test a customer-issued token against an application endpoint.
Incorrect Answers
A:Existing STS sessions have finite lifetimes independent of later IdP access changes. Use Amazon Cognito user pools for customer application authentication. Test a customer-issued token against an application endpoint.
B:Permission sets apply account-specific IAM permissions to authorized workforce identities. Use Amazon Cognito user pools for customer application authentication. Test a customer-issued token against an application endpoint.
C:Web identity federation can provide ephemeral permissions to eligible workloads. Use Amazon Cognito user pools for customer application authentication. Test a customer-issued token against an application endpoint.
Question 37
A corporate SAML assertion should assume an IAM role for a short AWS session. Which AWS API exchange fits?
- Use STS AssumeRoleWithSAML with the approved SAML provider and role.
- Remove the person's IAM Identity Center account assignment or identity-source group membership.
- Account for temporary session expiration and revocation controls after identity removal.
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
Explanation
Correct Answer
A:STS exchanges signed assertions for temporary AWS role credentials. Inspect role trust, audience and token validity.
Incorrect Answers
B:Central identity assignments reduce orphaned per-account human credentials. Use STS AssumeRoleWithSAML with the approved SAML provider and role. Inspect role trust, audience and token validity.
C:Existing STS sessions have finite lifetimes independent of later IdP access changes. Use STS AssumeRoleWithSAML with the approved SAML provider and role. Inspect role trust, audience and token validity.
D:Web identity federation can provide ephemeral permissions to eligible workloads. Use STS AssumeRoleWithSAML with the approved SAML provider and role. Inspect role trust, audience and token validity.
Question 38
An OIDC-authenticated Kubernetes workload should obtain AWS credentials without placing IAM user keys in pods. Which pattern fits?
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
- Federate the IdP to IAM Identity Center and assign permission sets.
- Assign distinct IAM Identity Center permission sets to each account.
- Account for temporary session expiration and revocation controls after identity removal.
Explanation
Correct Answer
A:Web identity federation can provide ephemeral permissions to eligible workloads. Verify a different service account cannot assume the role.
Incorrect Answers
B:Federated sign-in avoids distributing unrelated local IAM user passwords. Map the OIDC service account identity to an IAM role with a restricted trust condition. Verify a different service account cannot assume the role.
C:Permission sets apply account-specific IAM permissions to authorized workforce identities. Map the OIDC service account identity to an IAM role with a restricted trust condition. Verify a different service account cannot assume the role.
D:Existing STS sessions have finite lifetimes independent of later IdP access changes. Web identity federation can provide ephemeral permissions to eligible workloads.
Question 39
A central identity team needs a new member's cloud account access removed in one place. Which management process fits?
- Assign distinct IAM Identity Center permission sets to each account.
- Remove the person's IAM Identity Center account assignment or identity-source group membership.
- Federate the IdP to IAM Identity Center and assign permission sets.
- Account for temporary session expiration and revocation controls after identity removal.
Explanation
Correct Answer
B:Central identity assignments reduce orphaned per-account human credentials. Test that fresh sign-ins to previously assigned accounts fail.
Incorrect Answers
A:Permission sets apply account-specific IAM permissions to authorized workforce identities. Remove the person's IAM Identity Center account assignment or identity-source group membership. Test that fresh sign-ins to previously assigned accounts fail.
C:Federated sign-in avoids distributing unrelated local IAM user passwords. Remove the person's IAM Identity Center account assignment or identity-source group membership. Test that fresh sign-ins to previously assigned accounts fail.
D:Existing STS sessions have finite lifetimes independent of later IdP access changes. Central identity assignments reduce orphaned per-account human credentials.
Question 40
An organization uses an external IdP but IAM usernames are still individually provisioned for everyone. What architectural simplification is appropriate?
- Replace routine IAM-user console access with federated workforce roles.
- Map the OIDC service account identity to an IAM role with a restricted trust condition.
- Assign distinct IAM Identity Center permission sets to each account.
- Federate the IdP to IAM Identity Center and assign permission sets.
Explanation
Correct Answer
A:Human SSO can centralize authentication and issue role sessions without permanent IAM users. Audit IAM users for redundant human sign-in credentials.
Incorrect Answers
B:Web identity federation can provide ephemeral permissions to eligible workloads. Replace routine IAM-user console access with federated workforce roles. Audit IAM users for redundant human sign-in credentials.
C:Permission sets apply account-specific IAM permissions to authorized workforce identities. Replace routine IAM-user console access with federated workforce roles. Audit IAM users for redundant human sign-in credentials.
D:Federated sign-in avoids distributing unrelated local IAM user passwords. Replace routine IAM-user console access with federated workforce roles. Audit IAM users for redundant human sign-in credentials.