AWS - Advanced SecurityAn AWS Config rule is not triggering evaluations after resource changes. What is the most common misconfiguration causing this?AConfig Aggregator is disabledBConfig Recorder is not recording the resource typeCThe rule is set to manual trigger onlyDThe AWS Config console is not refreshedCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand evaluation triggersAWS Config rules trigger evaluations when the recorder tracks changes for relevant resource types.Step 2: Identify common causeIf the recorder does not record the resource type, the rule won't trigger on changes.Final Answer:Config Recorder is not recording the resource type -> Option BQuick Check:Recorder missing resource = no evaluations [OK]Quick Trick: Recorder must track resource types for rules [OK]Common Mistakes:Assuming Aggregator controls evaluationsConfusing manual trigger with automaticThinking console refresh affects triggers
Master "Advanced Security" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Advanced Security - Secrets Manager for credentials - Quiz 10hard Advanced Security - KMS for key management - Quiz 15hard CloudFormation - Outputs for cross-stack references - Quiz 6medium CloudFormation - Outputs for cross-stack references - Quiz 1easy CloudFormation - Creating stacks - Quiz 3easy CloudFormation - Outputs for cross-stack references - Quiz 8hard CloudFormation - Parameters for customization - Quiz 4medium ECS and Fargate - Fargate serverless containers - Quiz 14medium Route 53 - Domain registration - Quiz 9hard Serverless Architecture - Cognito for user authentication - Quiz 13medium