Topic 1: Deployment
An analyst is reviewing the Cisco FMC reports for the week. They notice that some peer-topeer applications are being used on the network and they must identify which poses the greatest risk to the environment. Which report gives the analyst this information?
A. Attacks Risk Report
B. User Risk Report
C. Network Risk Report
D. Advanced Malware Risk Report
Explanation
The Network Risk Report in Cisco Firepower Management Center (FMC) is designed to provide a high-level summary of risks detected on the network. It specifically focuses on hosts and network behavior, including the use of potentially risky applications such as peer-to-peer (P2P) file-sharing programs. This report helps analysts identify which hosts or applications pose the greatest risk to the environment by aggregating risk scores and highlighting suspicious or high-risk activity.
Why the Other Options Are Incorrect
A. Attacks Risk Report: This report focuses on intrusion events (IPS) and attack-related statistics, such as total attacks, relevant attacks, and hosts connected to command-and-control (CnC) servers. It does not specifically highlight peer-to-peer application usage or provide a general network risk assessment for P2P traffic.
B. User Risk Report: This is not a standard FMC risk report template. The standard risk reports provided by FMC are the Advanced Malware Risk Report, Attacks Risk Report, and Network Risk Report.
D. Advanced Malware Risk Report: This report is centered on malware detections and file analysis, not on network application usage like peer-to-peer traffic. It provides visibility into malware events and file dispositions rather than general network risk from P2P applications.
Reference
Cisco Documentation: Cisco Secure Firewall Management Center Administration Guide – Section on Risk Report Templates, which lists the Network Risk Report as the template for analyzing network-level risks, including application usage and host behavior.
With a recent summer time change, system logs are showing activity that occurred to be an hour behind real time Which action should be taken to resolve this issue?
A. Manually adjust the time to the correct hour on all managed devices
B. Configure the system clock settings to use NTP with Daylight Savings checked
C. Manually adjust the time to the correct hour on the Cisco FMC.
D. Configure the system clock settings to use NTP
Explanation
The issue described is a classic symptom of a Daylight Saving Time (DST) misconfiguration. When the clocks shift (e.g., for summer time), devices that are not configured to automatically adjust for DST will remain an hour behind (or ahead) of the actual local time.
In Cisco Firepower Management Center (FMC), time synchronization and DST handling are configured in the system settings. To resolve this, the administrator must configure the system clock to use NTP for accurate time synchronization and ensure that the Daylight Savings option is checked/enabled. This allows the FMC (and by extension, the managed devices synced to it) to automatically adjust the clock during DST transitions, keeping the logs aligned with real local time.
Why the Other Options Are Incorrect
A. Manually adjust the time to the correct hour on all managed devices: While this would temporarily fix the time, it is not a scalable or permanent solution. The devices would drift again or fail to adjust during the next DST transition. Managed devices typically sync their time from the FMC, so manual adjustments on each device are unnecessary and error-prone.
C. Manually adjust the time to the correct hour on the Cisco FMC: Similar to option A, this is only a temporary fix. Without enabling the DST setting, the FMC will not automatically adjust the clock during future time changes.
D. Configure the system clock settings to use NTP: While NTP is necessary for accurate time synchronization, simply enabling NTP without checking the Daylight Savings option will not solve the problem. NTP provides UTC time, but the DST setting is what tells the system to apply the local time offset for summer time. Both are required to fully resolve the issue.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on System Configuration > Time Synchronization, which explains how to configure NTP and enable the Daylight Savings Time (DST) option to automatically adjust for seasonal time changes.
An organization recently implemented a transparent Cisco FTD in their network. They must ensure that the device does not respond to insecure SSL/TLS protocols. Which action accomplishes the task?
A. Modify the device's settings using the device management feature within Cisco FMC to force only secure protocols
B. Use the Cisco FTD platform policy to change the minimum SSL version on the device to TLS 1.2.
C. Enable the UCAPL/CC compliance on the device to support only the most secure protocols available.
D. Configure a FlexConfig object to disable any insecure TLS protocols on the Cisco FTD device.
Explanation
In Cisco Firepower Threat Defense (FTD), the ability to specifically disable insecure SSL/TLS protocols (such as SSLv3, TLS 1.0, TLS 1.1) on the device's management or data plane interfaces is not directly exposed as a standard toggle in the FMC GUI. To enforce strict cryptographic standards and disable insecure protocols for the FTD device itself (e.g., for the web server, VPN, or management access), you must use FlexConfig.
FlexConfig allows you to push raw CLI commands to the FTD device that are not natively supported in the FMC graphical interface. By creating a FlexConfig object, you can apply the necessary underlying IOS/FTD CLI commands to disable specific SSL/TLS versions and ensure the device only accepts secure connections.
Why the Other Options Are Incorrect
A. Modify the device's settings using the device management feature within Cisco FMC to force only secure protocols: There is no single "force only secure protocols" toggle in the FMC device management settings that comprehensively disables insecure TLS versions across all services.
B. Use the Cisco FTD platform policy to change the minimum SSL version on the device to TLS 1.2: The Platform Policy in FMC does not provide a setting to change the minimum SSL/TLS version for the device's services.
C. Enable the UCAPL/CC compliance on the device to support only the most secure protocols available: While enabling UCAPL/CC compliance does enforce strict security and cryptographic standards, it is a broad compliance mode that changes many device behaviors. It is not the targeted, specific action to simply disable insecure SSL/TLS protocols, and FlexConfig is the standard method for granular TLS version control.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on FlexConfig Policies, which explains how to use FlexConfig to configure features not supported in the GUI, including specific cryptographic/TLS settings.
In a multi-tennent deployment where multiple domains are in use. which update should be applied outside of the Global Domain?
A. minor upgrade
B. local import of intrusion rules
C. Cisco Geolocation Database
D. local import of major upgrade
Explanation
In a Cisco Firepower Management Center (FMC) multi-tenant deployment using domains, the Global domain is the parent domain that governs all sub-domains. System-wide updates and shared intelligence must be applied at the Global level so they propagate down to all tenants.
However, custom intrusion rules (or local rule imports) are often specific to a particular tenant's environment, compliance requirements, or network traffic. If a tenant needs a custom rule that isn't part of the global policy, that local import of intrusion rules must be applied within that specific sub-domain, outside of the Global Domain, so it doesn't affect other tenants.
Why the Other Options Are Incorrect
A. Minor upgrade: Software upgrades (major or minor) are system-wide operations and must be applied at the Global domain level to ensure all domains run the same compatible software version.
C. Cisco Geolocation Database: The Geolocation database is a global intelligence feed used by all tenants. Updates to this database are applied at the Global domain level so all sub-domains receive the updated geolocation data.
D. Local import of major upgrade: Major upgrades cannot be applied locally to just one domain; they are system-level operations that must be performed from the Global domain.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Domain Management, which explains that global updates (software, geolocation, VDB) are applied in the Global domain, while domain-specific configurations (like custom intrusion rules) are applied in the respective sub-domains.
A VPN user is unable to conned lo web resources behind the Cisco FTD device terminating
the connection. While troubleshooting, the network administrator determines that the DNS
responses are not getting through the Cisco FTD What must be done to address this issue
while still utilizing Snort IPS rules?
A.
Uncheck the "Drop when Inline" box in the intrusion policy to allow the traffic
B. Modify the Snort rules to allow legitimate DNS traffic to the VPN users
C. Disable the intrusion rule threshes to optimize the Snort processing.
D. Decrypt the packet after the VPN flow so the DNS queries are not inspected
Explanation
The correct answer is D. Decrypt the packet after the VPN flow so the DNS queries are not inspected.
When a VPN tunnel terminates on a Cisco FTD device, the encrypted VPN traffic arrives at the device, gets decrypted by the VPN engine, and is then passed to the Snort inspection engine. If DNS responses are not getting through, Snort is likely inspecting the decrypted VPN traffic and dropping the DNS responses (e.g., due to inline normalization, stream reassembly issues, or false positives from IPS rules).
To resolve this while still utilizing Snort IPS rules for other traffic, you must change the inspection order so that the VPN traffic is decrypted before it reaches Snort, and configure the policy to bypass Snort for that specific VPN-decapsulated traffic. In FMC, this is typically achieved by creating a Prefilter Policy or adjusting the VPN policy to ensure DNS queries from the VPN pool are exempted from Snort inspection. This ensures that the DNS responses get through the firewall without being dropped, while Snort continues to protect the rest of the network.
Why the Other Options Are Incorrect
A. Uncheck the "Drop when Inline" box in the intrusion policy to allow the traffic: This globally disables Snort's ability to drop traffic inline, which cripples the IPS functionality across the entire network. It does not solve the specific issue for VPN DNS traffic while maintaining Snort rules.
B. Modify the Snort rules to allow legitimate DNS traffic to the VPN users: Modifying Snort rules is too granular and risky. It can create security gaps and does not address the underlying inspection order issue that causes the DNS responses to be dropped.
C. Disable the intrusion rule thresholds to optimize the Snort processing: Disabling thresholds does not fix the DNS response issue and can lead to excessive false positives and performance degradation, as it removes the rate-limiting on rule triggers.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Prefilter Policies and VPN Traffic Inspection, explaining how to bypass Snort for specific traffic while maintaining IPS for the rest of the network.
A network engineer sets up a secondary Cisco FMC that is integrated with Cisco Security Packet Analyzer What occurs when the secondary Cisco FMC synchronizes with the primary Cisco FMC?
A. The existing integration configuration is replicated to the primary Cisco FMC
B. The existing configuration for integration of the secondary Cisco FMC the Cisco Security Packet Analyzer is overwritten.
C. The synchronization between the primary and secondary Cisco FMC fails
D. The secondary Cisco FMC must be reintegrated with the Cisco Security Packet Analyzer after the synchronization
Explanation
When setting up a secondary Cisco Firepower Management Center (FMC) in a High Availability (HA) pair, the configuration from the primary FMC is synchronized to the secondary FMC. According to Cisco documentation, any existing configurations on the intended secondary FMC—specifically including integrations with Cisco Security Packet Analyzer—will be overwritten during this synchronization process. If you need to preserve that integration, you must recreate it on the primary FMC after synchronization is complete.
Why the Other Options Are Incorrect
A. The existing integration configuration is replicated to the primary Cisco FMC: Synchronization flows from the primary (active) FMC to the secondary (standby) FMC, not the other way around. Therefore, the secondary's configuration is overwritten, not replicated to the primary.
C. The synchronization between the primary and secondary Cisco FMC fails: The synchronization process is designed to overwrite the secondary's configuration. It does not fail simply because a Packet Analyzer integration exists on the secondary.
D. The secondary Cisco FMC must be reintegrated with the Cisco Security Packet Analyzer after the synchronization: The secondary FMC loses its integration configuration because it is overwritten. If the integration is still required for the HA pair, it must be configured on the primary FMC (which will then sync to the secondary), rather than being re-integrated directly on the secondary.
Reference
Cisco Documentation: Firepower Management Center High Availability configuration guide, which states: "Note that any existing configurations on the intended secondary Firepower Management Center for integrations with Cisco Security Packet Analyzer will be overwritten when synchronization occurs. If necessary, recreate any such configurations on the intended primary Firepower Management Center."
A network engineer is receiving reports of users randomly getting disconnected from their corporate applications which traverses the data center FTD appliance Network monitoring tools show that the FTD appliance utilization is peaking above 90% of total capacity. What must be done in order to further analyze this issue?
A. Use the Packet Export feature to save data onto external drives
B. Use the Packet Capture feature to collect real-time network traffic
C. Use the Packet Tracer feature for traffic policy analysis
D. Use the Packet Analysis feature for capturing network data
Explanation
When a Cisco FTD appliance is experiencing high utilization (peaking above 90%), it can cause intermittent connectivity issues, such as users being randomly disconnected. To analyze this issue further and see exactly what is happening at the packet level during these peak times, the engineer should use the Packet Capture feature on the FMC/FTD.
Packet Capture allows the engineer to capture real-time traffic traversing the FTD, applying specific match criteria (e.g., the specific users' IP addresses or the application ports) to isolate the problem. This data can then be downloaded and analyzed (often in Wireshark) to determine if packets are being dropped, delayed, or if there is a specific traffic pattern causing the high utilization and disconnects.
Why the Other Options Are Incorrect
A. Use the Packet Export feature to save data onto external drives: FMC/FTD does not have a "Packet Export" feature for saving data to external drives for this type of analysis. The correct feature is Packet Capture, which stores the capture in a circular buffer on the device for download via the FMC.
C. Use the Packet Tracer feature for traffic policy analysis: Packet Tracer (or the Packet Trace feature in FTD) is a simulation tool. It shows how a synthetic packet would be handled by the policies (NAT, Access Control, etc.), but it does not capture real-time traffic or show the actual live packets causing the high CPU/utilization issue.
D. Use the Packet Analysis feature for capturing network data: "Packet Analysis" is a general term. The specific, built-in feature on Cisco FTD to capture network data is called Packet Capture. There is no distinct "Packet Analysis" feature for this purpose on the FTD itself.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Packet Captures, which explains how to configure and run a packet capture on FTD devices to troubleshoot network traffic issues.
An engineer is restoring a Cisco FTD configuration from a remote backup using the command restore remote-manager-backup location 1.1.1.1 admin /volume/home/admin BACKUP_Cisc394602314.zip on a Cisco FMG. After connecting to the repository, an error occurred that prevents the FTD device from accepting the backup file. What is the problem?
A. The backup file is not in .cfg format.
B. The backup file is too large for the Cisco FTD device
C. The backup file extension was changed from tar to zip
D. The backup file was not enabled prior to being applied
Explanation
When restoring a Cisco Firepower Threat Defense (FTD) configuration from a remote backup, the backup file generated by the FTD backup process uses a specific format and naming convention. According to Cisco documentation, the backup archive uses a .tar extension and is often named something like BACKUP_
If the file extension has been manually changed (for example, from .tar to .zip), the FTD restore process may fail to recognize the archive format. The restore command expects the native backup format and may reject the file during validation, resulting in the error described in the scenario. The fix is to rename the file back to its original .tar extension before attempting the restore.
Why the Other Options Are Incorrect
A. The backup file is not in .cfg format: FTD backups are not stored as .cfg files. They are stored as .tar archives. The absence of a .cfg extension is expected and is not the cause of the error.
B. The backup file is too large for the Cisco FTD device: While there are size limitations based on available disk space, the error in the scenario is related to file format recognition, not size. A size issue typically presents a different, specific error message.
D. The backup file was not enabled prior to being applied: There is no step in the FTD restore process that requires the backup file to be "enabled" before it can be applied. The file needs to be in the correct format and accessible from the repository.
Reference
Cisco Documentation: "Cisco Firepower Threat Defense Command Reference" — restore remote-manager-backup command, which specifies the backup file format and naming conventions.
An engainer must add DNS-specific rules to me Cisco FTD intrusion policy. The engineer wants to use the rules currently in the Cisco FTD Snort database that are not already enabled but does not want to enable more than are needed. Which action meets these requirements?
A. Change the dynamic state of the rule within the policy.
B. Change the base policy to Security over Connectivity.
C. Change the rule state within the policy being used
D. Change the rules using the Generate and Use Recommendations feature.
Explanation
Cisco Firepower Management Center (FMC) includes a Recommendations feature (Generate and Use Recommendations) that analyzes the network traffic patterns for a specific intrusion policy. It provides a list of Snort rules from the Cisco database that are not currently enabled but are recommended based on the traffic observed in your environment.
By using this feature, the engineer can selectively enable only the DNS-specific rules that are relevant to the network, rather than enabling all available rules or manually guessing which ones to turn on. This ensures that only the necessary rules are enabled, optimizing performance and meeting the requirement of not enabling more rules than needed.
Why the Other Options Are Incorrect
A. Change the dynamic state of the rule within the policy:
The dynamic state (e.g., Drop, Generate Events) controls how an enabled rule handles traffic. It does not help in identifying which unenabled rules are relevant to the network.
B. Change the base policy to Security over Connectivity:
Changing the base policy affects the overall security posture and default rule set, but it does not provide a targeted way to find and enable only the needed DNS rules from the database.
C. Change the rule state within the policy being used:
This involves manually enabling rules, which requires the engineer to already know exactly which rules to enable. It does not provide the intelligence to know which of the unenabled database rules are actually needed for the environment.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Intrusion Policy Recommendations, which explains how to generate and apply recommendations based on network traffic to enable the most relevant rules.
A network engineer is logged into the Cisco AMP for Endpoints console and sees a
malicious verdict for an identified SHA-256 hash. Which configuration is needed to mitigate
this threat?
A. Add the hash to the simple custom deletion list.
B. Use regular expressions to block the malicious file.
C. Enable a personal firewall in the infected endpoint.
D. Add the hash from the infected endpoint to the network block list.
Explanation
In Cisco AMP for Endpoints, when a file is identified as malicious via its SHA-256 hash, the most direct and effective mitigation is to create a Simple Custom Detection (SCD) list. Administrators add the malicious SHA-256 hash to this list, and then apply the list to the relevant policy. Once the policy is deployed, the AMP connector on the endpoints will detect the file by its hash and take the configured action, typically quarantining or deleting the file. (Note: "Simple custom deletion list" in the option refers to the action taken by the Simple Custom Detection list, which is to delete/quarantine the file).
Why the Other Options Are Incorrect
B. Use regular expressions to block the malicious file:
AMP for Endpoints does not use regular expressions to block files based on hashes. It uses exact SHA-256 hash matching for custom detections. Regular expressions are not applicable here.
C. Enable a personal firewall in the infected endpoint:
A personal firewall controls network connections, not file execution. It will not block a malicious file that is already on the endpoint or prevent it from running.
D. Add the hash from the infected endpoint to the network block list:
A "network block list" is used to block IP addresses, domains, or URLs at the network level (e.g., on a firewall), not to block file execution on an endpoint. To block a file by hash, you must use the Endpoint custom detection list.
Reference
Cisco Documentation: "Cisco AMP for Endpoints User Guide" – Section on Simple Custom Detections, which explains how to add SHA-256 hashes to block, quarantine, or delete specific files across the organization.
A security engineer is configuring a remote Cisco FTD that has limited resources and internet bandwidth. Which malware action and protection option should be configured to reduce the requirement for cloud lookups?
A. Malware Cloud Lookup and dynamic analysis
B. Block Malware action and dynamic analysis
C. Block Malware action and local malware analysis
D. Block File action and local malware analysis
Explanation
In Cisco AMP for Endpoints, when a file is identified as malicious via its SHA-256 hash, the most direct and effective mitigation is to create a Simple Custom Detection (SCD) list. Administrators add the malicious SHA-256 hash to this list, and then apply the list to the relevant policy. Once the policy is deployed, the AMP connector on the endpoints will detect the file by its hash and take the configured action, typically quarantining or deleting the file. (Note: "Simple custom deletion list" in the option refers to the action taken by the Simple Custom Detection list, which is to delete/quarantine the file).
Why the Other Options Are Incorrect
B. Use regular expressions to block the malicious file:
AMP for Endpoints does not use regular expressions to block files based on hashes. It uses exact SHA-256 hash matching for custom detections. Regular expressions are not applicable here.
C. Enable a personal firewall in the infected endpoint:
A personal firewall controls network connections, not file execution. It will not block a malicious file that is already on the endpoint or prevent it from running.
D. Add the hash from the infected endpoint to the network block list:
A "network block list" is used to block IP addresses, domains, or URLs at the network level (e.g., on a firewall), not to block file execution on an endpoint. To block a file by hash, you must use the Endpoint custom detection list.
Reference
Cisco Documentation: "Cisco AMP for Endpoints User Guide" – Section on Simple Custom Detections, which explains how to add SHA-256 hashes to block, quarantine, or delete specific files across the organization.
An engineer must configure a Cisco FMC dashboard in a child domain. Which action must be taken so that the dashboard is visible to the parent domain?
A. Add a separate tab
B. Adjust policy inheritance settings
C. Add a separate widget
D. Create a copy of the dashboard
Explanation
In a Cisco Firepower Management Center (FMC) multi-domain deployment, domains are organized in a hierarchical structure (parent and child domains). A dashboard created in a child domain is private to that domain and is not automatically visible to the parent domain or sibling domains.
To make the dashboard visible in the parent domain, the engineer must create a copy of the dashboard. When copying the dashboard, FMC allows you to select the target domain (in this case, the parent domain) to where the copy will be placed. Once copied to the parent domain, the dashboard becomes available for users assigned to that domain.
Why the Other Options Are Incorrect
A. Add a separate tab:
Adding a tab to a dashboard only changes its layout within the child domain; it does not change the domain visibility of the dashboard itself.
B. Adjust policy inheritance settings:
Policy inheritance controls how policies (like Access Control or Intrusion policies) propagate from parent to child domains. It does not control dashboard visibility.
C. Add a separate widget:
Adding widgets customizes the dashboard's content within its current domain but does not move or share the dashboard to a parent domain.
Reference
Cisco Documentation: "Cisco Firepower Management Center Configuration Guide" – Section on Dashboard Management in Multiple Domains, which states that dashboards are domain-specific and must be copied to another domain (e.g., parent domain) to be visible there.
| Page 9 out of 35 Pages |
| 4567891011121314 |
| 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.