Topic 1: Deployment
With Cisco FTD software, which interface mode must be configured to passively receive
traffic that passes through the appliance?
A.
ERSPAN
B.
IPS-only
C.
firewall
D.
tap
firewall
Explanation
In Cisco FTD (Firepower Threat Defense) software, passive interfaces are used to monitor traffic without being in the direct flow. However, the interface mode that must be configured to passively receive traffic depends on the interface type.
For IPS-only interfaces, the mode is set to Passive (or ERSPAN). These interfaces receive traffic unconditionally and do not retransmit it, allowing the device to analyze a copy of the traffic without impacting the network flow. This is the standard method for passive monitoring in FTD.
Why the Other Options Are Incorrect
A. ERSPAN: ERSPAN is a specific type of passive interface that encapsulates traffic using GRE for monitoring across multiple switches. It is a sub-type of passive monitoring, not the general mode itself.
B. IPS-only: "IPS-only" refers to the deployment mode (bypassing firewall checks), not the specific interface mode used for passive reception. The interface mode within IPS-only is set to Passive.
D. tap: "Tap mode" is a feature applied to inline sets (not passive interfaces). It allows an inline deployment to copy packets for analysis without dropping traffic, but the interface itself is still configured as an inline set, not a passive interface.
Reference
- Cisco Documentation: "Firepower Management Center Configuration Guide" – Section on Passive Interfaces and PS-Only Mode, which states that passive interfaces receive all traffic unconditionally and do not retransmit it.
Which two routing options are valid with Cisco Firepower Threat Defense? (Choose two.)
A. BGPv6
B. ECMP with up to three equal cost paths across multiple interfaces
C. ECMP with up to three equal cost paths across a single interface
D. BGPv4 in transparent firewall mode
E. BGPv4 with nonstop forwarding
Explanation
Cisco Firepower Threat Defense (FTD) supports several dynamic routing protocols, including BGP, OSPF, EIGRP, and RIP. When considering the valid routing options among the choices provided:
A. BGPv6: FTD supports BGP for both IPv4 and IPv6 address families. You can configure BGP IPv6 neighbors and exchange IPv6 routes, which is a valid routing option on the platform.
C. ECMP with up to three equal cost paths across a single interface: FTD supports Equal-Cost Multi-Path (ECMP) routing. ECMP allows the device to load-balance traffic across multiple equal-cost paths. According to Cisco documentation, FTD supports ECMP and allows you to configure multiple equal-cost static or dynamic routes across interfaces within an ECMP zone. While the platform supports up to 8 interfaces in an ECMP zone, configuring multiple equal-cost paths (up to three) across a single interface is a valid configuration scenario for load balancing toward multiple next-hop gateways.
Why the Other Options Are Incorrect
B. ECMP with up to three equal cost paths across multiple interfaces: While FTD does support ECMP across multiple interfaces (up to 8 interfaces in an ECMP zone), the specific limit of "up to three" is incorrect. The platform supports up to 8 equal-cost paths, making this option inaccurate.
D. BGPv4 in transparent firewall mode: BGP is not supported in transparent firewall mode. Cisco documentation explicitly states that BGP is supported only in routed mode. Therefore, this is an invalid routing option for FTD.
E. BGPv4 with nonstop forwarding: While BGP supports graceful restart (which is a form of nonstop forwarding), the specific combination of "BGPv4 with nonstop forwarding" as a distinct routing option is not a standard supported feature in the context of this question. The platform supports BGP graceful restart, but the option as phrased is not a primary routing capability in the same way as BGPv6 or ECMP.
Reference
- Cisco Documentation: "BGP for Firepower Threat Defense" – Confirms BGP support for IPv4 and IPv6, and states BGP is not supported in transparent mode.

Refer to the exhibit An engineer is modifying an access control pokey to add a rule
to inspect all DNS traffic that passes through the firewall After making the change
and deploying the pokey they see that DNS traffic is not bang inspected by the Snort
engine What is the problem?
A. The rule must specify the security zone that originates the traffic
B. The rule must define the source network for inspection as well as the port
C. The action of the rule is set to trust instead of allow.
D. The rule is configured with the wrong setting for the source port
Explanation
The correct answer is C. The action of the rule is set to trust instead of allow.
Exhibit mein dekhein ke access control rule ka Action field "Trust" par set hai. Cisco Firepower (FMC/FTD) mein Trust action ka matlab hai ke traffic ko bypass kar diya jayega — yani koi bhi further inspection (Snort intrusion prevention, file inspection, DNS inspection, etc.) us traffic par apply nahi hogi. Trusted traffic ko firewall sirf allow karta hai lekin usse inspect nahi karta.
Agar engineer chahta hai ke DNS traffic ko Snort engine ke through inspect kiya jaye, to rule ka action "Allow" hona chahiye. Allow action ke saath hi associated intrusion policy, file policy, aur deep inspection apply hoti hai. Trust action use karne se traffic inspection bypass ho jati hai, isi liye DNS traffic inspect nahi ho raha.
Why the Other Options Are Incorrect
A. The rule must specify the security zone that originates the traffic. – Security zone specify karna zaroori ho sakta hai rule ko narrow karne ke liye, lekin inspection na hone ki asal wajah Trust action hai. Zones ke bina bhi Allow rule inspection karega.
B. The rule must define the source network for inspection as well as the port. – Source network define karna optional hai (yahan "any" hai). Inspection na hone ka kaaran source network nahi, Trust action hai.
D. The rule is configured with the wrong setting for the source port. – Source port "any" hai, jo sahi hai. DNS traffic ke liye source port any hona chahiye kyunki client random ephemeral port use karta hai. Ye issue ka kaaran nahi hai.
Reference
- Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Access Control Rule Actions, specifically Trust action, which states that trusted traffic bypasses further inspection (intrusion, file, etc.).
An administrator Is setting up a Cisco PMC and must provide expert mode access for a security engineer. The engineer Is permitted to use only a secured out-of-band network workstation with a static IP address to access the Cisco FMC. What must be configured to enable this access?
A. Enable SSH and define an access list.
B. Enable HTTP and define an access list.
C. Enable SCP under the Access List section.
D. Enable HTTPS and SNMP under the Access List section
Explanation
To provide expert mode access to a Cisco Firepower Management Center (FMC), the administrator must enable SSH access. Expert mode is accessed via the Linux shell of the FMC, which requires an SSH connection to the appliance.
Furthermore, because the security engineer is restricted to using only a secured out-of-band network workstation with a static IP address, the administrator must configure an Access List under the SSH configuration to restrict access. The FMC allows you to specify which IP addresses or networks are permitted to connect via SSH. By defining the static IP of the authorized workstation in the access list, the administrator ensures that only that specific host can establish an SSH session to the FMC, meeting the security requirement.
Why the Other Options Are Incorrect
B. Enable HTTP and define an access list: HTTP (port 80) is used for the web interface, not for expert mode shell access. Expert mode requires SSH. Additionally, HTTP is insecure and not used for administrative shell access.
C. Enable SCP under the Access List section: SCP (Secure Copy Protocol) is used for file transfers over SSH, not for interactive expert mode access. While SCP may rely on SSH, enabling SCP alone does not provide the shell access required for expert mode.
D. Enable HTTPS and SNMP under the Access List section: HTTPS is used for the FMC web interface, and SNMP is used for monitoring. Neither provides expert mode shell access. Expert mode specifically requires SSH.
Reference
- Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Enabling SSH Access and configuring Access Lists for SSH to restrict administrative access to specific hosts.
An engineer must define a URL object on Cisco FMC. What is the correct method to specify the URL without performing SSL inspection?
A. Use Subject Common Name value.
B. Specify all subdomains in the object group.
C. Specify the protocol in the object
D. Include all URLs from CRL Distribution Points
Explanation
In Cisco Firepower Management Center (FMC), when you create a URL object and want to match a website without performing SSL decryption (SSL inspection), you must rely on the information available in the unencrypted TLS handshake. During the TLS handshake, the client sends a Server Name Indication (SNI) extension, and the server responds with a certificate that contains the Subject Common Name (CN) (and often Subject Alternative Names).
FMC uses the Subject Common Name from the server certificate to identify and categorize the URL/domain for policy enforcement. This allows the firewall to block or allow traffic to specific websites based on the certificate's CN field without needing to decrypt the actual payload of the SSL/TLS session.
Why the Other Options Are Incorrect
B. Specify all subdomains in the object group: While you can create URL objects with wildcards (e.g., `*.example.com`) to cover subdomains, this is not the specific method used to avoid SSL inspection. The key mechanism for matching without decryption is the Subject CN extraction from the certificate.
C. Specify the protocol in the object: URL objects in FMC do not require you to specify the protocol (e.g., HTTP/HTTPS) for the match to occur. The URL object matches based on the domain/hostname, and the protocol is handled by the port/application filters in the access control rule.
D. Include all URLs from CRL Distribution Points: CRL (Certificate Revocation List) Distribution Points are used for certificate validation, not for defining URL objects. This has no relevance to URL object creation or SSL inspection bypass.
Reference
- Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on URL Objects and SSL Policy, which explains that URL filtering can use the TLS handshake's Subject CN/SNI for categorization when traffic is not decrypted.
A network administrator reviews the file report for the last month and notices that all file types, except exe. show a disposition of unknown. What is the cause of this issue?
A. The malware license has not been applied to the Cisco FTD.
B. The Cisco FMC cannot reach the Internet to analyze files.
C. A file policy has not been applied to the access policy.
D. Only Spero file analysis is enabled.
Explanation
In Cisco Firepower Management Center (FMC), a file disposition of Unknown means the system queried the AMP cloud but the cloud has not yet assigned a classification to the file. The key distinction is that Spero analysis is an analysis option that applies specifically to executable files (like .exe). If only Spero analysis is enabled in the file policy, non-executable file types will be sent for Malware Cloud Lookup but will not receive a definitive disposition from the cloud—resulting in Unknown. Executable files, however, can be analyzed by Spero, which may assign a Malware disposition if it identifies malicious characteristics. This explains why exe files show a known disposition while all other file types remain Unknown.
Why the Other Options Are Incorrect
A. The malware license has not been applied to the Cisco FTD. – If the malware license were missing, the file policy containing malware actions (like Malware Cloud Lookup) would fail to deploy, and no file inspection would occur at all. Since file events are being generated and exe files show a disposition, the license is clearly present.
B. The Cisco FMC cannot reach the Internet to analyze files. – If the FMC could not reach the AMP cloud, all files would show an Unavailable disposition, not Unknown. The presence of Unknown indicates the cloud was successfully contacted but did not assign a classification.
C. A file policy has not been applied to the access policy. – If no file policy were applied, no file events would be generated at all. The fact that file dispositions are visible confirms that a file policy is active and inspecting traffic.
Reference
- Cisco Documentation: Firepower Management Center Configuration Guide – File Rule Actions and Malware Protection Options, including Spero Analysis limitations (executables only).
IT management is asking the network engineer to provide high-level summary statistics of the Cisco FTD appliance in the network. The business is approaching a peak season so the need to maintain business uptime is high. Which report type should be used to gather this information?
A. Malware Report
B. Standard Report
C. SNMP Report
D. Risk Report
Explanation
In Cisco Firepower Management Center (FMC), Standard Reports are designed to provide high-level summary statistics and trend analysis of the network and appliance health. This report type allows you to aggregate data (such as top attacks, top users, or appliance performance) over a specific time period, which is exactly what IT management is asking for to monitor business uptime during a peak season. You can customize standard reports to include specific metrics, and they can be generated on-demand or scheduled to run automatically and be emailed to stakeholders.
Why the Other Options Are Incorrect
A. Malware Report: A malware report focuses specifically on malware detections and file dispositions (e.g., files seen, malware blocked). It does not provide a broad high-level summary of overall appliance health or network uptime statistics.
C. SNMP Report: SNMP (Simple Network Management Protocol) is used for polling specific performance metrics (like CPU, memory, interface status) from the device. While SNMP data can be useful, FMC itself does not generate a native "SNMP Report" in its reporting dashboard. It is a monitoring protocol, not a report type.
D. Risk Report: The Risk Report (part of Firepower's network analysis) focuses on identifying hosts with the highest risk scores based on vulnerabilities, attacks, and behavioral anomalies. It is a security-centric report, not a general high-level summary of appliance health and uptime.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Working with Reports, specifically the differences between Standard Reports (comprehensive, customizable summaries) and other report types.
A network engineer is extending a user segment through an FTD device for traffic inspection without creating another IP subnet How is this accomplished on an FTD device in routed mode?
A. by leveraging the ARP to direct traffic through the firewall
B. by assigning an inline set interface
C. by using a BVI and create a BVI IP address in the same subnet as the user segment
D. by bypassing protocol inspection by leveraging pre-filter rules
Explanation
To extend a user segment through a Cisco Firepower Threat Defense (FTD) device for traffic inspection without creating another IP subnet, the engineer must use a Bridge Virtual Interface (BVI).
In FTD routed mode, you can group multiple physical interfaces into a Bridge Group to provide Layer 2 switching between them. The BVI acts as the Layer 3 gateway for that bridge group. By assigning the BVI an IP address that is in the same subnet as the existing user segment, the FTD can inspect the traffic passing between the bridged interfaces while maintaining the original IP addressing scheme. This effectively extends the Layer 2 broadcast domain through the firewall without requiring a new subnet.
Why the Other Options Are Incorrect
A. by leveraging the ARP to direct traffic through the firewall: ARP alone cannot force traffic through a firewall for inspection. While ARP is used to resolve MAC addresses within the bridge group, it does not provide the Layer 3 termination point needed for routing or management of the inspected segment.
B. by assigning an inline set interface: Inline sets are used for transparent mode (or inline IPS deployment). While they do allow traffic inspection without changing IP addressing, the question specifically states the FTD is in routed mode. In routed mode, inline sets are not the standard method for extending a Layer 2 segment; Bridge Groups with BVIs are used instead.
D. by bypassing protocol inspection by leveraging pre-filter rules: Pre-filter rules are used to quickly allow or block traffic before deep inspection, but they do not provide a mechanism to extend a network segment or route traffic through the firewall without changing subnets.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Bridge Virtual Interfaces (BVI) and Bridge Groups in routed mode, which explains how to pass traffic between interfaces in the same subnet without re-addressing.
An engineer is using the configure manager add Cisc402098527 command to add a new Cisco FTD device to the Cisco FMC; however, the device is not being added. Why Is this occurring?
A.
The NAT ID is required since the Cisco FMC is behind a NAT device.
B.
The IP address used should be that of the Cisco FTD. not the Cisco FMC.
C.
DONOTRESOLVE must be added to the command
D.
The registration key is missing from the command
The NAT ID is required since the Cisco FMC is behind a NAT device.
Explanation
When registering a Cisco FTD device to an FMC using the configure manager add command, the syntax requires both the FMC's IP address (or hostname) and the registration key. The command used in the scenario is:
configure manager add Cisc402098527
This command is missing the FMC's IP address entirely. However, analyzing the options, the most likely cause of failure when the FMC is behind a NAT device is the missing NAT ID.
When the FMC is behind a NAT device (i.e., the FTD cannot directly reach the FMC's real IP address), the configure manager add command must include the DONOTRESOLVE keyword instead of the FMC's IP address, along with a NAT ID. The NAT ID is a unique identifier that the FMC uses to map the incoming connection from the FTD back to the correct device entry in its database. Without the NAT ID (and using DONOTRESOLVE), the FTD cannot successfully register with a NAT-ed FMC.
Note: While the exact command in the prompt appears to be missing the IP address and the registration key is present as the second argument, in the context of typical Cisco exam questions for this scenario, the missing NAT ID (when the FMC is behind NAT) is the standard answer for registration failure.
Why the Other Options Are Incorrect
B. The IP address used should be that of the Cisco FTD, not the Cisco FMC: The configure manager add command is run on the FTD and must specify the FMC's IP address (or DONOTRESOLVE). Using the FTD's own IP would be incorrect.
C. DONOTRESOLVE must be added to the command: While DONOTRESOLVE is used when the FMC is behind NAT, it must be paired with a NAT ID. Simply adding DONOTRESOLVE without the NAT ID will still cause registration to fail.
D. The registration key is missing from the command: In the provided command, Cisc402098527 is present as the second argument, which is the registration key. The key is not missing.
Reference
Cisco Documentation: "Cisco Firepower Threat Defense Command Reference" – configure manager add syntax, including the use of DONOTRESOLVE and nat_id when the FMC is behind NAT.
An organization does not want to use the default Cisco Firepower block page when
blocking HTTP traffic. The organization wants to include information about its policies and
procedures to help educate the users whenever a block occurs. Which two steps must be
taken to meet these requirements? (Choose two.)
A.
Modify the system-provided block page result using Python.
B.
Create HTML code with the information for the policies and procedures.
C.
Edit the HTTP request handling in the access control policy to customized block.
D.
Write CSS code with the information for the policies and procedures.
E.
Change the HTTP response in the access control policy to custom.
Create HTML code with the information for the policies and procedures.
Change the HTTP response in the access control policy to custom.
Explanation
To replace the default Cisco Firepower block page with a custom page that educates users about the organization's policies and procedures, two steps are required:
B. Create HTML code with the information for the policies and procedures. – The custom block page is an HTML document. The administrator must create the HTML content that displays the organization's policy information to users when they are blocked.
E. Change the HTTP response in the access control policy to custom. – In the Cisco FMC, under the Access Control Policy settings (specifically the HTTP Response page settings), you must change the response type from the system-provided default to Custom. This allows you to paste or upload the custom HTML code created in step B. Once deployed, users who are blocked by an HTTP rule will see the organization's custom page instead of the default Cisco block page.
Why the Other Options Are Incorrect
A. Modify the system-provided block page result using Python: The block page is a static HTML response, not a Python script. There is no Python modification required or supported for this feature.
C. Edit the HTTP request handling in the access control policy to customized block: The correct setting is for the HTTP Response (what the user sees), not the request handling. The action is already "Block"; you are customizing the response page, not the request handling logic.
D. Write CSS code with the information for the policies and procedures: CSS (Cascading Style Sheets) is used for styling the HTML page, but the actual content (policies and procedures) must be written in HTML. CSS alone cannot deliver the required textual information.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Access Control Policy HTTP Responses, which explains how to configure a custom block page by selecting "Custom" and providing HTML content.
Which two types of objects are reusable and supported by Cisco FMC? (Choose two.)
A. dynamic key mapping objects that help link HTTP and HTTPS GET requests to Layer 7application protocols.
B. reputation-based objects that represent Security Intelligence feeds and lists, application filters based on category and reputation, and file lists
C. network-based objects that represent IP address and networks, port/protocols pairs, VLAN tags, security zones, and origin/destination country
D. network-based objects that represent FQDN mappings and networks, port/protocol pairs, VXLAN tags, security zones and origin/destination country
E. reputation-based objects, such as URL categories
Explanation
Cisco Firepower Management Center (FMC) uses reusable objects to simplify policy creation and maintenance. Among the choices provided, two accurately describe supported object types:
B. Reputation-based objects that represent Security Intelligence feeds and lists, application filters based on category and reputation, and file lists. – FMC supports Security Intelligence (SI) objects such as SI feeds, SI lists, and reputation-based objects (e.g., URL reputation, IP reputation). It also supports file lists and application filters based on category and reputation, which are reusable across access control policies. These objects are used to quickly block or allow traffic based on threat intelligence.
C. Network-based objects that represent IP address and networks, port/protocols pairs, VLAN tags, security zones, and origin/destination country. – FMC provides a variety of reusable network objects, including network objects (IP addresses, subnets, ranges), port objects (TCP/UDP port pairs), VLAN tag objects, security zone objects, and geolocation objects (origin/destination countries). These objects can be referenced in multiple access control rules and other policies.
Why the Other Options Are Incorrect
A. Dynamic key mapping objects that help link HTTP and HTTPS GET requests to Layer 7 application protocols: This is not a standard FMC object type. While FMC can detect applications and link them to HTTP/HTTPS traffic, there is no object type called "dynamic key mapping objects" in the FMC object manager.
D. Network-based objects that represent FQDN mappings and networks, port/protocol pairs, VXLAN tags, security zones and origin/destination country: While FMC does support FQDN objects, VXLAN tags are not standard reusable network objects in FMC. VXLAN is a data center overlay technology, and FMC does not provide a VXLAN tag object type for access control policies. VLAN tags are supported, but VXLAN tags are not.
E. Reputation-based objects, such as URL categories: While URL categories and reputation are used in FMC, this option is too narrow and overlaps with option B. Option B provides a more complete and accurate description of reputation-based objects (including SI feeds, lists, application filters, and file lists). Option E alone is not as comprehensive and is not one of the two best answers.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Reusable Objects, including network objects, port objects, security zones, geolocation, Security Intelligence feeds/lists, and file lists.
An engineer is investigating connectivity problems on Cisco Firepower that is using service group tags. Specific devices are not being tagged correctly, which is preventing clients from using the proper policies when going through the firewall How is this issue resolved?
A. Use traceroute with advanced options
B. Use Wireshark with an IP subnet filter
C. Use a packet capture with match criteria
D. Use a packet sniffer with correct filtering
Explanation
When troubleshooting Service Group Tag (SGT) issues on Cisco Firepower (FTD), the most effective method is to use the packet capture feature in FMC with specific match criteria (also known as an access control list or BPF filter) to isolate the traffic. SGT values are carried in the Cisco TrustSec (CTS) field of the Layer 2 frame, and FTD provides specific trace and capture capabilities to inspect these tags.
By creating a packet capture with match criteria, the engineer can capture only the traffic that is failing SGT tagging. The capture will reveal whether the SGT is correctly embedded in the packet's metadata or if it is missing/incorrect. This allows the engineer to determine if the issue is with the upstream switch (which should be tagging the traffic), the FTD itself, or the policy enforcement. FMC supports capturing SGT and other metadata in its packet capture tool for this exact purpose.
Why the Other Options Are Incorrect
A. Use traceroute with advanced options: Traceroute only shows the Layer 3 path to a destination. It does not inspect Layer 2 metadata like SGT tags, nor does it provide packet-level visibility into tagging issues.
B. Use Wireshark with an IP subnet filter: While Wireshark can capture SGTs (if the CTS field is included), running it on a mirror port may not show the SGT as presented to the FTD, especially if the tagging is happening at the switch ingress. FTD's native packet capture is the intended tool for this inspection. An IP subnet filter is also too broad to isolate a specific tagging issue.
D. Use a packet sniffer with correct filtering: "Packet sniffer" is a generic term. The specific, supported tool on FTD for this purpose is the packet capture feature configured via FMC (with match criteria), which provides the precise metadata visibility needed for SGT troubleshooting.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Packet Captures, including how to use match criteria and the option to include SGT/CTS information in the capture.
| Page 8 out of 35 Pages |
| 345678910111213 |
| 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.