A company begins to use AWS WAF after experiencing an increase in traffic to the...

AWS WAF supportsWAF loggingas a dedicated feature that can deliver logs to destinations such as Amazon S3 (commonly via Kinesis Data Firehose). These logs contain rich request details (rule matches, action taken, headers, URI, source IP, etc.) that are essential for determining whether traffic spikes are due to application-layer attacks. For analysis with low operational overhead, storing logs inS3and querying them withAmazon Athenais a standard pattern. Usingpartition projectionfurther reduces administrative work by avoiding manual partition management and enabling efficient queries over time-based prefixes.

Options A and D incorrectly route WAF logs through CloudTrail; WAF request logs are not delivered “to a CloudTrail trail.” CloudTrail records AWS API activity, not per-request WAF inspection logs. Option B describes querying S3 data directly with OpenSearch using “partition projection,” which is an Athena/Glue concept; OpenSearch is typically used by ingesting data into an index (often via Firehose), not by directly querying S3 objects as a table in that manner.

Therefore, enabling WAF logs to S3 and analyzing them with Athena using partition projection is the correct solution.