Free Practice Questions for the Cisco CCNP Security 300-710 Exam (2026 Updated)

Name → HTTP-HTTPS-QoS

Apply QoS On → Interfaces in Destination Interface Objects

Download/Upload Limit → 5 Mb/s

Source Interface Networks → 192.168.1.0/24

Destination Interface Networks → 192.168.2.0/24

Destination Ports → HTTP-HTTPS

The HR workstation resides on the inside 192.168.1.0/24 network, making that subnet the source-interface network. Internet-bound traffic exits through the 192.168.2.0/24 network, which must be configured as the destination-interface network. Because rate limiting must occur as traffic leaves toward the internet, QoS is applied to interfaces in the destination interface objects. The HTTP-HTTPS object identifies the destination ports for web traffic, while HTTP-HTTPS-QoS provides a descriptive rule name. Both download and upload limits are configured as 5 Mb/s. Cisco Secure Firewall applies a QoS limit independently on each selected interface and determines upload and download direction based on the connection initiator. The Apply QoS On selection must correspond to a populated source or destination interface condition. Cisco Secure Firewall QoS configuration

https://www.cisco.com/c/en/us/td/docs/security/firepower/640/configuration/guide/fpmc-config-guide-v64/transparent_or_routed_firewall_mode_for_firepower_threat_defense.html

Peer poll time controls how frequently one high-availability unit sends hello or polling messages to determine whether its peer remains responsive. Peer hold time specifies how long the appliance waits without receiving the expected peer communication before declaring that peer unavailable. Decreasing both values causes the appliances to test peer availability more frequently and wait less time before initiating failover. Interface-oriented timers are used to evaluate monitored data-interface failures and do not specifically accelerate detection of a failed failover link. Although shorter peer timers improve failover speed, excessively aggressive values can cause false failovers during congestion or high CPU utilization. Cisco explains that threat defense appliances monitor peer health through hello messages on the failover link and begin additional testing after consecutive messages are missed. Cisco Secure Firewall high-availability monitoring

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

To add a Cisco Secure Firewall Threat Defense (FTD) device to Cisco Secure Firewall Management Center (FMC), the correct command to use isconfigure manager add 192.168.75.201 < reg_key > . This command registers the FTD device with the FMC using the FMC ' s IP address and the registration key provided during the FMC setup.

Command structure:

configure manager add < FMC_IP > < reg_key >

For the given scenario:

FMC IP address: 192.168.75.201

Registration key: provided during FMC setup

Thus, the correct command is:

configure manager add 192.168.75.201 < reg_key >

The content keyword is used to specify a string or pattern to search for in the payload or stream of a packet. The string must be enclosed in quotation marks and can use modifiers such as nocase, depth, offset, and so on. The string can also use hexadecimal notation by using a pipe symbol (|) before and after the hexadecimal characters. For example, content: " |45 5* 26 27 4 0A| " will match any payload or stream that contains the hexadecimal bytes 45 5 26 27 4 0A followed by any number of bytes2

After setting the interface mode to inline and enabling the interfaces on a Cisco Secure Firewall Threat Defense (FTD) device in an inline IPS deployment, the next step is to configure an inline set. An inline set groups two interfaces that work together to inspect traffic passing between them.

Steps to configure an inline set:

In FMC, navigate toDevices > Device Management.

Select the FTD device and configure the interfaces.

Create a new inline set, adding the relevant interfaces that have been set to inline mode.

Deploy the configuration to the FTD device.

Configuring an inline set ensures that the traffic between the specified interfaces is inspected and processed according to the IPS policies, completing the implementation of the inline IPS deployment.

Reference”https://www.cisco.com/c/en/us/td/docs/security/firepower/620/configuration/guide/fpmc-config-guide-v62/working_with_intrusion_events.html

When an FTD device that is managed by FDM is registered to FMC, the existing configuration is automatically converted and imported into FMC. The FMC then pushes the configuration back to the device. This process preserves most of the FDM configuration, except for some features that are not supported by FMC, such as VPN wizards and certificates.

The correct sequence of actions for configuring a multi-instance environment for high availability on a Cisco Firepower 4100 appliance is as follows:

Add a resource profile for container instances. A resource profile defines the CPU, RAM, and disk space allocation for each container instance.You can create multiple resource profiles with different resource settings and assign them to different container instances1.

Add a MAC pool prefix and view the MAC address for the container instance interfaces. A MAC pool prefix is a 24-bit prefix that is used to generate MAC addresses for the container instance interfaces. You can specify a custom MAC pool prefix or use the default one.You can also view the MAC addresses that are assigned to each container instance interface1.

Configure interfaces. You need to configure the physical interfaces, EtherChannels, and VLAN subinterfaces that will be used by the container instances.You can also configure shared interfaces that can be used by multiple container instances on the same security module/engine1.

Add a Standalone Firepower Threat Defense for Cisco Secure Firewall Management Center. You need to add a logical device that runs a standalone Firepower ThreatDefense (FTD) application instance and register it with the Cisco Secure Firewall Management Center (FMC).This logical device will act as the management interface for the container instances1.

Add a high-availability pair. You need to add another logical device that runs a standalone FTD application instance and register it with the FMC as well. Then, you need to configure high availability (HA) between the two standalone FTD logical devices.This will enable HA for the container instances that are associated with them1.

To support more than two interfaces per context and enable NAT configurations, the firewall must operate in routed mode. Since the firewall was previously in transparent mode, the network engineer needs to change it to routed mode.

Steps:

Access the CLI of the Secure FTD device.

Run the commandconfigure firewall routedto switch the firewall from transparent mode to routed mode.

Reregister the FTD device with the FMC by running theconfigure manager add < FMC_IP > < Registration_Key > command from the FTD device CLI.

This will ensure that the firewall can support the required NAT configurations and more than two interfaces per context.

https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/firewall/asa-910-firewall-config/access-sfr.html

Inline tap monitor-only mode (ASA inline)—In an inline tap monitor-only deployment, a copy of the traffic is sent to the ASA FirePOWER module, but it is not returned to the ASA. Inline tap mode lets you see what the ASA FirePOWER module would have done to traffic, and lets you evaluate the content of the traffic, without impacting the network. However, in this mode, the ASA does apply its policies to the traffic, so traffic can be dropped due to access rules, TCP normalization, and so forth.

A passive interface is specifically designed to monitor copied network traffic received from a switch SPAN or mirror port. Because the Secure Firewall Threat Defense device is not physically placed in the traffic path, it receives a copy of the packets for inspection but does not retransmit them. This provides network and intrusion visibility without affecting production traffic. The trade-off is that a passive deployment cannot directly block, shape, or modify the monitored traffic because the original packets continue through the switch independently. An inline deployment, by comparison, places paired interfaces directly in the forwarding path and can drop malicious traffic. Routed and transparent describe firewall forwarding modes and are not the appropriate SPAN-based IPS interface type. Therefore, a SPAN-port monitoring deployment requires a passive interface. Cisco passive-interface documentation

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

Cisco Secure Cloud Analytics ingests network flows and traffic telemetry, such as NetFlow and cloud flow logs, and applies behavioral modeling to that information. It establishes a baseline of normal activity for entities such as hosts, users, and workloads. New activity is compared with the baseline to identify anomalies, suspicious communication patterns, lateral movement, command-and-control traffic, and potential data exfiltration. The platform does not merely forward or archive the collected information. Although its analytics may incorporate statistical methods and machine learning, Cisco specifically describes the solution as using entity and behavioral modeling. This allows it to detect threats based on how an entity acts over time, including previously unknown threats that would not necessarily match a conventional signature. Cisco Secure Cloud Analytics

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

https://www.cisco.com/c/en/us/td/docs/security/firepower/620/configuration/guide/fpmc-config-guide-v62/firepower_management_center_high_availability.html

Cisco Secure Firewall Threat Defense supports IPsec encryption between the failover links of a high-availability pair. During HA configuration, the engineer enables encryption and selects the appropriate Key Generation method for IPsec. This protects failover and stateful synchronization data exchanged between the active and standby units. An SSL remote-access VPN is designed for user-to-network connectivity and is not used to protect an internal HA link. SSL is also not the documented encryption mechanism for Threat Defense failover synchronization. Clearing a commit queue does not encrypt or otherwise protect synchronized state information. Cisco’s HA configuration procedure explicitly instructs administrators to enable the encryption option and choose the Key Generation method for IPsec encryption between the failover links. Therefore, option B directly implements the required synchronization-protection mechanism. Cisco Secure Firewall high-availability configuration

Transparent firewall mode forwards traffic at Layer 2, so the participating physical interfaces must be assigned to at least one bridge group. This allows the device to inspect traffic while remaining logically transparent to the connected switch stacks. Bridge Protocol Data Units should also be exempted from advanced inspection. BPDUs are essential for spanning-tree operation, and delaying or blocking them during inspection restarts can produce topology instability or an interruption. A BVI provides Layer 3 addressing for device-originated traffic or management but is not inherently required merely to inspect transit traffic. Jumbo-frame configuration is unnecessary unless the network explicitly uses jumbo frames, and separate data and management routes do not establish transparent forwarding. Cisco specifically recommends using an EtherType ACL to trust BPDUs on each bridge-group member interface. Cisco transparent firewall configuration

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

SNMP provides nonintrusive, read-only monitoring of Secure Firewall Threat Defense devices and is appropriate for collecting high-level device statistics without interrupting production traffic. An external network management system can poll supported Management Information Base objects to obtain CPU utilization, memory usage, interface statistics, Snort information, process status, high-availability state, and cluster health. SNMP traps can also report important events without requiring continuous manual access to the device. Malware reports focus on malicious files and malware events, while risk reports summarize security risks and attacks. Host reports describe discovered hosts, applications, operating systems, and vulnerabilities rather than overall device performance. Because the requirement concerns device-level statistics and minimizing operational disruption during peak season, SNMP monitoring is the most appropriate choice. Cisco Secure Firewall SNMP monitoring

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

Integrated Routing and Bridging allows a Secure Firewall device operating in routed mode to contain bridge groups while also supporting routed interfaces. Multiple physical or logical interfaces can become members of one bridge group, placing them in the same Layer 2 broadcast domain, VLAN, and IP subnet. A Bridge Virtual Interface represents that bridge group at Layer 3 and functions as its gateway, permitting communication between the bridged network and routed interfaces or other bridge groups, subject to security policy. This can remove the need for an additional external Layer 2 switch when suitable firewall interfaces are available. IRB does not itself provide high availability, security-context separation, or Cisco Talos threat-intelligence updates. Those capabilities are implemented through separate features. Therefore, allowing multiple interfaces to participate in the same VLAN is the stated IRB benefit. Cisco IRB documentation

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

Cisco warns that displaying captured packets directly on the screen can degrade system and network performance. The -w test option writes raw packets to a file instead of continuously parsing and displaying them on the terminal. The -s 1518 option sets the snapshot length to the default Ethernet maximum frame size so complete packets are captured, while -c 1000 automatically stops the capture after 1,000 packets. The BPF expression host 10.10.10.10 further reduces resource consumption by capturing only traffic involving the specified host. Options A, B, and C limit the captured traffic to varying degrees, but they omit -w and therefore continue sending decoded packet output to the screen. Consequently, Option D is the complete performance-conscious capture command. Cisco packet-capture procedure

When reconfiguring an existing Cisco FTD from transparent mode to routed mode, an additional action that must be taken to maintain communication between the two network segments is toupdate the IP addressing so that each segment is a unique IP subnet. This is because in routed mode, the FTD device acts as a router hop in the network and requires each interface to be on a different subnet. In transparent mode, the FTD device acts as a layer 2 firewall and does not require different subnets for each interface1.

The other options are incorrect because:

Configuring a NAT rule so that traffic between the segments is exempt from NAT is not necessary to maintain communication between the two network segments. NAT is used to translate IP addresses between different networks, but it does not affect the routing of packets. Moreover, NAT is optional in routed mode and can be disabled if not needed2.

Deploying inbound ACLs on each interface to allow traffic between the segments is not required to maintain communication between the two network segments. ACLs are used to control access to network resources based on source and destination addresses, protocols, and ports. They do not affect the routing of packets. Furthermore, ACLs are optional in routed mode and can be configured as needed3.

Assigning a unique VLAN ID for the interface in each segment is not relevant to maintain communication between the two network segments. VLANs are used to create logical groups of hosts that share the same broadcast domain, regardless of their physical location or connection. They do not affect the routing of packets. Besides, VLANs are not supported in routed mode and can only be used in transparent mode4.

The Threat Defense device cannot change its firewall mode while it has an active manager configuration. After unregistering the device from Management Center, the engineer must execute configure manager delete to remove the manager association and place the device in No Manager Mode. The engineer can then execute configure firewall transparent to change the operating mode. Changing firewall modes clears the device configuration because routed-mode and transparent-mode interface configurations are incompatible. After completing the conversion, the engineer must configure the Management Center association again with configure manager add and register the device. Options A and B are not valid Threat Defense CLI commands. Option D performs the actual mode conversion, but it is not the first required CLI command while the manager association remains configured. Cisco Threat Defense command reference

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

To deploy a Cisco FTD device that meets the requirements of the question, the engineer must use transparent mode with a management interface. Transparent mode is a firewall configuration in which the FTD device acts as a “bump in the wire” or a “stealth firewall” and is not seen as a router hop to connected devices. In transparent mode, the FTD device can examine traffic without requiring network changes that will disrupt end users, such as changing IP addresses or routingconfigurations1. A management interface is a dedicated interface that is used for managing the FTD device and separating management traffic from data traffic. A management interface can be configured to allow SSH access for remote administration, which is more secure than Telnet2.

The other options are incorrect because:

Routed mode is a firewall configuration in which the FTD device acts as a router and performs address translation and routing for connected networks. Routed mode requires network changes that may disrupt end users, such as changing IP addresses or routing configurations1. A diagnostic interface is a special interface that is used for troubleshooting and capturing traffic on the FTD device. A diagnostic interface does not separate management traffic from data traffic or allow SSH access for remote administration.

Transparent mode with a data interface does not meet the requirement of separating management traffic from data traffic. A data interface is a regular interface that is used for passing and inspecting traffic on the FTD device. A data interface does not allow SSH access for remote administration2.

Routed mode with a bridge virtual interface (BVI) does not meet the requirement of examining traffic without requiring network changes that will disrupt end users. A BVI is a logical interface that acts as a container for one or more physical or logical interfaces that belong to the same layer 2 broadcast domain. A BVI allows the FTD device to route between different bridge groups on the same security module/engine. However, routed mode still requires network changes that may disrupt end users, such as changing IP addresses or routing configurations.

To enable Cisco Secure Firewall Malware Defense to detect and block malware, the network administrator must associate a File policy with an access control policy. File policies allow administrators to configure malware detection and file analysis capabilities on the Cisco Secure Firewall Threat Defense appliance.

Steps to configure File policy:

Navigate toPolicies > Access Control > File Policiesin the FMC.

Create a new file policy or edit an existing one to include malware detection and blocking settings.

Associate the file policy with the relevant access control policy.

Ensure that the access control policy is deployed to the FTD appliance.

By associating a file policy, the firewall will inspect files being transmitted through the web server for malware and take appropriate actions (block, allow, or alert) based on the configured rules.

" In routed firewall mode, broadcast and multicast traffic is blocked even if you allow it in an access rule... " " The bridge group does not pass CDP packets packets... " https://www.cisco.com/c/en/us/td/docs/security/asa/asa913/configuration/general/asa-913-general-config/intro-fw.html

Passing Traffic Not Allowed in Routed Mode

In routed mode, some types of traffic cannot pass through the ASA even if you allow it in an access rule. The bridge group, however, can allow almost any traffic through using either an access rule (for IP traffic) or an EtherType rule (for non-IP traffic):

IP traffic—In routed firewall mode, broadcast and " multicast traffic is blocked even if you allow it in an access rule, " including unsupported dynamic routing protocols and DHCP (unless you configure DHCP relay). Within a bridge group, you can allow this traffic with an access rule (using an extended ACL).

Non-IP traffic—AppleTalk, IPX, BPDUs, and MPLS, for example, can be configured to go through using an EtherType rule.

Note

" The bridge group does not pass CDP packets packets, or any packets that do not have a valid EtherType greater than or equal to 0x600. An exception is made for BPDUs and IS-IS, which are supported. "

To connect to a Secure Endpoint private cloud instance from Cisco Secure Firewall Management Center (FMC), the network engineer requires the SSL certificate for the Secure Endpoint private cloud instance. This SSL certificate is necessary to establish a secure, trusted connection between the FMC and the private cloud instance.

Steps:

Obtain the SSL certificate from the server administrator.

Import the SSL certificate into the FMC.

Configure the connection to the Secure Endpoint private cloud instance using the provided hostname and SSL certificate.

This ensures a secure and authenticated connection to the private cloud instance.

Step 1(Configure the primary unit for high availability),

Step 2(Configure the secondary unit for high availability),

Step 3(Configure the two units for high availability),

Step 4(Configure failover criteria for health monitoring)

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

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

To streamline the process of reviewing events and modifying blocking of specific files across both the firewall console and the endpoint console, the security engineer should initiate the integration between Secure FMC and Cisco Secure Endpoint (formerly AMP for Endpoints) from the Secure FMC using the AMP tab.

Steps:

In the FMC, navigate toDevices > Device Management.

Select the device and go to theAMPtab.

Initiate the integration by configuring the necessary API credentials and linking the FMC to the Cisco Secure Endpoint console.

This integration allows the security engineer to view endpoint events and apply blocking actions directly from the FMC, consolidating the management tasks.

This approach simplifies the workflow by providing a single interface to manage both network and endpoint security, reducing the time and effort required to maintain security across the organization.

Transparent mode is a firewall configuration in which the firewall acts as a “bump in the wire” or a “stealth firewall” and is not seen as a router hop to connected devices. In transparent mode, the firewall can forward traffic at both layer 2 and layer 3 for the same subnet, as it does not perform any address translation or routing. The firewall inspects the traffic and applies security policies based on the source and destination IP addresses, ports, and protocols. Transparent mode is useful when you want to deploy a firewall without changing the existing network topology or addressing scheme1.

In a failover configuration with Cisco Secure Firewall Threat Defense (FTD) devices, ensuring that users on the internal network can continue to communicate with outside devices if the primary device (FTD1) fails requires the implementation of a stateful failover link. The stateful failover link allows the secondary device (FTD2) to maintain session information and state data, ensuring seamless failover and minimizing disruptions.

Steps to implement a stateful failover link:

Physically connect a stateful failover link between FTD1 and FTD2.

Configure the stateful failover link in the FMC.

Ensure that both devices are properly synchronized and that stateful failover is enabled.

Deploy the changes to both FTD devices.

By configuring a stateful link, the secondary FTD can take over active sessions without requiring users to re-establish their connections, thus ensuring continuous communication.

The show bgp neighbors NEIGHBOR-IP advertised-routes command displays the prefixes that the Secure Firewall Threat Defense device is advertising to a specific BGP neighbor. It must be executed against the managed threat defense device through the Advanced Troubleshooting interface. The ordinary show route command displays routes installed in the local routing table, not the specific prefixes advertised to a neighbor. Route injection is a configuration capability and does not provide the required verification output. Cisco’s command reference confirms that the advertised-routes keyword displays all routes advertised to the specified BGP peer, including the network, next hop, metric, weight, and AS path. Therefore, option A directly verifies the routes being shared with the upstream router. Cisco Secure Firewall Threat Defense Command Reference

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

Secure Firewall access control evaluates a connection using the destination’s real, untranslated address. For an inbound static NAT connection, the Internet client sends traffic to the mapped public address, but the firewall performs NAT untranslation and evaluates the access control rule against the internal server address. Consequently, a rule containing only the public address will not match as intended. The administrator must replace that public destination with the web server’s internal IP address while retaining the required TCP port and appropriate Allow action. Changing the action to Trust does not correct an address-matching error and would also bypass additional inspection. Disabling intrusion inspection is unrelated, and translating the client’s source address is unnecessary for ordinary inbound static NAT. Therefore, the access control rule must reference the internal, real server address. Cisco NAT and real-address documentation

https://www.cisco.com/c/en/us/td/docs/security/firepower/620/configuration/guide/fpmc-config-guide-v62/reusable_objects.html#ID-2243-000009b4

" All interfaces in an interface object must be of the same type: all inline, passive, switched, routed, or ASA FirePOWER. After you create an interface object, you cannot change the type of interfaces it contains. "

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

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

Interface → outside

Source Host → any

Packet 1 source → 209.165.201.2

Packet 2 source → 209.165.201.1

Packet 4 ICMP message → echo reply

Unused Options:

209.165.202.1

209.165.202.2

The capture must run on the FTDv outside interface, where the client’s translated address is 209.165.201.2. Selecting any as the source-host criterion captures both the outbound echo requests and the inbound ICMP responses. The first request therefore appears as 209.165.201.2 to 209.165.202.2. When the initial traceroute probe expires at R1, the router generates an ICMP time-exceeded response using its interface address 209.165.201.1. A later probe reaches Server1, which returns an ICMP echo reply from 209.165.202.2 to 209.165.201.2. The completed-answer exhibit in List B places several IP addresses inconsistently; the mapping above follows the displayed topology and actual ICMP traceroute packet flow. Cisco FTD capture and Packet Tracer guidance

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