Cisco 300-710 - Securing Networks with Cisco Firewalls

An inline set consists of paired Secure Firewall Threat Defense interfaces placed directly in the network traffic path. The interfaces operate like a bump in the wire: one interface receives the traffic, the inspection engine evaluates it, and the paired interface retransmits it unless an access-control, intrusion, file, or other security policy explicitly drops it. This arrangement enables the IPS to prevent attacks because the device can stop malicious packets before forwarding them. A passive interface also receives traffic unconditionally, but it receives copied traffic from a SPAN or mirror port and retransmits none of it. Routed and transparent modes describe broader firewall packet-forwarding behavior rather than this IPS-only interface characteristic. Therefore, an inline deployment satisfies the requirement to inspect, retransmit, and selectively drop traffic. Cisco inline-set documentation

================

These fields belong to the Attacks Risk Report. Cisco defines Total Attacks as the number of IPS events and Hosts Targeted as the number of unique destination addresses associated with relevant IPS events. Events Requiring Attention represents the proportion of intrusion events with an impact flag indicating relevance. Hosts Connected to CnC Servers identifies unique hosts associated with the “CnC Connected” indication-of-compromise category. Together, these measurements summarize attack activity, affected assets, and potentially compromised systems. A Network Risk Report focuses on broader network-level risk and does not use this exact field collection. “Events Risk Report” and “Hosts Risk Report” are not the applicable standard risk-report templates. List B incorrectly marks Network Risk Report; Cisco’s report documentation explicitly assigns all four fields to the Attacks Risk Report, so the verified answer is B. Cisco risk-report templates

================

The Analysis > Hosts > Vulnerabilities page in Cisco FMC displays information about the hosts on the network and their associated vulnerabilities. The administrator can filter the hosts by impact level, which indicates how likely an attack is to succeed against a host. An impact level of 2 means that the host was attacked and is potentially vulnerable, but no exploit was confirmed. The administrator can click on a host to view more details, such as its IP address, operating system, applications, protocols, and intrusionevents. The administrator can also view the details of each vulnerability, such as its CVE ID, description, severity, and recommended actions3

The intended control node should be assigned a numerically lower priority value than the other cluster nodes. Cisco Secure Firewall cluster priority values operate inversely: the lowest numerical value represents the highest election priority. For example, a node configured with priority 1 takes precedence over nodes configured with priorities 10 or 20. If the current control node fails, the available node with the highest priority—meaning the lowest configured number—is elected as the replacement. Values 0 and 255 are outside the documented 1–100 range for this Management Center clustering implementation. Therefore, the node with greater processing resources should receive a lower numerical value. The supplied answer of C in List B is incorrect and has been corrected to B based on Cisco documentation. Cisco Secure Firewall clustering documentation

================

Change Reconciliation records snapshots whenever users save system-configuration changes and combines those snapshots into a detailed report covering the previous 24 hours. Under System > Configuration > Change Reconciliation, the administrator enables the feature, selects the daily execution time, and specifies management’s recipient email addresses. The administrator can also include policy-configuration changes and enable the full change history instead of receiving only a consolidated view. An email relay host must be configured so that Management Center can deliver the report. Sending audit logs to an HTTP or syslog server streams audit events to an external collector; it does not generate the required daily email summary. STIG Compliance applies security-hardening settings and is unrelated to scheduled change reporting. Cisco Change Reconciliation documentation