
Ultimate access to all questions.
In a company with hundreds of AWS accounts managed through AWS Organizations, a dedicated security tooling account serves as the delegated administrator for Amazon GuardDuty and AWS Security Hub. This setup is configured to automatically enable GuardDuty and Security Hub across all accounts, both existing and new. During a control test to ensure the security team's ability to detect and respond to security events, an Amazon EC2 instance was launched to generate a DNS finding by making DNS requests against a test domain. Despite these efforts, no GuardDuty finding was recorded in the Security Hub delegated administrator account. What might be the cause for the absence of this finding?
A
VPC flow logs were not turned on for the VPC where the EC2 instance was launched.
B
The VPC where the EC2 instance was launched had the DHCP option configured for a custom OpenDNS resolver.
C
The GuardDuty integration with Security Hub was never activated in the AWS account where the finding was generated.
D
Cross-Region aggregation in Security Hub was not configured.