Topic 3: Management and Troubleshooting
Which group within Cisco does the Threat Response team use for threat analysis and research?
A. Cisco Deep Analytics
B. OpenDNS Group
C. Cisco Network Response
D. Cisco Talos
Explanation
Cisco Talos is Cisco's threat intelligence and security research organization. It consists of researchers, analysts, and engineers who investigate emerging threats, analyze malware, research vulnerabilities, and provide threat intelligence that supports Cisco's security products.
Cisco Threat Response integrates threat intelligence from Cisco Talos and third-party sources to investigate indicators of compromise (IOCs), correlate threat information, and help security teams identify potential threats quickly. Therefore, Cisco Talos is the organization that provides the threat research and intelligence needed by the Threat Response team.
Why the Other Options Are Incorrect
A. Cisco Deep Analytics: This is not the Cisco threat intelligence organization identified as the source of threat research for Cisco Threat Response. That role is associated with Cisco Talos.
B. OpenDNS Group: OpenDNS is part of Cisco's security portfolio and contributes to DNS-layer security through Cisco Umbrella. However, it is not the primary threat research organization described in the question.
C. Cisco Network Response: This is not the recognized name of Cisco's threat intelligence research organization. Cisco Talos provides the threat intelligence and security research relevant to this scenario.
Reference
Cisco Threat Response documentation: Cisco Threat Response integrates threat intelligence from Cisco Talos and third-party sources to investigate indicators of compromise and help confirm threats. Cisco Talos is Cisco's threat intelligence and security research organization.
Which command is run at the CLI when logged in to an FTD unit, to determine whether the unit is managed locally or by a remote FMC server?
A. system generate-troubleshoot
B. show configuration session
C. show managers
D. show running-config | include manager
Explanation
When accessing a Cisco Firepower Threat Defense (FTD) device through the CLI, the show managers command displays the management application configured to manage the device. It allows administrators to determine whether the device is managed by a remote Firepower Management Center (FMC) or locally through Firepower Device Manager (FDM).
If the device is managed by a remote FMC, the command output displays the manager information, including the FMC IP address and registration status. If the device is managed locally, the output displays "Managed locally." Therefore, show managers is the purpose-built command for verifying the device's management configuration.
Why the Other Options Are Incorrect
A. system generate-troubleshoot: This command generates a troubleshooting archive containing diagnostic information for analysis. It is not specifically intended to display the device's management status.
B. show configuration session: This command relates to configuration sessions and does not provide the dedicated overview of the configured management application.
D. show running-config | include manager: This command filters the running configuration for lines containing the word manager. Although it may reveal related configuration entries, it is not the dedicated command for checking the management application and registration status.
Reference
Cisco Firepower Threat Defense Command Reference: The show managers command displays the applications defined to manage the device configuration and distinguishes remote management from local management.
Within Cisco Firepower Management Center, where does a user add or modify widgets?
A. dashboard
B. reporting
C. context explorer
D. summary tool
Explanation
In Cisco Firepower Management Center (FMC), widgets are added and customized directly on the Dashboard. Widgets are small, self-contained components that display information about different aspects of the system, such as security events, analysis results, and operational status.
To add a widget, navigate to the Dashboard, select the appropriate tab, and click Add Widgets. You can then choose from the available widget categories, such as Analysis & Reporting or Operations. Widget preferences, including update frequency and display settings, can also be configured directly from the dashboard.
Why the Other Options Are Incorrect
B. Reporting: The Reporting section is used to create, generate, and schedule reports based on report templates. It is not the primary location for adding or customizing dashboard widgets.
C. Context Explorer: Context Explorer provides graphical views of network activity and related data. It is a separate analysis tool, not the interface used to add or manage dashboard widgets.
D. Summary Tool: This is not the dedicated interface for widget management. A summary dashboard may contain predefined widgets, but adding or modifying widgets is performed through the Dashboard interface.
Reference
Cisco Firepower Management Center Configuration Guide — Dashboards: The documentation describes how to add widgets to a dashboard and configure widget preferences directly through the Dashboard interface.
In which two places can thresholding settings be configured? (Choose two.)
A. on each IPS rule
B. globally, within the network analysis policy
C. globally, per intrusion policy
D. on each access control rule
E. per preprocessor, within the network analysis policy
Explanation
Cisco Firepower supports intrusion event thresholding at two levels: globally within an intrusion policy and individually for specific intrusion rules. Each intrusion policy includes a default global rule threshold that applies to intrusion rules and preprocessor rules unless a more specific threshold overrides it.
Administrators can also configure thresholds for individual intrusion rules to override the global setting for specific signatures. This two-level approach provides flexibility by allowing a general limit on event volume while preserving more granular control over high-priority signatures.
Why the Other Options Are Incorrect
B. Globally, within the network analysis policy: Network analysis policies primarily control protocol inspection, decoding, and preprocessing settings. Global intrusion event thresholding is configured within the intrusion policy, not the network analysis policy.
D. On each access control rule: Access control rules determine how traffic is handled, such as allowing, blocking, or trusting it. They do not provide the per-intrusion-rule threshold settings described in the question.
E. Per preprocessor, within the network analysis policy: Although individual preprocessor rules can have their own thresholds, those thresholds are configured through the intrusion policy's rule settings, not within the network analysis policy. Global thresholds can also apply to preprocessor-generated events.
Reference
Cisco Firepower Management Center Configuration Guide — Global Rule Thresholding Basics and Setting Intrusion Event Thresholds: The documentation explains global threshold configuration within an intrusion policy and individual thresholds for shared object rules, standard text rules, and preprocessor rules.
When do you need the file-size command option during troubleshooting with packet capture?
A. when capture packets are less than 16 MB
B. when capture packets are restricted from the secondary memory
C. when capture packets exceed 10 GB
D. when capture packets exceed 32 MB
Explanation
According to Cisco's documentation, the file-size option is used when packet captures need to exceed the default 32 MB capture buffer limit. It allows administrators to specify a capture file size from 32 MB up to 10 GB. The captured packet data is written to a file on disk (flash storage) rather than being stored solely in the memory buffer.
Therefore, the file-size option is appropriate when a larger packet capture is required for troubleshooting or traffic analysis beyond the default buffer capacity.
Why the Other Options Are Incorrect
A. When captured packets are less than 16 MB: This is incorrect because captures smaller than the default 32 MB buffer limit do not require the file-size option solely because of their size.
B. When captured packets are restricted from secondary memory: This is incorrect. The option controls the capture file size and allows packet data to be written to disk. It does not address a restriction on secondary memory.
C. When captured packets exceed 10 GB: This is incorrect because 10 GB is the maximum supported capture file size for the documented file-size option. It cannot be used to configure a capture file larger than that limit.
Reference
Cisco Secure Firewall Management Center Administration Guide and Cisco Threat Defense Command Reference: The file-size option supports packet capture file sizes from 32 MB to 10 GB for captures that exceed the default 32 MB buffer limit.
What is the benefit of selecting the trace option for packet capture?
A. The option indicates whether the packet was dropped or successful
B. The option indicated whether the destination host responds through a different path.
C. The option limits the number of packets that are captured
D. The option captures details of each packet
Explanation
When you enable the Trace option during a packet capture in Cisco Firepower Management Center (FMC), the system provides additional information about how packets are processed by the firewall inspection engine. This includes the processing verdict, indicating whether a packet was successfully processed or dropped.
Trace helps administrators troubleshoot traffic flow by revealing how the firewall handles packets, beyond simply displaying their contents. This makes it useful for investigating unexpected drops and verifying packet-processing behavior.
Why the Other Options Are Incorrect
B. The option indicates whether the destination host responds through a different path: Trace examines packet processing within the FTD. It does not determine whether the destination host sends return traffic through an alternative network path.
C. The option limits the number of packets that are captured: This is incorrect. Trace adds packet-processing information, while the separate Trace Count setting controls how many packets are traced.
D. The option captures details of each packet: This is incomplete as the best answer. Standard packet capture already records packet contents. The specific benefit of Trace is that it provides additional processing information and a verdict indicating whether the packet was dropped or successfully processed.
Reference
Cisco Firepower Management Center Configuration Guide: The packet capture Trace option provides a verdict indicating whether a packet was dropped or successfully processed.
When creating a report template, how can the results be limited to show only the activity of a specific subnet?
A. Create a custom search in Firepower Management Center and select it in each sectionof the report.
B. Add an Input Parameter in the Advanced Settings of the report, and set the type to Network/IP.
C. Add a Table View section to the report with the Search field defined as the network in CIDR format.
D. Select IP Address as the X-Axis in each section of the report.
Explanation
In Cisco Firepower Management Center (FMC), to dynamically limit report results to a specific subnet when creating a report template, configure an Input Parameter under the template's Advanced Settings. When creating the parameter, select the Network/IP type, which supports an IP address or network segment in CIDR format.
After defining the input parameter, apply it to the Search field of the relevant report section, such as Source IP or Destination IP. When the report is generated, FMC prompts the user to enter the desired subnet, allowing the report results to be filtered dynamically for that network. This approach makes the template reusable for different subnets without requiring a separate template for each one.
Why the Other Options Are Incorrect
A. Create a custom search in Firepower Management Center and select it in each section of the report: A saved custom search can filter report results, but it does not provide the same generation-time flexibility as an input parameter that prompts the user to specify a subnet when running the report.
C. Add a Table View section to the report with the Search field defined as the network in CIDR format: This can apply a specific, predefined network filter, but it does not provide the reusable, parameter-driven behavior requested. Input parameters are configured in Advanced Settings and then applied to the appropriate report section.
D. Select IP Address as the X-Axis in each section of the report: The X-Axis controls how data is grouped or displayed in a chart. It does not filter the underlying dataset to restrict results to a particular subnet.
Reference
Cisco Firepower Management Center Configuration Guide — Report Templates and Input Parameters: The Network/IP parameter type accepts an IP address or network segment in CIDR format. Input parameters allow users to supply values when generating a report, enabling dynamic filtering of report results.
Which command is typed at the CLI on the primary Cisco FTD unit to temporarily stop running high- availability?
A. configure high-availability resume
B. configure high-availability disable
C. system support network-options
D. configure high-availability suspend
Explanation
On a Cisco Firepower Threat Defense (FTD) device, the configure high-availability suspend command temporarily suspends the high-availability (HA) configuration without permanently removing the relationship between the active and standby units. This allows administrators to perform maintenance or troubleshooting while retaining the existing HA configuration for later resumption.
When executed on the active unit, the command prompts for confirmation. After confirmation, HA is suspended on both the active and standby units. The command output typically displays "Successfully suspended high-availability." This is useful when temporarily stopping HA monitoring without permanently breaking the configuration.
Why the Other Options Are Incorrect
A. configure high-availability resume: This command performs the opposite operation. It resumes a previously suspended HA configuration and allows the units to re-establish their active/standby relationship.
B. configure high-availability disable: This command disables HA and removes the existing failover configuration, rather than temporarily suspending it while retaining the configuration.
C. system support network-options: This is a support-related command and does not provide the specific function of temporarily suspending high availability.
Reference
Cisco Firepower Threat Defense Command Reference: The configure high-availability command supports the suspend, resume, and disable options. The suspend option temporarily pauses HA while retaining its configuration, allowing it to be resumed later.
What is a behavior of a Cisco FMC database purge?
A. User login and history data are removed from the database if the User Activity check box is selected.
B. Data can be recovered from the device
C. The appropriate process is restarted.
D. The specified data is removed from Cisco FMC and kept for two weeks
Explanation
According to Cisco's official documentation, when you perform a database purge on the Firepower Management Center (FMC), the system removes the specified data, such as discovery, identity, connection, or Security Intelligence events, from the database. A critical behavior of this operation is that the appropriate process is restarted after the purge is completed.
Why the Other Options Are Incorrect
A. User login and history data are removed from the database if the User Activity check box is selected: This is inaccurate. The User Activity checkbox removes user activity events, whereas the User Identities checkbox removes user login and user history data.
B. Data can be recovered from the device: This is false. Cisco documentation explicitly warns that once data is deleted through a purge, it cannot be recovered.
D. The specified data is removed from Cisco FMC and kept for two weeks: There is no such retention period. The data is permanently deleted when the purge is performed.
Reference
Cisco Firepower Management Center Configuration Guide — Data Storage: "Note that when you purge a database, the appropriate process is restarted" and "After the data is deleted, it cannot be recovered.
Which limitation applies to Cisco Firepower Management Center dashboards in a multidomain environment?
A. Child domains can view but not edit dashboards that originate from an ancestor domain.
B. Child domains have access to only a limited set of widgets from ancestor domains.
C. Only the administrator of the top ancestor domain can view dashboards
D. Child domains cannot view dashboards that originate from an ancestor domain
Explanation
In a Cisco FMC multidomain deployment, dashboards and their widgets are scoped according to the domain hierarchy. According to Cisco's official documentation, you cannot view dashboards from an ancestor domain while logged into a child or leaf domain. The system displays dashboards relevant to the current domain. If you need a similar view in a child domain, the documented workaround is to create a new dashboard by copying the ancestor dashboard. However, the original ancestor dashboard remains inaccessible from the child domain.
Why the Other Options Are Incorrect
A. Child domains can view but not edit dashboards that originate from an ancestor domain: This is false. The restriction applies to visibility, not merely editing permissions. Child domains cannot view the ancestor dashboard directly.
B. Child domains have access to only a limited set of widgets from ancestor domains: This is inaccurate. The restriction applies at the dashboard level, not just to individual widgets. You cannot directly access specific widgets from an ancestor dashboard as a way around this limitation.
C. Only the administrator of the top ancestor domain can view dashboards: This is false. Users in the Global (top) domain can view dashboards, but users in other domains can also view dashboards available within their own domain. The restriction concerns viewing dashboards from an ancestor domain while working in a child domain.
Reference
Cisco Secure Firewall Management Center Administration Guide: "In a multidomain deployment, you cannot view dashboards from an ancestor domain. However, you can create a new dashboard that is a copy of the higher-level dashboard."
Which two OSPF routing features are configured in Cisco FMC and propagated to Cisco FTD? (Choose two.)
A. OSPFv2 with IPv6 capabilities
B. virtual links
C. SHA authentication to OSPF packets
D. area boundary router type 1 LSA filtering
E. MD5 authentication to OSPF packets
Explanation
Cisco FMC supports configuring OSPF features that are deployed to managed FTD devices. Virtual links can be configured to logically connect a disconnected OSPF area to the backbone area (Area 0). MD5 authentication is also supported to secure OSPF packet exchanges. Both features are available in the FMC OSPF configuration interface.
Why the Other Options Are Incorrect
A. OSPFv2 with IPv6 capabilities: OSPFv2 is designed for IPv4 routing and does not support IPv6. IPv6 routing requires OSPFv3, which is configured separately in FMC.
C. SHA authentication to OSPF packets: FMC supports MD5 and clear-text password authentication for OSPF, but SHA authentication is not supported in the described configuration.
D. Area boundary router Type 1 LSA filtering: FTD supports Type 3 LSA filtering on area border routers (ABRs), not Type 1 LSA filtering. Type 1 LSAs describe routers within an area and are flooded throughout that area.
Reference
Cisco Firepower Management Center Configuration Guide: OSPF for FTD documents support for virtual links and MD5 authentication. It also explains that OSPFv2 does not support IPv6 and that Type 3 LSA filtering is supported on ABRs.
What is the maximum bit size that Cisco FMC supports for HTTPS certificates?
A. 1024
B. 8192
C. 4096
D. 2048
Explanation
Cisco Firepower Management Center (FMC) supports HTTPS certificates with public server keys up to 4096 bits. According to Cisco's official documentation, if the certificate used by FMC contains a public server key larger than 4096 bits, you will be unable to log in to the FMC web interface. This is a documented limitation, meaning an 8192-bit certificate cannot be used for FMC web access.
Why the Other Options Are Incorrect
A. 1024: This is below the supported maximum and is not the documented upper limit for FMC HTTPS certificates.
B. 8192: Certificates with public server keys larger than 4096 bits, including 8192-bit keys, are not supported for FMC web interface access. Using such a certificate can prevent you from logging in to the GUI.
D. 2048: A 2048-bit certificate is supported, but it is not the maximum. Cisco documentation identifies 4096 bits as the upper limit.
Reference
Cisco Secure Firewall Management Center Administration Guide: "The FMC supports 4096-bit HTTPS certificates. If the certificate used by the FMC was generated using a public server key larger than 4096 bits, you will not be able to log in to the Firepower Management Center web interface."
| Page 5 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.