All practice questions

2237 questions

Question 841Question

A network engineer is executing a scheduled operating system software update on a core managed switch equipped with dual flash memory banks (Bank 0 and Bank 1). The switch currently executes its operational firmware from Bank 0. To follow software maintenance best practices for risk mitigation and rapid rollback capability, which of the following procedures should the engineer execute?

Show answer & explanation

Answer: Upload the new software image into Bank 1, update the startup boot environment variable to target Bank 1, and preserve the active software image in Bank 0.

Answer

Uploading the updated software image into Bank 1, setting the boot system configuration to point to Bank 1, and keeping the proven operational software in Bank 0 represents the correct operational maintenance procedure.
Utilizing dual flash memory banks allows network engineers to perform non-destructive software updates. By writing the new software image to the alternate bank (Bank 1) and updating the boot configuration parameters while leaving the known-working image untouched on Bank 0, the engineer retains an immediate, verified recovery option if the new software image experiences boot loops, memory corruptions, or feature regressions.

Step-by-Step Solution

1
Transfer the validated software patch image to the secondary, non-active flash storage partition (Bank 1).
The new firmware file is stored locally on the switch without altering the currently running operating system.
Staging the image in secondary storage preserves the running software image in primary storage.
2
Modify the startup configuration system boot path variable to point to the newly written image on Bank 1.
The switch configuration instructs the bootloader to read the updated software binary upon next system reload.
Explicitly updating the boot variable directs the control plane to initialize the new version.
3
Reboot the switch during the designated maintenance window while leaving Bank 0 intact.
The device boots into the updated operating system version while maintaining Bank 0 as an instantaneous fall-back target.
Preserving the previous image in Bank 0 ensures a instant rollback procedure can be executed if post-patch sanity checks fail.

Key Concept

Dual-Bank Flash Firmware Maintenance and Rollback Strategy
Question 842Question

A network security administrator needs to implement a security solution that continuously monitors network traffic and actively drops malicious packets in real time before they can reach critical application servers. Which device type and deployment configuration best fulfills these requirements?

Show answer & explanation

Answer: A Network Intrusion Prevention System (NIPS) deployed inline (in-band) within the network traffic flow.

Answer

A Network Intrusion Prevention System (NIPS) deployed inline (in-band) within the network traffic flow.
A Network Intrusion Prevention System (NIPS) installed inline (in-band) processes all network traffic passing through its interfaces. This placement allows the appliance to analyze packet payloads against threat signatures or anomalies and immediately drop malicious packets before they reach target servers.

Step-by-Step Solution

1
Analyze the operational requirement for active prevention.
The scenario requires stopping malicious packets in real time before they arrive at application servers, which demands a prevention system (IPS) rather than a detection-only system (IDS).
Detection systems (IDS) only generate alerts or passive logs after traffic passes.
2
Evaluate network placement topology (inline vs out-of-band).
Inline (in-band) placement positions the security appliance directly between network segments so all traffic must traverse the device.
Out-of-band topologies receive duplicate copies of traffic from TAP or SPAN ports, making inline packet dropping impossible.

Key Concept

Inline NIPS Deployment vs. Passive NIDS Placement
Estimated Time:1m 15s
Question 843Question

A network security architect is reviewing enterprise controls to align with core security principles across a hybrid multi-cloud environment. Match each technical security mechanism to the primary security principle of the CIA Triad or expanded core concepts it directly fulfills.

Click a left item, then click its matching right item

Items

Implementation of HMAC-SHA256 digests generated using a shared secret for all internal API transaction payloads
Deployment of active-active redundant firewalls across geographically dispersed data centers with automated BGP health checks and route failure propagation
Enforcement of Ephemeral Diffie-Hellman (ECDHE) key exchange within TLS 1.3 session configurations
Requiring developers to sign code commits using asymmetric private keys linked to identity-verified X.509 certificates and cryptographically timestamped by a trusted RFC 3161 authority

Matches

Show answer & explanation

Answer

HMAC-SHA256 payload digests pair with Integrity; Redundant BGP-monitored active-active firewalls pair with Availability; ECDHE key exchange pairs with Confidentiality (PFS); Asymmetrically signed code commits with RFC 3161 timestamps pair with Non-repudiation.
Each security control aligns precisely with its corresponding security principle: HMAC guarantees integrity via tamper detection; dual-homed redundant firewalls guarantee availability through fault tolerance; ephemeral key exchange guarantees confidentiality via forward secrecy; and timestamped asymmetric signatures establish non-repudiation through proof of origin.

Step-by-Step Solution

1
Analyze the technical control in left item 1 (HMAC-SHA256 payload digests).
HMAC produces a keyed cryptographic hash value.
Hashing protects data against unauthorized tampering, which directly maps to the Integrity pillar.
2
Analyze the technical control in left item 2 (Active-active redundant firewalls with automated BGP health checks).
High availability and rapid fault failover infrastructure.
Eliminating single points of failure ensures continuous operational uptime, which maps directly to Availability.
3
Analyze the technical control in left item 3 (Ephemeral Diffie-Hellman key exchange).
Provides Perfect Forward Secrecy by using disposable per-session keys.
Preventing unauthorized decryption of intercepted traffic guarantees data secrecy over time, mapping directly to Confidentiality.
4
Analyze the technical control in left item 4 (Asymmetric private key code signing with RFC 3161 timestamps).
Binds author identity securely to specific code states at precise times.
Prevents the author from denying authorship or claiming modification occurred later, establishing Non-repudiation.

Key Concept

Core Information Security Principles (CIA Triad & Non-repudiation)
Question 844Question

A network administrator configures an inbound extended Access Control List (ACL) on a router interface (GigabitEthernet0/0) to allow internal workstations on subnet 172.16.10.0/24 to browse secure external websites and perform domain name resolution. The applied ACL rules are evaluated top-down as follows:

LineActionProtocolSource IP / WildcardDestination IPDestination Port
10permittcp172.16.10.0 0.0.0.255anyeq 443
20permitudp172.16.10.0 0.0.0.255host 8.8.8.8eq 53

Although outbound TCP SYN packets sent to external Web servers successfully pass through the router interface, internal clients report that HTTPS web pages fail to load and connections instantly time out. Outbound interface NAT and default routing are verified to be fully operational.

Which technical requirement of stateless access control filtering explains why these HTTPS connections fail to establish?

Show answer & explanation

Answer: Stateless ACLs do not track TCP connection state, so return traffic from external servers targeting random ephemeral client ports is blocked by the implicit deny rule on the return path unless explicitly permitted.

Answer

Stateless ACLs do not maintain connection state tables. Consequently, return traffic originating from external servers with source port 443 directed toward high-numbered client ephemeral ports is dropped by the default implicit deny unless return rules or stateful filtering (such as reflexive ACLs or stateful firewalls) are enabled.
Standard router Access Control Lists (ACLs) are stateless, meaning they evaluate each packet in isolation without keeping track of TCP session states. While rule 10 permits outbound TCP SYN packets destined for port 443, the returning TCP SYN-ACK packets sent from port 443 to the client's randomly generated ephemeral port do not match rule 10 (which checks destination port 443). Without a return ACL entry allowing established connections or a stateful firewall mechanism, the return traffic is dropped by the implicit deny all rule at the end of the ACL.

Step-by-Step Solution

1
Analyze the operational behavior of standard extended ACLs
Standard router ACLs are stateless filters that examine IP and transport layer headers of individual packets independently without tracking session states.
Understanding stateless evaluation is required to diagnose directionality issues in ACL traffic flows.
2
Trace the TCP three-way handshake flow for HTTPS (TCP 443)
An internal client (e.g., 172.16.10.15:49152) sends a SYN packet to an external server (e.g., 93.184.216.34:443). Rule 10 permits this packet outbound through GigabitEthernet0/0.
Outbound traffic matches source subnet 172.16.10.0/24 and destination port 443.
3
Evaluate the return SYN-ACK packet flow from the external server back to the client
The server sends a SYN-ACK packet with source IP 93.184.216.34 (port 443) and destination IP 172.16.10.15 (port 49152). When entering an interface or returning, this packet does not match rule 10 (which expects destination port 443, not source port 443).
Because stateless ACLs do not automatically allow return packets matching established sessions, the return SYN-ACK hits the implicit deny rule and is dropped.

Key Concept

Stateless vs. Stateful Filtering and Return Traffic Evaluation in ACLs
Estimated Time:2m 0s
Question 845Question

An enterprise network administrator maintains a disaster recovery plan for an active database server. The backup schedule performs a full backup every Sunday at 01:00, daily differential backups every evening at 23:00 (Monday through Saturday), and incremental transaction log backups every two hours between 08:00 and 18:00 daily. On Thursday at 15:30, a primary storage failure occurs. Which sequence of backup sets must be restored to recover the server to its 14:00 Thursday point-in-time state with the fewest restoration operations?

Show answer & explanation

Answer: The Sunday full backup, the Wednesday differential backup, and the Thursday 08:00, 10:00, 12:00, and 14:00 incremental backups in chronological order

Answer

Restoring the Sunday full backup, the Wednesday differential backup, and the sequential Thursday incremental backups (08:00, 10:00, 12:00, and 14:00) provides the fastest, complete point-in-time recovery.
To achieve a point-in-time restore with the minimum number of steps, the restoration process begins with the last full backup (Sunday). The latest differential backup (Wednesday at 23:00) is applied next, which rolls all data forward to Wednesday night in one operation, superseding Monday and Tuesday differentials. Finally, because incremental backups record only changes since the last backup of any type, each incremental backup on Thursday (08:00, 10:00, 12:00, and 14:00) must be applied sequentially to recover up to 14:00.

Step-by-Step Solution

1
Restore the baseline full backup
Establishes the initial baseline full system image state from Sunday at 01:00.
All recovery processes require an initial full backup baseline before applying differential or incremental changes.
2
Restore the latest differential backup prior to the outage
Applies all cumulative data changes made between Sunday 01:00 and Wednesday 23:00 in a single step.
Differential backups capture all changes since the last full backup, rendering earlier differential backups (Monday and Tuesday) obsolete for restoration.
3
Restore all incremental backups created after the latest differential backup up to the recovery target time
Applies Thursday's 08:00, 10:00, 12:00, and 14:00 incremental backups in sequential order.
Incremental backups contain only data changed since the previous backup event. Each incremental backup depends on the preceding incremental file.

Key Concept

Disaster recovery backup restoration sequences using full, differential, and incremental backup types
Question 846Question

An enterprise network engineer is analyzing complex network performance anomalies across different application types and operational environments. Match each observed performance symptom or monitoring vulnerability to its corresponding performance metric, protocol mechanism, or diagnostic technique.

Click a left item, then click its matching right item

Items

VoIP call quality degradation characterized by distorted audio and out-of-order packet arrival across a WAN link despite low average bandwidth utilization.
A sudden spike in core router CPU usage accompanied by unauthorized configuration changes following cleartext network monitoring traffic interception.
Intermittent database transaction drops during peak hours due to transient switch port buffer congestion that does not show up on standard 5-minute average bandwidth polling.
Real-time video conferencing quality degradation caused by significant fluctuations in packet inter-arrival times across asymmetric routing paths.

Matches

Show answer & explanation

Answer

The symptoms map to their corresponding performance monitoring metrics as follows: VoIP call degradation correlates with Jitter/MOS tracking via IP SLA probes; cleartext monitoring vulnerability correlates with SNMPv3 authPriv configuration; hidden buffer overflow drops correlate with microburst detection via high-frequency queue sampling; and video inter-arrival fluctuations correlate with packet delay variation and unidirectional latency analysis.
Each pair correctly matches a specific network performance or security monitoring challenge to its specialized diagnostic tool or metric: IP SLA probes evaluate voice jitter and MOS scores; SNMPv3 with authPriv resolves unencrypted monitoring vulnerabilities; high-frequency queue monitoring exposes microburst buffer drops; and hardware-timestamped packet analysis measures unidirectional latency and inter-arrival jitter across asymmetric paths.

Step-by-Step Solution

1
Analyze real-time voice traffic degradation symptoms
Identify that low average bandwidth with high voice distortion indicates latency variation (jitter) and out-of-order packets, requiring IP SLA MOS tracking.
Voice codecs are highly sensitive to delay variations and jitter rather than raw throughput.
2
Evaluate monitoring protocol security breach
Determine that unencrypted monitoring allowing unauthorized device configuration modification is caused by SNMPv1/v2c plaintext community strings, which must be mitigated by SNMPv3 authPriv.
SNMPv1 and SNMPv2c transmit credentials in plaintext, enabling attackers to execute unauthorized SET commands.
3
Diagnose sub-second traffic congestion anomalies
Recognize that short burst congestion missed by standard 5-minute SNMP interval polling represents microbursting, requiring high-frequency queue depth sampling.
Standard SNMP polling intervals average out sub-second traffic spikes that overflow port buffers.
4
Assess asymmetric routing effects on video stream timing
Connect inter-arrival timing variations on asymmetric paths to packet delay variation and unidirectional latency measurements.
Asymmetric paths introduce differing delay characteristics in opposing directions, altering packet inter-arrival timing.

Key Concept

Network Performance Metrics, Monitoring Tools, and Baseline Anomaly Analysis
Question 847Question

An enterprise infrastructure uses two Layer 3 switches, Router-Alpha and Router-Beta, configured with Hot Standby Router Protocol (HSRP) to provide default gateway redundancy for hosts on VLAN 50 (172.16.50.0/24172.16.50.0/24). Router-Alpha is intended to be the primary gateway and is configured with an HSRP priority of 120120, preemption enabled, and WAN interface tracking with a priority decrement of 3030. Router-Beta is configured with an HSRP priority of 100100. During an unexpected WAN uplink disruption on Router-Alpha, its tracked interface goes down, successfully reducing its advertised priority to 9090. However, network monitoring reveals that host traffic on VLAN 50 continues routing through Router-Alpha's degraded path instead of transitioning to Router-Beta. Which configuration deficiency on Router-Beta prevents it from assuming the Active gateway role?

Show answer & explanation

Answer: Router-Beta does not have preemption enabled in its HSRP configuration, causing it to remain in Standby state as long as Router-Alpha continues transmitting hello packets.

Answer

Router-Beta does not have preemption enabled in its HSRP configuration, causing it to remain in Standby state as long as Router-Alpha continues transmitting hello packets.
In First Hop Redundancy Protocols such as HSRP and VRRP, interface tracking decrements a primary router's priority when a monitored uplink fails. If the primary router remains online, it continues broadcasting hello frames with its newly reduced priority. For a backup or standby router to seize the Active role from an operational router with a lower priority, preemption MUST be enabled on the backup/standby router. Without preemption on the standby router, it will only become Active if the primary router completely stops transmitting hello packets.

Step-by-Step Solution

1
Analyze initial HSRP priorities and roles.
Router-Alpha has priority 120120 (Active) and Router-Beta has priority 100100 (Standby).
The router with the higher priority value wins the HSRP Active election.
2
Evaluate the effect of interface tracking when the WAN uplink fails.
Router-Alpha's priority drops by 3030, resulting in a new priority of 12030=90120 - 30 = 90.
Interface tracking decrements the active router's priority value upon link failure to trigger failover.
3
Determine HSRP preemption behavior on the Standby router.
Router-Beta's priority (100100) is now higher than Router-Alpha's priority (9090), but Router-Alpha is still sending HSRP hello messages.
Without preemption enabled on Router-Beta, a Standby router will never forcibly take over the Active role from an operational Active router, even if the Active router's priority drops below that of the Standby router.

Key Concept

First Hop Redundancy Protocol (FHRP) Priority, Preemption, and Interface Tracking
Question 848Question

Prior to installing a minor software patch on an enterprise edge router, a network engineer creates a backup of the current operating configuration and tests the update in an isolated environment. What is the primary purpose of performing these pre-deployment actions?

Show answer & explanation

Answer: To verify system stability and ensure a reliable rollback path if the patch causes unexpected issues

Answer

To verify system stability and ensure a reliable rollback path if the patch causes unexpected issues.
Performing lab testing and backing up baseline system configurations ensure that potential software bugs are discovered safely and that the device can be rapidly restored to its prior state if issues arise during maintenance.

Step-by-Step Solution

1
Identify the purpose of pre-deployment patch management activities
Recognize that configuration backups provide a recovery point and staging environments allow risk-free testing.
Applying unvalidated software updates directly to live systems risks downtime and operational disruption.
2
Evaluate the choices against best practices for network maintenance
Determining that backing up configurations and pre-testing updates directly supports risk mitigation and system recovery.
If an update corrupts device operational behavior, the saved backup and validated procedure enable immediate recovery.

Key Concept

Patch Staging and Baseline Backups
Question 849Question

An enterprise network design requires deploying redundant layer 2 and layer 3 mechanisms across perimeter firewalls, default gateways, and switch uplinks. Match each high availability protocol on the left with its corresponding operational specification or MAC/header characteristic on the right.

Click a left item, then click its matching right item

Items

Hot Standby Router Protocol (HSRP)
Virtual Router Redundancy Protocol (VRRP)
Link Aggregation Control Protocol (LACP)
Common Address Redundancy Protocol (CARP)

Matches

Show answer & explanation

Answer

Hot Standby Router Protocol (HSRP) matches with Cisco-proprietary gateway redundancy protocol using Active/Standby roles and virtual MAC address prefix 0000.0c07.acXX; Virtual Router Redundancy Protocol (VRRP) matches with Open-standard gateway redundancy protocol using Master/Backup roles and virtual MAC address prefix 0000.5e00.01XX; Link Aggregation Control Protocol (LACP) matches with IEEE 802.3ad standard protocol that dynamically bundles physical ethernet ports into a single logical interface; Common Address Redundancy Protocol (CARP) matches with BSD-derived open-source protocol allowing multiple hosts on a segment to share an IP address using cryptographic authentication.
Each protocol is accurately matched to its design standard, MAC address structure, and operational role: HSRP is Cisco-proprietary using Active/Standby states (0000.0c07.acXX); VRRP is an open standard using Master/Backup states (0000.5e00.01XX); LACP is the IEEE 802.3ad multi-link trunking standard; and CARP is the open-source BSD protocol with cryptographic authentication.

Step-by-Step Solution

1
Identify First-Hop Redundancy Protocols (FHRP) and distinguish proprietary implementations from open standards.
HSRP is identified as Cisco-proprietary (Active/Standby, MAC prefix 0000.0c07.acXX), whereas VRRP is an open IETF standard (Master/Backup, MAC prefix 0000.5e00.01XX).
MAC address ranges and operational terminology are key differentiators between HSRP and VRRP.
2
Identify link-layer aggregation protocols.
LACP matches IEEE 802.3ad dynamic bundling for interface redundancy.
LACP operates at Layer 2 to aggregate physical switch ports rather than creating virtual gateway IP addresses at Layer 3.
3
Identify specialized open-source security-focused gateway redundancy protocols.
CARP matches the BSD-derived open-source protocol offering cryptographic authentication.
CARP was explicitly developed within BSD to provide secure IP sharing without patent encumbrance.

Key Concept

High Availability and Gateway/Link Redundancy Protocols
Question 850Question

A network administrator is configuring Virtual Router Redundancy Protocol (VRRP) across two routers to provide first-hop redundancy for a local subnet. To ensure that end-user workstations seamlessly switch traffic to the standby router in the event of a primary router failure, which IP address should be configured as the default gateway on the workstations?

Show answer & explanation

Answer: The shared Virtual IP (VIP) address assigned to the VRRP redundancy group

Answer

The shared Virtual IP (VIP) address assigned to the VRRP redundancy group should be configured as the default gateway on client workstations.
Configuring the shared Virtual IP (VIP) address as the default gateway ensures that host devices send outbound packets to the virtual router instance. When the primary router fails, the backup router automatically assumes control of the Virtual IP address, maintaining uninterrupted network communication for hosts.

Step-by-Step Solution

1
Identify the purpose of First Hop Redundancy Protocols (FHRP) such as VRRP.
FHRP protocols present multiple physical routers as a single logical router sharing a Virtual IP (VIP) address and Virtual MAC address.
This logical representation allows hosts to maintain a constant gateway target regardless of which physical router is actively forwarding traffic.
2
Determine the correct workstation gateway assignment.
Workstations must be configured with the shared Virtual IP address as their default gateway.
If the active router fails, the VRRP master role transitions to the backup router, which assumes responsibility for answering ARP requests for the Virtual IP address without requiring host configuration changes.

Key Concept

Virtual Router Redundancy Protocol (VRRP) Virtual IP Configuration
Question 851Question

A network security engineer is auditing the logging infrastructure of an enterprise network. The engineer discovers that network infrastructure devices transmit sensitive audit logs to a central SIEM server over an unencrypted channel, and critical log messages are lost during peak traffic congestion. Which protocol configuration change will ensure encrypted transport and guaranteed delivery of the audit logs?

Show answer & explanation

Answer: Configure Syslog forwarding to use TLS over TCP port 6514.

Answer

Configure Syslog forwarding to use TLS over TCP port 6514.
Configuring Syslog to use TLS over TCP port 6514 ensures connection-oriented transport with delivery guarantees (via TCP acknowledgments and retransmissions) and privacy (via TLS encryption).

Step-by-Step Solution

1
Identify transport reliability requirements
Recognize that connection-oriented TCP is required to prevent packet loss and guarantee log delivery during network congestion.
UDP is connectionless and drops packets when network links are saturated.
2
Identify security and encryption requirements
Determine that TLS-based encapsulation is necessary to protect sensitive audit logs in transit.
Standard Syslog over UDP port 514 sends log entries in unencrypted cleartext.
3
Select standard protocol and port specification
Select Syslog over TLS running on TCP port 6514.
RFC 5425 establishes TCP port 6514 as the standard port for TLS-encrypted Syslog transport.

Key Concept

Secure Syslog Transport (Syslog over TLS / TCP 6514)
Question 852Question

A network security architect must implement centralized AAA management for network administrators executing commands on enterprise routers across loss-prone WAN links. The solution must support per-command authorization policy enforcement, encrypt the entire packet payload during transit, and use a reliable connection-oriented transport protocol to guarantee delivery of accounting records. Which protocol and transport combination should the architect deploy?

Show answer & explanation

Answer: TACACS+ utilizing TCP port 49

Answer

TACACS+ utilizing TCP port 49
TACACS+ (Terminal Access Controller Access-Control System Plus) fully decouples the AAA functions, enabling separate per-command authorization checks for router administration. It encrypts the complete packet payload (except the standard header) and uses connection-oriented TCP on port 49, satisfying the WAN reliability and accounting delivery requirements.

Step-by-Step Solution

1
Analyze access control and authorization requirements
Identified requirement for granular per-command CLI authorization.
TACACS+ separates authorization from authentication, allowing distinct CLI command permission checks, whereas RADIUS couples them together.
2
Evaluate payload encryption requirements
Identified requirement for full packet payload encryption.
TACACS+ encrypts the entire payload body of the packet, while RADIUS only encrypts the password attribute in transit.
3
Determine transport protocol and port specifications
Selected TCP over port 49.
TACACS+ runs natively on connection-oriented TCP port 49 to provide reliable transmission over lossy WAN links.

Key Concept

Decoupled AAA architecture, payload encryption scope, and transport protocol characteristics of TACACS+ versus RADIUS.
Question 853Question

Following a workstation compromise, an enterprise security team observes that an internal database server receives encrypted command-and-control traffic, accompanied by unauthorized local process injection and file integrity alterations. The existing network-based IDS connected via a switch SPAN port failed to decrypt the payload and was structurally incapable of stopping the local system modifications due to its passive out-of-band placement. To actively block unauthorized system calls, memory manipulation, and malicious file modifications directly on the server host, which security technology should be deployed?

Show answer & explanation

Answer: Host-based Intrusion Prevention System (HIPS)

Answer

Host-based Intrusion Prevention System (HIPS) should be deployed because it runs locally on the host to monitor and actively block unauthorized system calls, file modifications, and process injections.
A Host-based Intrusion Prevention System (HIPS) is installed directly on host endpoints (such as servers). Because it runs within the operating system, it has complete visibility into decrypted data, file system alterations, registry modifications, and kernel/system calls. Furthermore, as a prevention system, it actively interrupts and blocks unauthorized or anomalous process execution and system calls before damage occurs.

Step-by-Step Solution

1
Analyze the threat vectors and monitoring requirements described in the scenario.
The scenario requires protection against host-level threats (process injection, local system calls, memory modification) and encrypted traffic that out-of-band network sensors cannot inspect or block.
Identifying whether the vulnerability/attack surface is network-centric or endpoint-centric dictates the correct system architecture.
2
Evaluate network-based vs host-based security mechanisms.
Network-based systems (NIDS/NIPS) process network traffic in transit. Host-based systems (HIDS/HIPS) process host activity after network decryption, inspecting internal operating system calls and file systems.
Host-level processes and payload contents encrypted in transit are visible only at the host endpoint.
3
Differentiate between passive detection and active prevention capabilities.
Intrusion Detection Systems (IDS) detect and alert passively, whereas Intrusion Prevention Systems (IPS) sit inline relative to the activity and actively block malicious actions.
The requirement specifically demands actively blocking local system modifications, necessitating an inline prevention technology.

Key Concept

Host-based Intrusion Prevention System (HIPS) vs. Network-based Security Placement
Estimated Time:2m 0s
Question 854Question

A network engineer is troubleshooting log loss during periods of high link congestion. System logs sent from edge routers to a centralized collector are currently dropped during traffic spikes. The compliance team mandates that log transmission across the WAN link must guarantee delivery, avoid loss under network congestion, and encrypt log payloads in transit. Which configuration change best satisfies all technical and compliance requirements?

Show answer & explanation

Answer: Configure Syslog to use TCP port 6514 with TLS encryption enabled.

Answer

Configure Syslog to use TCP port 6514 with TLS encryption enabled.
Configuring Syslog over TLS on TCP port 6514 satisfies both delivery assurance and confidentiality requirements. TCP provides connection-oriented transmission with error recovery and flow control to prevent packet loss during congestion, while TLS encrypts event data across untrusted network paths.

Step-by-Step Solution

1
Identify transport reliability requirements
UDP (port 514) is connectionless and drops packets during buffer saturation, whereas TCP provides flow control and retransmission to guarantee log delivery under congestion.
The requirement explicitly demands preventing log loss during periods of network congestion.
2
Identify encryption requirements for audit logs
Standard Syslog over UDP port 514 is unencrypted. Syslog over TLS utilizes TCP port 6514 to encrypt log messages in transit across untrusted links.
Compliance mandates protecting log contents against eavesdropping.
3
Evaluate protocol security models
Syslog over TLS (TCP 6514) directly addresses both transport reliability and cryptographic protection requirements.
Alternative configurations using UDP or insecure SNMP versions (SNMPv2c) fail reliability or confidentiality criteria.

Key Concept

Syslog Transport and Encryption (TCP/6514 TLS)
Estimated Time:1m 30s
Question 855Question

An enterprise organization requires a disaster recovery strategy for its mission-critical database cluster across dual data centers separated by 120 km. The business demands a Recovery Point Objective (RPO) of absolute zero data loss and a Recovery Time Objective (RTO) under 5 minutes. Which of the following technical controls and redundancy configurations MUST be combined to satisfy these stringent business continuity metrics? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Synchronous storage block-level replication between active-active multi-site cluster nodes; Continuous Data Protection (CDP) paired with automated BGP route advertisement or DNS failover triggers

Answer

Meeting an RPO of zero requires synchronous replication or Continuous Data Protection (CDP) so no committed transaction is lost. Achieving an RTO under 5 minutes necessitates automated active-active cluster failover or dynamic BGP/DNS redirection without manual intervention.
Synchronous block-level storage replication and Continuous Data Protection (CDP) ensure every transaction is committed at the remote site before completion, guaranteeing zero data loss (RPO = 0). Pairing these with automated failover mechanisms such as active-active clustering or dynamic BGP/DNS updates enables service restoration within minutes, meeting the RTO threshold.

Step-by-Step Solution

1
Analyze RPO requirements
RPO = 0 mandates real-time write confirmation across sites (synchronous replication or Continuous Data Protection). Asynchronous, log shipping, and periodic backup schedules all introduce potential data loss windows.
Periodic or asynchronous operations allow data modifications to exist exclusively at the primary site prior to replication.
2
Analyze RTO requirements
RTO < 5 minutes requires fully automated failover mechanisms (active-active clustering or automated network route/DNS redirection).
Manual intervention, restoring backup files, or provisioning cold site infrastructure exceeds the 5-minute threshold.
3
Select matching technologies
Synchronous block replication with active-active clustering and CDP with automated network redirection satisfy both RPO=0 and RTO < 5 min.
Both selected technologies provide real-time data persistence and automated failover.

Key Concept

RPO and RTO Trade-off Analysis in High Availability and Disaster Recovery Design
Question 856Question

A company is updating its perimeter network architecture to defend against automated exploit attacks targeted at public-facing application servers. The security strategy requires a device positioned directly in the traffic flow that can inspect packet payloads in real time and automatically drop malicious frames before they cross into the internal segment. Which security appliance deployment best satisfies these active mitigation requirements?

Show answer & explanation

Answer: A Network Intrusion Prevention System (NIPS) deployed inline between the perimeter router and the internal web network

Answer

A Network Intrusion Prevention System (NIPS) deployed inline between the perimeter router and the internal web network
Deploying a Network Intrusion Prevention System inline places the device directly inside the network traffic path (in-band). This enables the system to perform deep packet inspection on passing traffic and immediately block or drop malicious packets before they reach internal application servers.

Step-by-Step Solution

1
Identify the operational requirement specified in the scenario
The scenario demands an active prevention solution placed directly in the traffic path to inspect payloads and drop malicious packets immediately.
Active packet dropping requires in-band (inline) placement so traffic must pass through the device.
2
Evaluate the distinction between passive detection and active inline prevention
NIDS operates out-of-band via SPAN/TAP ports (passive monitoring), whereas NIPS operates inline (active prevention).
Only an inline appliance can drop packets mid-stream before they arrive at host destinations.
3
Select the matching deployment model
Deploying a Network Intrusion Prevention System (NIPS) inline between the perimeter router and internal segment satisfies all requirements.
Inline NIPS combines deep packet payload inspection with real-time active traffic blocking.

Key Concept

Inline NIPS vs. Passive NIDS Deployment
Estimated Time:1m 15s
Question 857Question

During a security compliance audit of an enterprise network, an administrator is tasked with remediating an auditing finding regarding switch telemetry monitoring. The audit report indicates that device monitoring traps sent across the management VLAN are vulnerable to packet sniffing because authentication credentials and telemetry payloads are transmitted without encryption. Which SNMP configuration mode should the administrator deploy to satisfy the audit requirement for both cryptographic user authentication and payload encryption?

Show answer & explanation

Answer: SNMPv3 configured with authPriv

Answer

SNMPv3 configured with authPriv is the correct choice as it enforces both cryptographic authentication and data payload encryption.
SNMPv3 with the authPriv (Authentication and Privacy) security level uses cryptographic algorithms such as SHA/MD5 for message authentication and hashing, and AES/DES for payload encryption. This ensures both integrity/authenticity of the monitoring host and privacy of transmitted telemetry across untrusted network segments.

Step-by-Step Solution

1
Analyze the audit compliance requirement
Identified the need for both credential authentication and payload confidentiality (encryption) for network monitoring telemetry.
The audit finding specifically highlighted unencrypted payloads and cleartext credential vulnerability.
2
Evaluate SNMP version security capabilities
Determined that SNMPv1 and SNMPv2c lack native cryptographic encryption, requiring SNMPv3.
Only SNMPv3 introduces user-based security models (USM) with selectable security levels.
3
Select the appropriate SNMPv3 security level
Selected authPriv (Authentication and Privacy).
authNoPriv adds authentication without encryption, whereas authPriv enforces both authentication and privacy/encryption.

Key Concept

SNMPv3 Security Levels and Telemetry Auditing
Estimated Time:1m 0s
Question 858Question

A network engineer is configuring Variable Length Subnet Masking (VLSM) within the assigned block 10.200.16.0/2010.200.16.0/20. The first subnet (Subnet A) must be allocated from the start of the block to support at least 600600 usable host interfaces. The second subnet (Subnet B) must be provisioned immediately following the address space allocated to Subnet A to accommodate at least 250250 usable host interfaces. What is the decimal value of the third octet in the network ID of Subnet B?

Show answer & explanation

Answer: 20

Answer

The decimal value of the third octet in the network ID of Subnet B is 20.
To support at least 600 usable hosts in Subnet A, 10 host bits are required (2102=10222^{10} - 2 = 1022 usable addresses), establishing a /22 subnet mask. With a /22 prefix starting at 10.200.16.010.200.16.0, the block spans 4 values in the third octet (16,17,18,1916, 17, 18, 19), covering 10.200.16.010.200.16.0 through 10.200.19.25510.200.19.255. The next available network address for Subnet B starts immediately at 10.200.20.010.200.20.0. Thus, the third octet decimal value is 20.

Step-by-Step Solution

1
Determine the required prefix length for Subnet A.
Subnet A requires a /22 prefix length.
Subnet A needs at least 600 usable host IPs. Since 292=5102^9 - 2 = 510 is insufficient, 10 host bits are required (2102=10222^{10} - 2 = 1022). The prefix length is 3210=2232 - 10 = 22.
2
Calculate the block size and address range for Subnet A.
Subnet A spans 10.200.16.010.200.16.0 to 10.200.19.25510.200.19.255.
A /22 prefix has a block size of 2(3222)=10242^{(32-22)} = 1024 total addresses (44 block increments in the third octet). Starting at 10.200.16.010.200.16.0, the subnet ends at 10.200.19.25510.200.19.255.
3
Find the starting network ID for Subnet B.
Subnet B begins at 10.200.20.010.200.20.0.
Subnet B must be allocated immediately after the broadcast address of Subnet A (10.200.19.25510.200.19.255).
4
Extract the third octet value.
20
In the IPv4 address 10.200.20.010.200.20.0, the third octet is 20.

Key Concept

Variable Length Subnet Masking (VLSM) block size calculation and sequential subnet allocation.
Question 859Question

A network security analyst is investigating a compromised corporate subnet where users attempting to access internal file servers are periodically redirected to an unauthorized external server capturing credentials. A packet capture analysis on the local segment reveals two distinct operational anomalies:
1. Unsolicited, continuous ARP response frames broadcast across the segment, binding the subnet default gateway's IP address to an unrecognized host's MAC address.
2. Injected response packets intercepting local recursive name resolution requests and supplying spoofed IP addresses for internal domain names.

Which of the following attack vectors are directly being executed in this enterprise incident? (Select TWO)

Select all that apply

Show answer & explanation

Answer: ARP Poisoning (Spoofing) to establish a Layer 2 On-path (Man-in-the-Middle) position by altering local host neighbor caches; DNS Poisoning (Spoofing) to compromise name-to-IP resolution and redirect domain lookup queries to unauthorized IP addresses

Answer

The two attack vectors actively being executed are ARP Poisoning (Spoofing) and DNS Poisoning (Spoofing).
The scenario describes two distinct malicious actions: local ARP table corruption via unsolicited ARP responses (ARP Poisoning) to position the attacker as an On-path intermediary, and the injection of fraudulent DNS resolution answers (DNS Poisoning) to redirect users to unauthorized IP destinations.

Step-by-Step Solution

1
Analyze anomaly #1: Unsolicited ARP response frames mapping gateway IP to an unknown MAC.
Identified as ARP Poisoning/Spoofing. Gratuitous ARP frames poison local ARP caches, causing hosts on the broadcast domain to send gateway-bound packets directly to the attacker's Layer 2 MAC address.
ARP lacks authentication mechanisms, allowing spoofed replies to overwrite legitimate IP-to-MAC resolution tables.
2
Analyze anomaly #2: Injected response packets altering local name resolution output.
Identified as DNS Poisoning/Spoofing. Fake DNS replies overwrite cache or resolution entries to direct hostname lookups to malicious destination IPs.
DNS resolution manipulation specifically targets domain name translation to divert application traffic.
3
Evaluate remaining options against observed packet anomalies.
VLAN Hopping and Port 23 Downgrade do not match ARP cache corruption or DNS response injection symptoms.
VLAN hopping exploits trunking configuration tagging, and Telnet on port 23 is unrelated to name resolution or address resolution.

Key Concept

Common Network Attack Types and Vectors (ARP Poisoning and DNS Spoofing)
Estimated Time:3m 0s
Question 860Question

A network security administrator is transitioning core switch infrastructure management from a RADIUS solution to TACACS+. When auditing protocol behavior and firewall traffic rules for TACACS+, which of the following operational characteristics accurately describe TACACS+ compared to RADIUS? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Encrypts the entire body of the packet rather than concealing only the user password field.; Utilizes connection-oriented TCP port 49 for communication between the AAA client and server.

Answer

TACACS+ encrypts the entire body of the packet rather than concealing only the user password field, and it utilizes connection-oriented TCP port 49 for communication between the AAA client and server.
TACACS+ provides full-payload encryption beyond the protocol header and relies on TCP port 49 for reliable connection management. This allows network security systems to perform granular per-command authorization over a secure, connection-oriented channel.

Step-by-Step Solution

1
Analyze protocol encryption scope differences between RADIUS and TACACS+.
Identify that TACACS+ encrypts all payload content beyond the basic header, whereas RADIUS encrypts only the password attribute in Access-Request packets.
Security auditing requires determining payload confidentiality boundaries across administrative AAA traffic.
2
Evaluate transport layer protocols and port requirements for TACACS+ traffic rules.
Confirm that TACACS+ relies on TCP port 49, offering reliable connection state monitoring, whereas RADIUS relies on UDP (ports 1812/1813 or legacy 1645/1646).
Firewall access rules must accurately reflect TCP port 49 for TACACS+ client-server communication.
3
Verify AAA architecture modularity distinctions.
Differentiate TACACS+ (decoupled AAA functions allowing per-command authorization) from RADIUS (coupled authentication/authorization).
Eliminate choices that misattribute combined AAA transactions or RADIUS UDP ports to TACACS+.

Key Concept

AAA Framework protocol differences between TACACS+ (TCP 49, full payload encryption, decoupled AAA) and RADIUS (UDP 1812/1813, password-only encryption, combined authentication/authorization).
Estimated Time:2m 0s
PreviousPage 43 / 112Next
All practice questions — CompTIA Network+ | Examkin