Refer to the exhibit. An experienced AWS administrator is creating a new virtual public cloud (VPC) flow log with the settings shown in the exhibit. What is the purpose of this configuration?

Question

Exhibit

Options

• ATo maximize the number of logs saved
• BTo store the logs for further analysis
• CTo monitor the logs in real time
• DTo troubleshoot a log flow issue

• A
  3% (1)
• B
  92% (34)
• C
  5% (2)

Explanation

Storing VPC flow logs - whether in Amazon S3 or CloudWatch Logs - is the defining purpose of creating a flow log, making B correct. The configuration shown sets a destination (S3 bucket or log group) where captured network traffic metadata is persisted for later querying, auditing, or security analysis.

• A is wrong because flow logs don't have a "maximize logs" setting; you capture what you configure (Accepted, Rejected, or All traffic), not more or less.
• C is wrong because flow logs are not real-time - they're delivered with a delay (typically 10–15 minutes), so they're unsuitable for live monitoring; use tools like VPC Traffic Mirroring for that.
• D is wrong because troubleshooting a log flow issue is a use case that comes after logs are stored - the act of creating the flow log itself is about enabling storage, not diagnosing a problem.

Memory tip: Think of VPC Flow Logs as a security camera DVR - the DVR stores footage (S3/CloudWatch) for later review; it doesn't alert you live (C), it doesn't pick what to record maximally (A), and setting it up isn't the same as watching the footage to fix something (D).

No community discussion yet for this question.