What are the MOST likely reasons for this situation?
(Choose two.)
The Administrator must configure the VPC Flow Logs to have them sent to AWS CloudTrail.
The Administrator has waited less than ten minutes for the log group to be created in CloudWatch.
The account VPC Flow Logs have been disabled by using a service control policy.
No relevant traffic has been sent since the VPC Flow Logs were created
The account has Amazon GuardDuty enabled.
Explanations:
VPC Flow Logs do not need to be configured to be sent to AWS CloudTrail. They are sent to CloudWatch Logs, not CloudTrail.
CloudWatch log groups for VPC Flow Logs may take up to 10 minutes to appear after creation. Waiting less than 10 minutes can result in the log group not being found.
Service control policies (SCPs) do not disable VPC Flow Logs by default. SCPs typically restrict AWS service actions for accounts, but would not prevent CloudWatch log creation specifically for VPC Flow Logs.
If no relevant traffic has been sent, the VPC Flow Logs might not show any data. A log group will still exist, but with no logs to display.
Amazon GuardDuty is unrelated to VPC Flow Logs or their creation. GuardDuty analyzes security data but does not affect the logging of VPC traffic.
As I see it, the answer is:
The Administrator has waited less than ten minutes for the log group to be created in CloudWatch.
From what I’ve heard, the answer is:
The Administrator has waited less than ten minutes for the log group to be created in CloudWatch.