AWS - Identity and Access ManagementAn inline policy attached to a role is not granting expected permissions. What is a possible reason?AInline policies do not support resource-level permissions.BManaged policies override inline policies and block permissions.CThe inline policy is attached to the wrong role.DThe role must be deleted and recreated to apply inline policies.Check Answer
Step-by-Step SolutionSolution:Step 1: Verify policy attachmentPermissions depend on correct attachment of the inline policy to the intended role.Step 2: Check other optionsManaged policies do not override inline policies negatively; inline policies support resource-level permissions; roles do not require recreation.Final Answer:The inline policy is attached to the wrong role. -> Option CQuick Check:Correct attachment is key for inline policy effect = C [OK]Quick Trick: Check policy attached to correct role [OK]Common Mistakes:Believing managed policies block inline policiesThinking inline policies lack resource-level controlAssuming role recreation is needed
Master "Identity and Access Management" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes AWS Account and Billing - Billing dashboard overview - Quiz 8hard EC2 Fundamentals - Why EC2 matters for compute - Quiz 14medium Identity and Access Management - Multi-factor authentication setup - Quiz 2easy Identity and Access Management - Why IAM is foundational - Quiz 5medium Identity and Access Management - Policy evaluation logic - Quiz 9hard Identity and Access Management - Assuming roles for temporary access - Quiz 5medium S3 Fundamentals - Creating S3 buckets - Quiz 5medium VPC Fundamentals - Internet Gateway for public access - Quiz 12easy VPC Fundamentals - Default VPC overview - Quiz 3easy VPC Fundamentals - Why VPC provides network isolation - Quiz 14medium