AWS - CloudFormationYou ran drift detection but the results show 'NOT_CHECKED' for some resources. What could cause this?AThe resource is deleted from the stackBThe resource is in sync with the templateCThe stack is in rollback stateDThe resource type does not support drift detectionCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand 'NOT_CHECKED' status meaningThis status means drift detection cannot check that resource type.Step 2: Compare optionsOnly The resource type does not support drift detection correctly explains why some resources are not checked.Final Answer:The resource type does not support drift detection -> Option DQuick Check:'NOT_CHECKED' = Unsupported resource type [OK]Quick Trick: 'NOT_CHECKED' means unsupported resource type for drift detection [OK]Common Mistakes:Confusing 'NOT_CHECKED' with deletion or rollbackAssuming 'NOT_CHECKED' means resource is fine
Master "CloudFormation" in AWS9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More AWS Quizzes Architecture Best Practices - Performance efficiency pillar - Quiz 6medium Cost Optimization - Right-sizing resources - Quiz 13medium Cost Optimization - Data transfer cost awareness - Quiz 15hard ECS and Fargate - ECS with ALB integration - Quiz 8hard ECS and Fargate - ECS service auto scaling - Quiz 11easy EKS - EKS networking with VPC CNI - Quiz 10hard Serverless Architecture - Lambda with API Gateway pattern - Quiz 1easy Serverless Architecture - Step Functions for workflows - Quiz 9hard Serverless Architecture - Lambda with DynamoDB Streams - Quiz 9hard Serverless Architecture - Lambda with API Gateway pattern - Quiz 11easy