Cisco 300-740 Exam With Confidence Using Practice Dumps

The Secure Cloud Analytics alert indicates suspicious heartbeat-based connections from an internal server (ip-10-201-0-16) to multiple suspicious IPs over UDP/port 53 (DNS). This behavior suggests command-and-control (C2) activity or botnet communications.

B: Alerting the incident response (IR) team is a critical next step in escalating a verified threat as per SCAZT Section 6 (Threat Response, Pages 114–117).

D: Blocking the identified malicious IPs on perimeter firewalls or network access control devices is an appropriate containment step to disrupt communication.

Reinstallation (A/E) is premature without a full forensic investigation. Validating IDS logs (C) is useful but not immediate response-focused compared to actions B and D.

The policy includes three rules under the Apps scope. Rule #1 allows HR to communicate with IT on TCP port 23 (Telnet), but it is marked as “Default.” Rule #2 denies the same HR-to-IT Telnet traffic and is marked as “Absolute,” which takes precedence over any default rule. In Cisco Secure Workload (Tetration), an “Absolute” rule will override both “Default” and inherited rules. Therefore, even though there’s an allow in Rule #1, the deny in Rule #2 prevents HR from using Telnet to connect to IT.

Rule 3 allows all traffic (including SSH) from 10.1.0.0/30 during the hours of 18:00–08:00, which directly conflicts with Rule 1 that is intended to deny SSH at those same hours. Since firewall rules are evaluated top-down and Rule 3 allows traffic during the exact period where SSH should be blocked, deleting Rule 3 will allow Rule 1 to apply correctly.

This behavior is explained in SCAZT Section 3 (Network and Cloud Security, Pages 72–75), where rule precedence and time-based evaluation logic are discussed.