AWS - Advanced Security
After activating GuardDuty in your AWS account, you notice no security findings are generated. Which of the following could explain this behavior?
After activating GuardDuty in your AWS account, you notice no security findings are generated. Which of the following could explain this behavior?
medium📝 Debug Q6 of 15
Step-by-Step Solution
Solution:
Step 1: Understand GuardDuty operation
GuardDuty continuously analyzes AWS data sources for threats without manual scans.Step 2: Check data sources
If no suspicious activity is detected in VPC Flow Logs, CloudTrail, or DNS logs, no findings will be generated.Final Answer:
No suspicious activity has been detected in the monitored data sources -> Option DQuick Check:
GuardDuty auto-detects threats; no agent or manual scans needed [OK]
Quick Trick: GuardDuty auto-generates findings only when threats exist [OK]
Common Mistakes:
- Assuming manual scans are required
- Believing agents must be installed on EC2 instances
- Thinking GuardDuty only runs during certain hours
Master "Advanced Security" in AWS
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore AWS Quizzes