Amazon AWS Certified Solutions Architect - Associate SAA-C03 Practice Test 5
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.
Question 41
An internal API must accept S3 requests only from an approved VPC endpoint. Which bucket policy condition limits the network path?
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
- Check aws:PrincipalOrgID in the role trust conditions where supported.
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
- Use an applicable kms:ViaService condition in the key policy.
Explanation
Correct Answer
A:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Test access through the endpoint and from an unapproved internet path.
Incorrect Answers
B:Organization-ID conditions constrain trust to principals in the approved organization. Use an appropriate aws:SourceVpce condition on the bucket access policy. Test access through the endpoint and from an unapproved internet path.
C:MFA condition keys can constrain eligible API actions for authenticated sessions. Use an appropriate aws:SourceVpce condition on the bucket access policy. Test access through the endpoint and from an unapproved internet path.
D:KMS service conditions scope cryptographic operations to approved integrations. Use an appropriate aws:SourceVpce condition on the bucket access policy. Test access through the endpoint and from an unapproved internet path.
Question 42
An IAM role may tag EC2 instances only for its own business unit. What authorization technique ties tags to the caller?
- Use an applicable kms:ViaService condition in the key policy.
- Compare aws:PrincipalTag and request or resource tag keys in IAM conditions.
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
- Require the approved s3:RequestObjectTag key and value on PutObject.
Explanation
Correct Answer
B:Condition keys can require consistent ownership labels before operations succeed. Attempt a mismatched department tag in a test role session.
Incorrect Answers
A:KMS service conditions scope cryptographic operations to approved integrations. Compare aws:PrincipalTag and request or resource tag keys in IAM conditions. Attempt a mismatched department tag in a test role session.
C:MFA condition keys can constrain eligible API actions for authenticated sessions. Compare aws:PrincipalTag and request or resource tag keys in IAM conditions. Attempt a mismatched department tag in a test role session.
D:S3 request tag conditions restrict accepted object metadata at upload. Compare aws:PrincipalTag and request or resource tag keys in IAM conditions. Attempt a mismatched department tag in a test role session.
Question 43
A team wants to enforce HTTPS for all S3 object reads regardless of identity policy Allow. What bucket rule is appropriate?
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
- Deny S3 requests when aws:SecureTransport is false.
- Compare aws:PrincipalTag and request or resource tag keys in IAM conditions.
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
Explanation
Correct Answer
B:An explicit TLS transport condition helps block unencrypted HTTP object requests. Test signed HTTPS access and a deliberately rejected HTTP request.
Incorrect Answers
A:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Deny S3 requests when aws:SecureTransport is false. Test signed HTTPS access and a deliberately rejected HTTP request.
C:Condition keys can require consistent ownership labels before operations succeed. Deny S3 requests when aws:SecureTransport is false. Test signed HTTPS access and a deliberately rejected HTTP request.
D:MFA condition keys can constrain eligible API actions for authenticated sessions. Deny S3 requests when aws:SecureTransport is false. Test signed HTTPS access and a deliberately rejected HTTP request.
Question 44
An external role should assume a target role only from one approved AWS Organization. Which trust-policy key is relevant?
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
- Require the approved s3:RequestObjectTag key and value on PutObject.
- Use an applicable kms:ViaService condition in the key policy.
- Check aws:PrincipalOrgID in the role trust conditions where supported.
Explanation
Correct Answer
D:Organization-ID conditions constrain trust to principals in the approved organization. Test an outsider principal against the trust policy.
Incorrect Answers
A:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Check aws:PrincipalOrgID in the role trust conditions where supported. Test an outsider principal against the trust policy.
B:S3 request tag conditions restrict accepted object metadata at upload. Check aws:PrincipalOrgID in the role trust conditions where supported. Test an outsider principal against the trust policy.
C:KMS service conditions scope cryptographic operations to approved integrations. Check aws:PrincipalOrgID in the role trust conditions where supported. Test an outsider principal against the trust policy.
Question 45
A role may invoke a deployment service only if a required MFA context is present. What condition can it enforce?
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
- Use an applicable kms:ViaService condition in the key policy.
- Compare aws:PrincipalTag and request or resource tag keys in IAM conditions.
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
Explanation
Correct Answer
A:MFA condition keys can constrain eligible API actions for authenticated sessions. Compare calls from MFA and non-MFA sessions.
Incorrect Answers
B:KMS service conditions scope cryptographic operations to approved integrations. Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful. Compare calls from MFA and non-MFA sessions.
C:Condition keys can require consistent ownership labels before operations succeed. Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful. Compare calls from MFA and non-MFA sessions.
D:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful. Compare calls from MFA and non-MFA sessions.
Question 46
A policy should let a service write only objects carrying an approved classification tag. What request condition is relevant?
- Compare aws:PrincipalTag and request or resource tag keys in IAM conditions.
- Check aws:PrincipalOrgID in the role trust conditions where supported.
- Require the approved s3:RequestObjectTag key and value on PutObject.
- Use an applicable kms:ViaService condition in the key policy.
Explanation
Correct Answer
C:S3 request tag conditions restrict accepted object metadata at upload. Test tagged and untagged uploads.
Incorrect Answers
A:Condition keys can require consistent ownership labels before operations succeed. Require the approved s3:RequestObjectTag key and value on PutObject. Test tagged and untagged uploads.
B:Organization-ID conditions constrain trust to principals in the approved organization. Require the approved s3:RequestObjectTag key and value on PutObject. Test tagged and untagged uploads.
D:KMS service conditions scope cryptographic operations to approved integrations. Require the approved s3:RequestObjectTag key and value on PutObject. Test tagged and untagged uploads.
Question 47
A finance role may decrypt a KMS key only through a specific AWS service. What policy condition limits service use?
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
- Use an applicable kms:ViaService condition in the key policy.
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
- Require the approved s3:RequestObjectTag key and value on PutObject.
Explanation
Correct Answer
B:KMS service conditions scope cryptographic operations to approved integrations. Try direct decrypt and approved service-mediated decrypt separately.
Incorrect Answers
A:MFA condition keys can constrain eligible API actions for authenticated sessions. Use an applicable kms:ViaService condition in the key policy. Try direct decrypt and approved service-mediated decrypt separately.
C:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Use an applicable kms:ViaService condition in the key policy. Try direct decrypt and approved service-mediated decrypt separately.
D:S3 request tag conditions restrict accepted object metadata at upload. Use an applicable kms:ViaService condition in the key policy. Try direct decrypt and approved service-mediated decrypt separately.
Question 48
A VPC endpoint must be the source of API calls but CloudTrail shows identity policies are valid. Where should the engineer inspect an additional Deny?
- Inspect endpoint policies and resource-policy network conditions for the specific API.
- Use aws:MultiFactorAuthPresent in the applicable identity policy where meaningful.
- Use an appropriate aws:SourceVpce condition on the bucket access policy.
- Use an applicable kms:ViaService condition in the key policy.
Explanation
Correct Answer
A:Permission evaluation includes network-related endpoint and resource constraints beyond identity grants. Compare the failing request context with the expected endpoint identity.
Incorrect Answers
B:MFA condition keys can constrain eligible API actions for authenticated sessions. Inspect endpoint policies and resource-policy network conditions for the specific API. Compare the failing request context with the expected endpoint identity.
C:Source endpoint conditions restrict supported requests to a particular VPC endpoint. Inspect endpoint policies and resource-policy network conditions for the specific API. Compare the failing request context with the expected endpoint identity.
D:KMS service conditions scope cryptographic operations to approved integrations. Inspect endpoint policies and resource-policy network conditions for the specific API. Compare the failing request context with the expected endpoint identity.
Question 49
A role trust policy permits an external principal, but that caller lacks permission to invoke sts:AssumeRole. What is missing?
- Set the Lambda service principal in the execution-role trust policy.
- Grant a narrowly scoped caller-side AssumeRole permission where cross-account authorization requires it.
- Replace account-wide trust with the specific approved principal or constrained conditions.
- Require and preserve an identifiable role session name or source identity.
Explanation
Correct Answer
B:Trust and caller identity authorization are distinct in cross-account role assumption. Inspect the STS AccessDenied context and both policies.
Incorrect Answers
A:A service execution role must trust the service that assumes it. Grant a narrowly scoped caller-side AssumeRole permission where cross-account authorization requires it. Inspect the STS AccessDenied context and both policies.
C:Trust policies should identify the smallest intended caller set. Grant a narrowly scoped caller-side AssumeRole permission where cross-account authorization requires it. Inspect the STS AccessDenied context and both policies.
D:STS session identity fields help correlate assumed-role activity to the originating user. Grant a narrowly scoped caller-side AssumeRole permission where cross-account authorization requires it. Inspect the STS AccessDenied context and both policies.
Question 50
A Lambda role is allowed to access DynamoDB, but its trust relationship lists EC2 only. What should be corrected?
- Set the Lambda service principal in the execution-role trust policy.
- Replace account-wide trust with the specific approved principal or constrained conditions.
- Supply a session policy intersecting with the base role permissions.
- Transmit permitted STS session tags and enforce them in IAM policy conditions.
Explanation
Correct Answer
A:A service execution role must trust the service that assumes it. Rerun the Lambda invocation after updating the trust policy.
Incorrect Answers
B:Trust policies should identify the smallest intended caller set. Set the Lambda service principal in the execution-role trust policy. Rerun the Lambda invocation after updating the trust policy.
C:Session policies cannot elevate rights; they reduce the assumed role's effective scope. Set the Lambda service principal in the execution-role trust policy. Rerun the Lambda invocation after updating the trust policy.
D:Session attributes enable ABAC across temporary role sessions under controlled trust. Set the Lambda service principal in the execution-role trust policy. Rerun the Lambda invocation after updating the trust policy.