312-39 Questions Bank

A trend analysis report is designed to show how incident frequency, types, severity, and impact change over time, which is exactly what leadership needs for investment decisions. The scenario is about demonstrating an increase in malware incidents over six months and linking them to phishing as an entry vector. A trend report can quantify growth rates, highlight recurring patterns, identify peak periods, compare pre- and post-control effectiveness, and estimate business risk (downtime, remediation hours, affected users). This supports a clear business case for budget: if phishing-driven malware is increasing, investments in email filtering and user training directly address the root cause and should reduce future incident volume. A monitoring summary report may provide a snapshot but often lacks time-series depth. A real-time monitoring report focuses on current status and active alerts, not long-term justification. An incident report is typically focused on a single event and is useful for lessons learned but not for demonstrating systemic trends. From a SOC management perspective, trend analysis aligns technical evidence with strategic decisions, making it the most effective report type to support funding for preventive controls and awareness programs.

Amazon GuardDuty is the fully managed AWS threat detection service designed to analyze CloudTrail events, VPC Flow Logs, and DNS logs to identify suspicious and malicious activity. It uses threat intelligence and behavioral models to detect patterns such as unusual API calls, anomalous network connections (including known malicious destinations), and suspicious DNS activity—directly matching the scenario requirements. Macie is focused on discovering and protecting sensitive data (especially in S3) through classification and data exposure detection, not broad threat detection across API/network/DNS. AWS Config is a configuration compliance and drift monitoring service; it tracks resource configurations and policy compliance but does not provide threat detection based on network and activity logs. Security Hub aggregates and normalizes findings from multiple AWS security services and partners; it is a central view and compliance/finding management layer, but it relies on services like GuardDuty to generate threat findings. From a SOC perspective, GuardDuty provides the near-real-time detection signals the team needs, and those findings can be forwarded to SIEM/SOAR workflows for triage and response.

To filter the output of the‘show logging’ command to include entries related to a specific access control list, Peter should use the ‘include’ keyword followed by the access list number. The correct command would be ‘show logging | include 210’. This command will display all log entries that contain the string ‘210’, which is the number of the access control list he wants to monitor.

To monitor and visualize Tor traffic hitting the network, John would need data sources that can provide detailed information about the source IP addresses of incoming traffic, as well as the capability to resolve these IP addresses to more identifiable information such as hostnames or geographical locations. DHCP logs, or other log sources capable of maintaining detailed IP address records and facilitating IP-to-Name resolution, would be suitable for this purpose. This data would allow John to create a dashboard in the SIEM system that maps the source IP addresses of Tor traffic to their corresponding locations or identities, providing insights into where the Tor traffic is originating. While web server logs (options B, C, and D) can provide IP addresses, they might not offer the same level of detail or resolution capabilities as DHCP logs or similar network-level logs for this specific use case.