Free Cisco 300-710 Practice Exam with Questions & Answers | Set: 10

The “Risky Applications with Low Business Relevance” widget identifies BitTorrent as the most significant application risk, with 342 connections—substantially more than the other applications displayed. BitTorrent is a peer-to-peer application that can introduce malware, facilitate unauthorized file transfers, consume bandwidth, and bypass normal content-distribution controls. The engineer should configure an access control rule or application filter that blocks all BitTorrent applications. Google Play appears only as a frequently used web application and is not identified by the dashboard as the primary risky application. Disabling a user account would not address BitTorrent usage by other users, while patching Chrome concerns endpoint vulnerability management rather than application usage risk. Cisco application-control rules can block applications according to risk and business relevance. Cisco application-control documentation

When connectivity issues are detected between Cisco Secure Firewall Management Center (FMC) and Cisco Secure Firewall Threat Defense (FTD) devices, and initial troubleshooting indicates that heartbeats and events are not being received, the engineer can run the following commands to resolve the issue by re-establishing secure channels and checking process statuses:

manage_procs.pl:This script is used to manage and restart processes on the FTD device. Running this script can help restart any malfunctioning processes and re-establish connectivity between the FMC and FTD.

sudo stats_unified.pl:This command provides detailed statistics and status of the unified system processes. It helps in diagnosing and resolving issues related to the secure channel and event reporting.

Steps:

Access the FTD CLI.

Run the commandmanage_procs.plto restart processes.

Run the commandsudo stats_unified.plto gather detailed process statistics and verify the status.

These commands help resolve connectivity issues by ensuring that all necessary processes are running correctly and secure channels are re-established.

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

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

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

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

4, 1, 2, 3