Topic 1: Deployment
An administrator is optimizing the Cisco FTD rules to improve network performance, and wants to bypass inspection for certain traffic types to reduce the load on the Cisco FTD. Which policy must be configured to accomplish this goal?
A. prefilter
B. intrusion
C. identity
D. URL filtering
Explanation
In Cisco FMC, the Prefilter Policy runs before the Access Control Policy and is specifically designed for early handling of traffic. You can create fastpath rules within the prefilter policy that cause matching traffic to bypass Snort deep inspection entirely. This reduces the load on the FTD by excluding trusted or performance-sensitive traffic from further inspection.
Cisco documentation confirms that prefiltering improves performance by handling traffic early, either by blocking it or fastpathing it. A fastpath prefilter rule exempts matching traffic from further Snort inspection.
Why the Other Options Are Incorrect
B. Intrusion: The intrusion policy is a sub-policy within an access control rule that defines which IPS signatures are used to inspect traffic. It does not provide the prefilter fastpath mechanism for bypassing Snort inspection.
C. Identity: The identity policy is used for user authentication and identity-based access control, not for bypassing inspection to improve performance.
D. URL filtering: URL filtering is a condition within access control rules that categorizes web traffic. It does not provide a mechanism to bypass deep inspection through prefilter fastpath rules.
Reference
Cisco Firepower Management Center Configuration Guide: Prefilter rules with the Fastpath action bypass further inspection. The prefilter policy is evaluated before access control rules and can improve performance by fastpathing trusted traffic.
On the advanced tab under inline set properties, which allows interfaces to emulate a passive interface?
A. transparent inline mode
B. TAP mode
C. strict TCP enforcement
D. propagate link state
Explanation
In the advanced settings of a Cisco FTD inline set, Tap Mode is the option that allows the inline interfaces to emulate the behavior of a passive interface. When Tap Mode is enabled, the physical interfaces remain cabled inline, in the traffic path, but the actual network traffic is bridged and forwarded without modification. A copy of each packet is sent to the Snort engine for analysis, meaning the device behaves like a passive monitoring interface: it can generate alerts but cannot drop the live traffic.
Cisco's official configuration guide confirms that under the Advanced settings of an inline set, the Tap Mode option is available and sets the inline set to inline tap mode. The comparison table further clarifies that with Tap Mode enabled, a copy of the packet is inspected and dropped internally while the actual traffic passes through FTD unmodified. This is the passive-like behavior described in the question.
Why the Other Options Are Incorrect
A. Transparent inline mode: This is not a valid option in the inline set's advanced settings. Transparent mode is a firewall deployment mode, not an inline set property.
C. Strict TCP enforcement: This is an inline set option that enforces strict TCP state tracking, but it cannot be enabled simultaneously with Tap Mode. It does not emulate passive behavior.
D. Propagate link state: This option propagates the link state of the inline interfaces to connected devices. It is unrelated to passive interface emulation.
Reference
Cisco Secure Firewall Management Center Device Configuration Guide — Configure an Inline Set. Under the Advanced settings, Tap Mode sets the inline set to inline tap mode. Cisco documentation confirms that Tap Mode sends a copy of packets for inspection while the original traffic passes through unmodified.
A Cisco FTD has two physical interfaces assigned to a BVI. Each interface is connected to a different VLAN on the same switch. Which firewall mode is the Cisco FTD set up to support?
A. active/active failover
B. transparent
C. routed
D. high availability clustering
Explanation
When two physical interfaces of a Cisco FTD are assigned to the same Bridge Virtual Interface (BVI), and each interface connects to a different VLAN on the same switch, this is a typical transparent firewall mode deployment. In transparent mode, data interfaces must belong to a bridge group, and the device forwards traffic within the bridge group by looking up the destination MAC address rather than performing route lookups. The BVI is used as the source address for management and device-originated traffic. Its IP address must be in the same subnet as the connected network, and it cannot be used as the default gateway for downstream devices.
Why the Other Options Are Incorrect
A. Active/active failover: FTD high availability supports active/standby mode, not active/active failover. This option is unrelated to interface bridging.
C. Routed: In routed mode, interfaces are configured with IP addresses and traffic is forwarded through route lookups. Although bridge groups can also exist in routed mode, the scenario described is commonly associated with transparent mode because it focuses on Layer 2 bridging between interfaces rather than Layer 3 routing decisions.
D. High availability clustering: Clustering is a scalability technology that allows multiple devices to work together. It is unrelated to the interface bridging mode described in the question.
Reference
Cisco Firepower Management Center Configuration Guide: In transparent mode, at least one bridge group is required, and data interfaces must belong to a bridge group. Traffic within a bridge group is forwarded based on destination MAC address lookups.
Which Firepower feature allows users to configure bridges in routed mode and enables devices to perform Layer 2 switching between interfaces?
A. FlexConfig
B. BDI
C. SGT
D. IRB
Explanation
Integrated Routing and Bridging (IRB) is the Firepower feature that allows you to configure bridge groups within routed mode and perform Layer 2 switching between member interfaces. According to Cisco documentation, bridge groups are supported in both transparent and routed firewall modes. When a Bridge Virtual Interface (BVI) is configured in routed mode, the BVI participates in routing like any other regular interface, while the member interfaces of the bridge group continue to switch traffic at Layer 2 based on destination MAC address lookups. This provides the capability described in the question: configuring bridge groups in routed mode while enabling Layer 2 switching between interfaces.
Why the Other Options Are Incorrect
A. FlexConfig: FlexConfig is a feature used to push CLI commands to FTD for settings that are not natively exposed in FMC. It is not a bridging or switching feature.
B. BDI: Bridge Domain Interface (BDI) is a term used in Cisco IOS XE router configurations. It is not the native FTD feature used to configure bridge groups in routed mode.
C. SGT: Security Group Tag (SGT) is associated with Cisco TrustSec identity-based segmentation. It is unrelated to Layer 2 bridging.
Reference
Cisco Firepower Management Center Configuration Guide: Bridge groups are supported in both transparent and routed firewall modes. When a BVI is named, it participates in routing like any other regular interface.
Which action should be taken after editing an object that is used inside an access control policy?
A. Delete the existing object in use
B. Refresh the Cisco FMC GUI for the access control policy.
C. Redeploy the updated configuration
D. Create another rule using a different object name.
Explanation
In Cisco FMC, after editing an object referenced by an active access control policy, simply saving the object does not push the changes to the managed devices. The modified configuration must be redeployed for the changes to take effect on the FTD devices. Cisco's official documentation explicitly states that if an active policy references the edited object, configuration changes must be deployed. When editing an object group used in an access control policy, you must redeploy the changed configuration for the changes to take effect.
Why the Other Options Are Incorrect
A. Delete the existing object in use: This is incorrect and may cause deployment failures. Cisco documentation notes that you cannot delete a group that is in use in an active policy. Removing objects that are still referenced can also create configuration inconsistencies.
B. Refresh the Cisco FMC GUI for the access control policy: Refreshing the GUI only updates the displayed information. It does not push configuration changes to the managed devices.
D. Create another rule using a different object name: This is unnecessary and does not address the requirement. The correct workflow is to edit the existing object and redeploy the configuration, rather than create duplicate rules.
Reference
Cisco Secure Firewall Management Center Device Configuration Guide — Object Management: If an active policy references an object, deploy the configuration changes. When editing an object group used in a policy, redeploy the configuration for the changes to take effect.
Which command is entered in the Cisco FMC CLI to generate a troubleshooting file?
A. show running-config
B. show tech-support chassis
C. system support diagnostic-cli
D. sudo sf_troubleshoot.pl
Explanation
On the FMC, the sf_troubleshoot.pl script is the command-line tool used to generate a troubleshooting file. It collects system logs, configuration data, and diagnostic output into a compressed archive, typically saved under /var/common/, that can be sent to Cisco TAC. It is run from the FMC's Linux shell with root privileges, hence the use of sudo. Similar troubleshooting files can also be generated through the GUI under System > Health > Monitor > Advanced Troubleshooting.
Why the Other Options Are Incorrect
A. show running-config: This command displays the device's active configuration. It does not generate a troubleshooting archive and is not the FMC Linux shell command used for this purpose.
B. show tech-support chassis: This is an FXOS command for Firepower 4100/9300 chassis. It is run on the chassis supervisor, not on the FMC.
C. system support diagnostic-cli: This is an FTD CLI command that opens the diagnostic CLI on a threat defense device. It does not run on the FMC to generate a troubleshooting file.
Reference
- Cisco Secure Firewall Management Center Administration Guide: Troubleshooting and Advanced Troubleshooting (Generate Troubleshooting Files)
- Cisco TAC documentation: Generate Troubleshooting Files on Firepower Devices
An organization is using a Cisco FTD and Cisco ISE to perform identity-based access controls. A network administrator is analyzing the Cisco FTD events and notices that unknown user traffic is being allowed through the firewall. How should this be addressed to block the traffic while allowing legitimate user traffic?
A. Modify the Cisco ISE authorization policy to deny this access to the user.
B. Modify Cisco ISE to send only legitimate usernames to the Cisco FTD.
C. Add the unknown user in the Access Control Policy in Cisco FTD.
D. Add the unknown user in the Malware & File Policy in Cisco FTD.
Explanation
Cisco FTD's identity policy itself does not block traffic; it is responsible for collecting user identity information. Cisco documentation explains that authentication failure does not automatically prevent network access. Identity policies collect user identity information only, and access control rules must be used to prevent users who fail authentication from accessing the network. Therefore, the root cause of unknown-user traffic being allowed lies in the access control policy's matching logic, rather than the identity policy alone.
Since authentication is performed through Cisco ISE, adding a deny rule in the ISE authorization policy for users whose authentication result is "Unknown User" or who fail authentication can help prevent unauthorized network access at the network access layer. However, to block traffic through FTD, the access control policy must also contain an appropriate rule that denies traffic from unknown users. Option A is intended to address access enforcement through ISE, but the FTD access control policy must be configured correctly to ensure the desired result.
Why the Other Options Are Incorrect
B. Modify Cisco ISE to send only legitimate usernames to the Cisco FTD: ISE can provide user-IP mappings based on observed network activity. Selectively withholding mappings for unknown users would leave FTD unable to identify those users, but it would not automatically prevent their traffic from passing. Blocking decisions must be enforced through the appropriate access control mechanism.
C. Add the unknown user in the Access Control Policy in Cisco FTD: FTD access control rules can match the Unknown user condition and deny the associated traffic. This is a direct FTD-side enforcement method and may be appropriate when the requirement is specifically to block unknown users at FTD. The rule must be correctly configured and ordered so that it is evaluated before any broader rule that permits the traffic.
D. Add the unknown user in the Malware & File Policy in Cisco FTD: Malware and file policies are used for file inspection and advanced malware protection. They do not provide the required identity-based network access control.
Reference
Cisco Secure Firewall Management Center Device Configuration Guide: Identity policies collect user identity information only. To prevent users who fail authentication from accessing the network, configure appropriate access control rules. Cisco ISE authorization policies can also enforce network access decisions based on authentication results.
After deploying a network-monitoring tool to manage and monitor networking devices in your organization, you realize that you need to manually upload an MIB for the Cisco FMC. In which folder should you upload the MIB file?
A. /etc/sf/DCMIB.ALERT
B. /sf/etc/DCEALERT.MIB
C. /etc/sf/DCEALERT.MIB
D. system/etc/DCEALERT.MIB
Explanation
Cisco's official documentation states that if your network management system requires the Management Information Base (MIB) file for the Secure Firewall Management Center (FMC), you can obtain it from the FMC at the path /etc/sf/DCEALERT.MIB. This file contains definitions for SNMP traps and alerts sent by the FMC. It allows network monitoring tools to properly interpret and process the alerts generated by the FMC.
Why the Other Options Are Incorrect
A. /etc/sf/DCMIB.ALERT: The filename does not match the official documentation. Cisco specifies DCEALERT.MIB, not DCMIB.ALERT.
B. /sf/etc/DCEALERT.MIB: The directory order is incorrect. The documented path starts with /etc/sf/, not /sf/etc/.
D. system/etc/DCEALERT.MIB: This path does not match the documented location. The correct path is /etc/sf/DCEALERT.MIB.
Reference
Cisco Secure Firewall Management Center documentation — Intrusion SNMP Alert Options: If a network management system requires an MIB file, it can be obtained from the Secure Firewall Management Center at /etc/sf/DCEALERT.MIB. This location is also referenced in the Create an SNMP Alert Response documentation.
Which command-line mode is supported from the Cisco Firepower Management Center CLI?
A. privileged
B. user
C. configuration
D. admin
Explanation
The Cisco Firepower Management Center (FMC) CLI officially defines four modes: the default CLI Management mode, plus system, show, and configure modes. Among the options, configuration corresponds to the configure mode, which provides supported commands for configuring and managing system operations, such as changing passwords and generating troubleshooting files.
Why the Other Options Are Incorrect
A. Privileged: Privileged EXEC is a command mode associated with the Cisco Firepower Threat Defense (FTD) diagnostic CLI, not the FMC CLI.
B. User: User EXEC is also associated with the FTD diagnostic CLI and is not an FMC CLI mode.
D. Admin: Admin is a username, commonly used for the default administrator account, not a command-line mode. After logging into FMC, the prompt may display admin@FMC:, but the mode itself is not named admin.
Reference
Cisco Firepower Management Center Administration Guide — Firepower Management Center CLI Modes: The CLI includes four modes, with commands in the system, show, and configure modes beginning with the corresponding mode name.
A company is in the process of deploying intrusion prevention with Cisco FTDs managed by a Cisco FMC. An engineer must configure policies to detect potential intrusions but not block the suspicious traffic. Which action accomplishes this task?
A. Configure IDS mode when creating or editing a policy rule under the Cisco FMC Intrusion tab in Access Policies section by unchecking the "Drop when inline" option.
B. Configure IDS mode when creating or editing a policy rule under the Cisco FMC Intrusion tab in Access Policies section by unchecking the "Drop when inline" option.
C. Configure IPS mode when creating or editing a policy rule under the Cisco FMC Intrusion tab in Access Policies section by unchecking the "Drop when inline" option.
D. Configure IDS mode when creating or editing a policy rule under the Cisco FMC Intrusion tab in Access Policies section by checking the "Drop when inline" option.
Explanation
In Cisco FMC, the official name of the intrusion policy is IPS, and FMC does not provide a separate IDS mode toggle. To configure the policy for detection without blocking traffic, uncheck the Drop when Inline option in the intrusion policy. Cisco's official documentation explains that checking Drop when Inline allows intrusion rules to affect traffic and generate events, while unchecking it prevents intrusion rules from affecting traffic but still generates events. Therefore, unchecking this option allows the policy to function like an IDS by detecting suspicious activity without blocking traffic through intrusion-rule actions.
Why the Other Options Are Incorrect
A. Configure IDS mode by checking the Drop when Inline option: Checking this option allows intrusion rules to affect traffic, enabling blocking behavior when applicable. This contradicts the requirement to detect suspicious traffic without blocking it.
B. Configure IPS mode by unchecking the Drop when Inline option: Unchecking this option does achieve the required non-blocking behavior. However, Cisco calls the policy an intrusion policy or IPS policy rather than providing a separate IDS mode. The key configuration change is to uncheck Drop when Inline.
C. Configure IPS mode by checking the Drop when Inline option: Checking this option allows intrusion rules to affect traffic, including dropping traffic when applicable. This contradicts the requirement for detection without blocking.
Reference
Cisco Firepower Management Center Configuration Guide: Check the Drop when Inline check box to allow intrusion rules to affect traffic and generate events. Uncheck Drop when Inline to prevent intrusion rules from affecting traffic while still generating events.
A network engineer is configuring URL Filtering on Firepower Threat Defense. Which two port requirements on the Firepower Management Center must be validated to allow communication with the cloud service? (Choose two.)
A. outbound port TCP/443
B. inbound port TCP/80
C. outbound port TCP/8080
D. inbound port TCP/443
E. outbound port TCP/80
Explanation
To allow the Firepower Management Center (FMC) to communicate with Cisco cloud services for URL Filtering, the FMC requires outbound access on both TCP/443 (HTTPS) and TCP/80 (HTTP). According to Cisco's official communication port documentation, the FMC uses these ports to retrieve URL category and reputation data and perform lookups for uncategorized URLs. Port 443 supports secure HTTPS communication, while port 80 is also listed as a requirement for retrieving URL category and reputation data.
Why the Other Options Are Incorrect
B. Inbound port TCP/80: The FMC initiates the connection to the cloud service. It does not need to accept inbound HTTP traffic for this function.
C. Outbound port TCP/8080: Port 8080 is not listed as a required port for FMC-to-cloud URL Filtering communication in the referenced Cisco documentation.
D. Inbound port TCP/443: Although the FMC may accept inbound HTTPS connections for management access, URL Filtering cloud communication is initiated outbound by the FMC. Therefore, inbound TCP/443 is not the requirement described in the question.
Reference
Cisco Firepower Management Center Configuration Guide — Security, Internet Access, and Communication Ports: The communication ports documentation lists TCP/443 and TCP/80 for the Management Center to obtain URL category and reputation data.
Which report template field format is available in Cisco FMC?
A. box lever chart
B. arrow chart
C. bar chart
D. benchmark chart
Explanation
According to Cisco's official Firepower Management Center (FMC) documentation, the available field format options for report templates include bar charts, line charts, pie charts, table views, and detail views. Among the options, Bar Chart is a supported chart format used to compare the number of records matching specific attributes.
Why the Other Options Are Incorrect
A. Box lever chart: This is not a chart type supported by FMC report templates. Cisco documentation does not list this format.
B. Arrow chart: This is not a supported format option in FMC report templates.
D. Benchmark chart: This is not a chart type listed for FMC reports in the official documentation.
Reference
Cisco Secure Firewall Management Center Administration Guide — Report Template Fields: The Format options include Bar Chart, Line Chart, Pie Chart, Table View, and Detail View.
| Page 3 out of 35 Pages |
| 1234567891011 |
| 300-710 Practice Test Home |
Real-World Scenario Mastery: Our 300-710 practice exam don't just test definitions. They present you with the same complex, scenario-based problems you'll encounter on the actual exam.
Strategic Weakness Identification: Each practice session reveals exactly where you stand. Discover which domains need more attention, before Securing Networks with Cisco Firepower (300-710 SNCF) exam day arrives.
Confidence Through Familiarity: There's no substitute for knowing what to expect. When you've worked through our comprehensive 300-710 practice exam questions pool covering all topics, the real exam feels like just another practice session.