Free Practice Questions for Cisco 300-710 Exam

To capture packets that are dropped by Cisco Secure Firewall Threat Defense (FTD) and troubleshoot the issue of traffic from the inside network to a webserver not getting through, the administrator should use the command to capture packets dropped by the accelerated security path (ASP) engine. The correct command is:

capture CAP type asp-drop all headers-only

This command captures all packets dropped by the ASP engine, which includes packets that are being blocked by access control policies, NAT issues, or other security checks.

Steps:

Access the FTD CLI.

Run the commandcapture CAP type asp-drop all headers-onlyto capture dropped packets.

Analyze the captured data to identify the cause of the drops.

This command provides detailed information on why packets are being dropped, helping the administrator resolve the issue.

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.

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

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