[Solved] You have set up GuardDuty with a delegated administrator account to monitor multiple AWS member accounts.... What could be a misconfiguration causing this? | AWS

AWS - Advanced Security

You have set up GuardDuty with a delegated administrator account to monitor multiple AWS member accounts. Some member accounts are not reporting findings. What could be a misconfiguration causing this?

AGuardDuty requires manual activation on the delegated administrator account

BGuardDuty is not supported in the AWS region where member accounts reside

CThe delegated administrator account does not have billing permissions

DMember accounts have not accepted the invitation to be monitored by the delegated administrator

Step-by-Step Solution

Solution:

Step 1: Understand GuardDuty multi-account setup
Member accounts must accept the invitation from the delegated administrator to send findings.
Step 2: Identify common misconfigurations
If invitations are not accepted, member accounts won't report findings despite being linked.
Final Answer:
Member accounts have not accepted the invitation to be monitored by the delegated administrator -> Option D
Quick Check:
Member accounts must accept GuardDuty invitations to send findings [OK]

Quick Trick: Member accounts must accept GuardDuty invitations to report findings [OK]

Common Mistakes:

Assuming billing permissions affect findings reporting
Believing GuardDuty is unsupported in certain regions without verification
Thinking delegated admin requires manual activation

Master "Advanced Security" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More AWS Quizzes

What could be a misconfiguration causing this?

Step 1: Understand GuardDuty multi-account setup

Step 2: Identify common misconfigurations

Final Answer:

Quick Check:

Want More Practice?