Network Security

427 questions

Question 41Question

During a security incident response on subnet 192.168.50.0/24192.168.50.0/24, a network engineer observes that multiple workstations have lost connectivity to internal corporate servers and are transmitting sensitive traffic to an unapproved external address. Packet captures reveal a rapid influx of DHCP DISCOVER and REQUEST messages originating from thousands of randomly generated MAC addresses, which completely exhausts the legitimate DHCP server's IP address pool. Immediately after the pool is depleted, clients receive IP leases containing an unauthorized default gateway IP address broadcast by an unidentified device on the local Layer 2 broadcast domain. Which of the following attack types represents the primary vector used to hijack client traffic?

Show answer & explanation

Answer: A DHCP starvation attack combined with a rogue DHCP server injection

Answer

The attack executed is a DHCP starvation attack combined with a rogue DHCP server injection.
The scenario describes a classic two-stage network attack. First, the adversary floods the network with DHCP requests containing randomized MAC addresses, completely exhausting the legitimate DHCP server's available IP scope (DHCP starvation). Second, an unauthorized device answers subsequent client lease requests by assigning IP configurations that include a malicious default gateway (rogue DHCP server injection), effectively establishing a Man-in-the-Middle (MitM) position.

Step-by-Step Solution

1
Analyze the log signature showing thousands of DISCOVER/REQUEST packets with unique spoofed MAC addresses.
Identify that the legitimate DHCP scope pool on 192.168.50.0/24192.168.50.0/24 was intentionally exhausted (DHCP starvation).
Depleting available IP addresses prevents new or renewing hosts from acquiring legitimate network configurations.
2
Examine the client lease details received immediately after pool exhaustion.
Observe that clients accepted new network configurations, including a malicious default gateway, from an unauthorized device.
Once the legitimate server is starved, a rogue DHCP server can answer client requests faster and assign malicious gateway settings.
3
Correlate the multi-stage behavior to select the corresponding network attack vector.
Confirm that the combination of MAC address flooding and unauthorized lease generation constitutes DHCP starvation and rogue DHCP injection.
This specific multi-step vector relies on Layer 2 broadcasting of UDP port 67/68 traffic to manipulate endpoint routing.

Key Concept

DHCP Starvation and Rogue DHCP Server Injection
Question 42Question

A network technician is configuring an IPsec site-to-site Virtual Private Network (VPN) between two branch offices. Arrange the following steps in the correct order in which an IPsec VPN connection is established between the two gateways.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for establishing an IPsec VPN connection is: 1) Negotiate IKE Phase 1 security parameters, 2) Authenticate peers and perform Diffie-Hellman key exchange to establish the IKE Phase 1 tunnel, 3) Negotiate IKE Phase 2 parameters to establish IPsec Security Associations (SAs), and 4) Encrypt and transmit user data packets across the established IPsec tunnel.
Establishing an IPsec connection requires setting up a secure management channel first via IKE Phase 1 (negotiation followed by authentication and key exchange), then negotiating IPsec SAs in Phase 2, and finally encrypting and forwarding actual user data.

Step-by-Step Solution

1
Identify the initial policy negotiation phase.
Gateways agree on Phase 1 proposal parameters (IKE Phase 1 negotiation).
Both VPN endpoints must agree on encryption and hash algorithms before initiating authentication.
2
Establish the management tunnel.
Diffie-Hellman key exchange completes and creates the ISAKMP/IKE SA tunnel.
Peer authentication and key exchange establish a secure control channel to protect subsequent negotiations.
3
Negotiate parameters for data protection.
IKE Phase 2 creates IPsec Security Associations (SAs).
Phase 2 defines how the actual user payload data will be encapsulated and encrypted (ESP/AH).
4
Begin data transmission.
User data is encrypted and transmitted.
Payload traffic can only pass through once data-plane security associations are fully negotiated and active.

Key Concept

IPsec VPN Tunnel Establishment Process (IKE Phase 1 and Phase 2)
Question 43Question

A network technician is configuring a remote access solution for mobile workers to securely connect to internal enterprise resources. The technical requirements specify that the security protocol suite must operate at the Network layer (Layer 3) of the OSI model to authenticate and encrypt all IP packets passing through the tunnel. Which of the following protocols should the technician implement?

Show answer & explanation

Answer: IPsec

Answer

IPsec is the correct protocol suite because it functions at the OSI Network layer (Layer 3) to authenticate and encrypt all IP packet payloads and headers.
IPsec (Internet Protocol Security) operates natively at Layer 3 (the Network layer) of the OSI model. By running at Layer 3, IPsec can secure and encrypt all upper-layer protocol traffic (such as TCP and UDP) seamlessly without requiring application-specific configurations.

Step-by-Step Solution

1
Identify the OSI layer constraint specified in the prompt requirement.
The target protocol must operate directly at Layer 3 (Network layer).
Layer 3 protocols can encrypt and encapsulate full IP packets regardless of upper-layer applications.
2
Evaluate the listed VPN and remote access protocols against their operating layer.
IPsec operates at Layer 3; TLS operates at Layer 4/7; SSH operates at Layer 7; PPTP encapsulates Layer 2 frames.
Only IPsec meets the exact OSI Layer 3 architectural requirement.

Key Concept

IPsec Layer 3 Operation and Encapsulation
Question 44Question

As part of a wireless security assessment, an engineer must accurately map each IEEE 802.11 cryptographic protocol to its underlying encryption algorithm and message integrity mechanism. Match each protocol on the left to its matching cryptographic pair on the right.

Click a left item, then click its matching right item

Items

GCMP-256
CCMP-128
TKIP
BIP-GMAC-256

Matches

Show answer & explanation

Answer

GCMP-256 matches AES in Galois/Counter Mode (256-bit key). CCMP-128 matches AES in Counter Mode with CBC-MAC (128-bit key). TKIP matches RC4 stream cipher with the Michael algorithm. BIP-GMAC-256 matches Galois Message Authentication Code under 802.11w for broadcast/multicast management frames.
Each protocol correctly pairs with its cryptographic specification: GCMP-256 uses AES in Galois/Counter Mode with 256-bit keys; CCMP-128 uses AES Counter Mode with CBC-MAC; TKIP pairs RC4 with the Michael integrity check algorithm; and BIP-GMAC-256 provides Galois MAC integrity protection for broadcast management frames.

Step-by-Step Solution

1
Identify the cryptographic suite requirements for high-strength WPA3 Enterprise (192-bit mode).
GCMP-256 provides 256-bit authenticated encryption via Galois/Counter Mode.
WPA3 Enterprise 192-bit security relies on GCMP-256 as its primary data protection cipher.
2
Analyze standard IEEE 802.11i baseline encryption (CCMP-128).
CCMP-128 pairs AES in Counter Mode (CTR) for encryption with CBC-MAC for integrity.
This is the mandatory baseline cipher suite for standard WPA2 and WPA3 Personal.
3
Examine legacy protocol primitives for TKIP.
TKIP wraps RC4 encryption with the Michael Message Integrity Check (MIC).
TKIP was created to fix WEP vulnerabilities without requiring new hardware, utilizing RC4 and Michael.
4
Determine the management frame integrity protocol for broadcast traffic.
BIP-GMAC-256 uses Galois MAC to protect group management frames under Protected Management Frames (PMF).
Broadcast Integrity Protocol (BIP) safeguards deauthentication and disassociation broadcast frames from spoofing attacks.

Key Concept

Wireless Cipher Suites and Integrity Mechanisms
Question 45Question

A network administrator is troubleshooting connectivity issues on a router filtering traffic between client workstations on subnet 172.16.20.0/24172.16.20.0/24 and an internal core server on host 10.10.1.5/3210.10.1.5/32. Workstations are unable to resolve domain names using the internal DNS service hosted on 10.10.1.510.10.1.5. The administrator inspects the following IPv4 extended Access Control List (ACL) applied inbound on the workstation interface:

`10 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 53`
`20 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 88`
`30 permit tcp 172.16.20.0 0.0.0.255 host 10.10.1.5 eq 445`

Which of the following best explains why standard DNS queries sent by client workstations to the server are being dropped?

Show answer & explanation

Answer: Standard client DNS lookups primarily use UDP port 53, but rule 10 only permits TCP port 53, causing UDP queries to fall through to the implicit deny rule.

Answer

Standard client DNS lookups primarily use UDP port 53, but rule 10 only permits TCP port 53, causing UDP queries to fall through to the implicit deny rule.
Standard DNS client queries use UDP port 53 for fast, connectionless name lookups. Rule 10 specifies protocol `tcp`, which does not match UDP packets. Unmatched UDP DNS queries pass through lines 10, 20, and 30 without matching, hitting the ACL's mandatory implicit deny rule at the bottom and getting dropped.

Step-by-Step Solution

1
Analyze the protocol requirement for standard DNS queries.
Standard client-to-server DNS name resolution requests are sent using UDP datagrams to port 53 (TCP port 53 is reserved for zone transfers or responses exceeding 512 bytes).
Identifying the transport-layer protocol used by standard DNS client software is necessary to evaluate ACL rule parameters.
2
Evaluate the configured ACL entries against client DNS traffic.
Line 10 permits `tcp` port 53 traffic from `172.16.20.0/24` to `10.10.1.5`. Incoming UDP packets targeting port 53 do not match the protocol field (`tcp`) of line 10.
ACL rules evaluate packets sequentially and require exact matches for configured fields (protocol, source, destination, port).
3
Determine packet disposition for unmatched traffic.
The incoming UDP packets fail to match lines 10, 20, and 30, reaching the end of the access control list where they are dropped by the implicit `deny ip any any` rule.
Every network ACL ends with an invisible default action that blocks all traffic not explicitly permitted.

Key Concept

Stateless ACL matching rules, transport layer protocol distinctions (TCP vs UDP for DNS), and the implicit deny behavior.
Estimated Time:2m 0s
Question 46Question

Which wireless security standard introduced mandatory support for the Counter Mode Cipher Block Chaining Message Authentication Code Protocol (CCMP), utilizing the Advanced Encryption Standard (AES) cipher to replace legacy TKIP encryption?

Show answer & explanation

Answer: WPA2

Answer

WPA2
WPA2 (Wi-Fi Protected Access 2), defined under IEEE 802.11i, introduced mandatory support for CCMP, which employs the 128-bit AES block cipher to deliver strong confidentiality and packet integrity.

Step-by-Step Solution

1
Identify the cryptographic mechanism described in the question prompt.
The prompt specifies the introduction of CCMP (Counter Mode Cipher Block Chaining Message Authentication Code Protocol) using AES.
Understanding which standard first mandated AES-CCMP is key to classifying 802.11 security generations.
2
Compare historical 802.11 security standards and their default encryption ciphers.
WEP used RC4 with static keys, WPA introduced TKIP over RC4, WPA2 introduced CCMP with AES, and WPA3 upgraded to GCMP-256 and SAE.
Mapping standards to ciphers isolates WPA2 as the standard that introduced CCMP.

Key Concept

Wireless Encryption Protocols and Ciphers
Question 47Question

A remote worker needs to access internal corporate web applications over the Internet using a standard web browser with SSL/TLS encryption, without installing any dedicated software on the laptop. Which of the following remote access solutions is being utilized?

Show answer & explanation

Answer: Clientless SSL VPN

Answer

Clientless SSL VPN is the technology that provides secure remote access via a standard web browser without requiring client software installation.
Clientless SSL VPN enables secure remote access to web-based internal applications directly through a standard web browser using SSL/TLS encryption. Because the browser handles the cryptographic session, no additional client software needs to be deployed or managed on the endpoint device.

Step-by-Step Solution

1
Analyze the access requirements described in the scenario.
The scenario specifies connection through a standard web browser, SSL/TLS encryption, and no dedicated client software installation.
Identifying endpoint application requirements and transport mechanisms determines the appropriate VPN model.
2
Match the requirement against available remote access technologies.
Clientless SSL VPN runs directly within a Web browser using standard TLS, satisfying all endpoint restrictions.
IPsec requires pre-installed host software, while RADIUS and SNMPv3 serve authentication and network management purposes respectively.

Key Concept

Clientless SSL VPN vs. Client-based Remote Access
Estimated Time:45s
Question 48Question

An enterprise network engineer is documenting the connection workflow for remote employees accessing internal web applications via a Clientless SSL/TLS VPN gateway integrated with a central RADIUS AAA server. Arrange the operational steps in the correct chronological sequence from the initial remote connection request to the retrieval of internal corporate resources.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence begins with establishing the underlying TLS session on TCP port 443, presenting the web authentication portal, forwarding a RADIUS Access-Request to the AAA server, receiving the RADIUS Access-Accept response with authorization parameters, generating the authenticated portal session with an HTTP cookie, and finally proxying client HTTP requests to internal servers.
Establishing a Clientless SSL VPN session requires a strict logical progression: first, negotiating an encrypted TLS channel (TCP 443) to protect credential transmission; second, presenting the login interface; third, using RADIUS AAA protocol to forward credentials from the gateway to the backend authentication server; fourth, receiving authorization via RADIUS Access-Accept; fifth, issuing session state cookies and rendering the application portal; and sixth, acting as a Layer 7 reverse proxy for requests to internal corporate resources.

Step-by-Step Solution

1
Establish encrypted transport layer connection
TLS session negotiated over TCP port 443 between client browser and VPN concentrator.
Security requires creating an encrypted channel before transmitting sensitive user authentication data.
2
Present authentication interface
VPN gateway delivers the HTML login portal to the remote client browser.
The gateway must collect user credentials over the secure channel.
3
Delegate authentication to RADIUS AAA server
VPN gateway formats an Access-Request message and sends it over UDP (port 1812/1645) to RADIUS.
The VPN gateway functions as a RADIUS client and delegates identity verification to central AAA infrastructure.
4
Receive AAA authorization validation
RADIUS server validates credentials and responds with an Access-Accept packet containing user group policies.
The central directory confirms identity and communicates access constraints to the VPN concentrator.
5
Instantiate client session state
VPN gateway sets a secure HTTP session cookie and renders the customized portal page.
Session cookies maintain state across subsequent HTTPS requests without re-authenticating on every page load.
6
Reverse-proxy internal application traffic
The gateway accepts portal requests, communicates with internal application servers, and returns re-encrypted responses to the client.
Clientless SSL VPN access operates at Layer 7, functioning as a reverse proxy without assigning an internal virtual IP adapter to the endpoint.

Key Concept

Clientless SSL/TLS VPN Architecture & AAA/RADIUS Sequence
Question 49Question

A network administrator installs a passive Network Intrusion Detection System (NIDS) connected to a switch SPAN port to monitor application traffic for web servers. All incoming web application traffic is encrypted end-to-end using TLS on TCP port 443. During a penetration test, simulated cross-site scripting (XSS) attacks sent inside HTTPS payloads pass through the network undetected by the NIDS. Which of the following best explains why the NIDS failed to generate an alert?

Show answer & explanation

Answer: The passive NIDS cannot decrypt packet payloads in transit, preventing signature matching against the encrypted application-layer attack strings.

Answer

The passive NIDS failed to detect the attack because it cannot inspect packet payloads encrypted by TLS without access to session decryption mechanisms.
Network Intrusion Detection Systems (NIDS) rely on deep packet inspection (DPI) to match known attack signatures against application-layer payloads. When web application traffic is protected by TLS encryption, the HTTP payload containing the attack string (such as an XSS payload) is converted into ciphertext. A passive out-of-band NIDS connected to a SPAN port receives duplicate raw encrypted frames and lacks the cryptographic keys and inline decryption capability required to inspect the underlying payload.

Step-by-Step Solution

1
Analyze the traffic type and deployment mode described in the scenario.
The traffic uses TLS encryption on TCP port 443, and the sensor is a passive out-of-band NIDS connected via SPAN port.
Understanding where the sensor sits and what data it receives determines its visibility limits.
2
Evaluate the impact of end-to-end TLS encryption on network-based inspection.
TLS encrypts the application layer payload (HTTP request containing XSS vectors) before transmission across the wire.
Signature-based NIDS inspects unencrypted payload strings; when traffic is encrypted, the payload appears as uninterpretable ciphertext to the passive network sensor.
3
Identify the correct technical limitation causing the detection failure.
Without SSL/TLS decryption offloading or a host-based agent (HIDS/HIPS), the NIDS cannot perform deep packet inspection on encrypted payloads.
This highlights the trade-off of passive out-of-band NIDS deployments when facing modern encrypted transport protocols.

Key Concept

Impact of Payload Encryption on Network Intrusion Detection Systems
Question 50Question

A system administrator is configuring a secure remote access solution using an SSL/TLS VPN to allow telecommuters to access internal network applications. Which transport layer protocol and default port number are used by an SSL/TLS VPN connection?

Show answer & explanation

Answer: TCP port 443

Answer

TCP port 443 is the standard protocol and port used for SSL/TLS VPN connections.
SSL/TLS remote access VPNs utilize Transport Layer Security, which operates over TCP port 443 by default. Because TCP port 443 is also used for standard encrypted web browsing (HTTPS), it easily traverses firewalls and Network Address Translation (NAT) devices.

Step-by-Step Solution

1
Identify the VPN technology specified in the scenario.
The scenario specifies an SSL/TLS-based remote access VPN.
Determining the underlying protocol suite identifies the required transport protocol and port assignment.
2
Associate SSL/TLS with its standard transport layer port number.
SSL/TLS uses TCP port 443.
Port 443 is the established standard port for Transport Layer Security (TLS) traffic.

Key Concept

SSL/TLS VPN Transport Port Characteristics
Estimated Time:45s
Question 51Question

A network security administrator is deploying a site-to-site IPsec VPN tunnel between a branch office and central headquarters across an ISP connection where the branch router sits behind a network device performing Port Address Translation (PAT). Initial testing using Authentication Header (AH) in transport mode fails to pass traffic, whereas switching the configuration to Encapsulating Security Payload (ESP) in tunnel mode with NAT-Traversal (NAT-T) enabled allows full connectivity. Which of the following technical mechanisms explains why AH fails across a PAT-enabled device while ESP with NAT-T functions successfully?

Show answer & explanation

Answer: AH computes its Integrity Check Value (ICV) over immutable header fields including IP source and destination addresses, causing authentication failures when PAT mutates header fields; ESP with NAT-T encapsulates protocol packets inside UDP port 4500 headers to preserve payload integrity across translation.

Answer

AH fails in a PAT environment because its Integrity Check Value (ICV) calculation incorporates the outer IP header (including IP addresses), which is altered by PAT and leads to verification failure. In contrast, ESP encapsulates payload data without hashing the outer IP header, and NAT-T wraps ESP inside UDP port 4500 headers to allow PAT routers to translate IP addresses and UDP port numbers without breaking packet integrity or firewall tracking.
The option explaining that AH includes outer IP header fields in its ICV calculation while ESP with NAT-T encapsulates traffic in UDP port 4500 is correct. Because PAT modifies IP addresses in the packet header, AH's cryptographic integrity check fails upon receipt. ESP does not include the outer IP header in its ICV, and NAT-Traversal encapsulates ESP within UDP port 4500 packets, allowing PAT devices to translate address and port headers seamlessly.

Step-by-Step Solution

1
Analyze the scope of cryptographic integrity protection for IPsec Authentication Header (AH).
Identify that AH calculates an Integrity Check Value (ICV) over the entire IP packet, including immutable fields in the outer IP header such as Source and Destination IP addresses.
Understanding what fields are signed by AH explains why any modification to the IP packet in transit invalidates the hash.
2
Examine the impact of Port Address Translation (PAT) on packet headers.
Recognize that PAT modifies source/destination IP addresses and layer 4 port numbers on intermediate network devices.
Address translation changes header values, which directly causes the receiving peer's AH ICV check to fail.
3
Evaluate why Encapsulating Security Payload (ESP) with NAT-Traversal (NAT-T) resolves the issue.
Note that ESP does not protect the outer IP header within its ICV, and NAT-T encapsulates ESP (IP Protocol 50) inside standard UDP datagrams (UDP port 4500).
Encapsulating ESP within UDP allows PAT routers to modify outer IP and UDP headers without altering the encrypted inner payload or invalidating the ICV.

Key Concept

IPsec AH vs ESP Header Protection and NAT-Traversal (NAT-T) Mechanics
Question 52Question

A network security team is deploying an extended stateless IPv4 Access Control List (ACL) on an egress router interface filtering traffic between an internal database server (10.50.10.25/2410.50.10.25/24) and external application servers (172.16.100.0/24172.16.100.0/24). The application servers initiate database connections to TCP port 54325432 (PostgreSQL), and the database server is configured to send automated diagnostic alerts to an external syslog server at 172.16.100.50172.16.100.50 listening on UDP port 514514. Which TWO configuration entries or operational requirements must be implemented on the stateless egress ACL to guarantee bidirectional application communication and outbound alerting? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Permit outbound TCP traffic from host 10.50.10.25 source port 5432 to 172.16.100.0/24 with TCP control flags set to permit return query responses.; Permit outbound UDP traffic from host 10.50.10.25 to destination host 172.16.100.50 on destination port 514.

Answer

To allow communication through a stateless router ACL, explicit outbound rules must be created: one allowing return TCP responses from source port 5432 with TCP control flags (ACK/established) set, and one allowing outbound UDP syslog traffic from the database server to destination IP 172.16.100.50 on destination UDP port 514.
Because stateless ACLs do not automatically track session state, return traffic from TCP port 5432 must be explicitly permitted using TCP flag matching (ACK/established). Additionally, UDP syslog traffic originating from the server targeting destination port 514 requires an explicit permit statement due to the implicit deny at the end of the ACL.

Step-by-Step Solution

1
Analyze the stateless filtering behavior for connection-oriented TCP traffic.
Unlike stateful firewalls, stateless router ACLs do not maintain a connection table. When an external host connects to TCP port 5432, return packets originating from the database server (source port 5432) require an explicit outbound ACL rule matching the TCP ACK or established flag.
Without an explicit return rule for source port 5432 with TCP control flags, return database traffic will be dropped by the ACL.
2
Analyze the stateless filtering behavior for connectionless UDP traffic.
Syslog traffic transmitted from the database server to the logging server at 172.16.100.50 uses connectionless UDP port 514. An explicit permit rule matching destination UDP port 514 is necessary.
Because UDP has no handshakes or connection states, stateless devices require a simple direction-specific match rule for destination UDP port 514.
3
Evaluate default ACL behavior and protocol definitions.
Standard ACLs end with an implicit deny all statement (`deny ip any any`), so unpermitted traffic is blocked. Standard Syslog uses UDP rather than TCP.
Confusing implicit deny rules or protocol types (TCP vs UDP) causes security rule misconfigurations.

Key Concept

Stateless ACL rules require bidirectional explicit definitions, using TCP control flag matching for TCP return flows and specific UDP port permitting for connectionless logging.
Question 53Question

Remote workers attempting to connect to an enterprise network using an IPsec IKEv2 remote access client report that authentication succeeds, but no internal network resources are accessible and tunnel data transmission fails immediately after connection setup. The edge network security monitoring tool shows that Phase 1 (IKE) negotiations complete successfully over UDP port 500, but Encapsulating Security Payload (ESP) packets sent during Phase 2 are silently dropped by the remote users' Small Office/Home Office (SOHO) routers performing Port Address Translation (PAT). Which of the following configuration changes will resolve this connectivity issue while maintaining secure, encrypted communications?

Show answer & explanation

Answer: Enable NAT Traversal (NAT-T) on the VPN headend gateway to encapsulate ESP data within UDP port 4500 packets.

Answer

Enabling NAT Traversal (NAT-T) on the VPN headend gateway encapsulates ESP traffic inside UDP port 4500 packets, allowing the IPsec tunnel to traverse PAT/NAT devices without dropping Phase 2 traffic.
Standard IPsec Encapsulating Security Payload (ESP) operates at Layer 3 using IP protocol number 50. Because ESP lacks Layer 4 TCP/UDP port headers, SOHO routers using Port Address Translation (PAT) frequently drop or misroute raw ESP packets. Enabling NAT Traversal (NAT-T) encapsulates ESP packets inside standard UDP datagrams targeting port 4500, permitting PAT routers to properly process and forward the encrypted tunnel traffic.

Step-by-Step Solution

1
Analyze the reported issue and network path symptoms.
Phase 1 (IKE) succeeds over UDP port 500, but Phase 2 data transport fails when raw ESP traffic (IP protocol 50) encounters intermediate SOHO routers performing Port Address Translation (PAT).
PAT devices rebind Layer 4 TCP/UDP ports, but standard ESP operates directly on Layer 3 (IP protocol 50) without TCP or UDP headers, causing many basic consumer NAT routers to drop or fail to track ESP sessions correctly.
2
Evaluate potential solutions for IPsec NAT compatibility.
NAT Traversal (NAT-T) automatically detects intermediate NAT/PAT devices during Phase 1 negotiations (IKE) and wraps the raw ESP packets inside UDP headers using port 4500.
Because UDP port 4500 contains standard Layer 4 port headers, PAT gateways can cleanly translate and track the stateful VPN session.
3
Verify protocol enforcement and security posture.
Enabling NAT-T on the headend gateway allows remote users behind home PAT routers to establish a fully encrypted IPsec tunnel without sacrificing confidentiality.
NAT-T maintains ESP encryption while resolving the NAT handling conflict.

Key Concept

IPsec NAT Traversal (NAT-T) and UDP Port 4500 Encapsulation
Estimated Time:2m 0s
Question 54Question

An IT administrator investigating unexpected latency on a voice-over-IP (VoIP) network segment notices that host traffic destined for the default gateway IP address (10.20.4.110.20.4.1) is being redirected through an unauthorized host with MAC address `02:AB:C1:23:45:67`. Inspection of network captures reveals continuous unsolicited Gratuitous Address Resolution Protocol (GARP) frames originating from IP address 10.20.4.8810.20.4.88, associating its own physical address with 10.20.4.110.20.4.1. Which of the following network attack types is actively occurring on this segment?

Show answer & explanation

Answer: ARP Poisoning

Answer

ARP Poisoning is occurring because the attacker uses unsolicited GARP broadcasts to overwrite the Layer 2 cache entries of local devices.
The correct option correctly identifies ARP Poisoning because the attacker sends forged Gratuitous ARP packets to pollute the neighbor caches of local hosts, binding the gateway's IP address to the attacker's physical MAC address for traffic interception.

Step-by-Step Solution

1
Analyze the protocol behavior described in the incident logs.
Unsolicited Gratuitous ARP (GARP) frames are mapping IP address 10.20.4.1 to MAC address 02:AB:C1:23:45:67.
Address Resolution Protocol operates at Layer 2 to map IPv4 logical addresses to physical MAC addresses.
2
Determine how local hosts handle these incoming frames.
Hosts update their internal ARP tables to send gateway traffic to the attacker's network interface.
Standard network nodes blindly update their ARP tables upon receiving ARP responses without validating prior request queries.
3
Identify the corresponding security attack classification.
This technique matches the operation of ARP Poisoning (or ARP Spoofing).
Manipulating Layer 2 neighbor discovery entries with spoofed MAC mappings is the core mechanism of ARP poisoning.

Key Concept

Common Network Attack Types and Vectors - ARP Poisoning
Question 55Question

During a security incident investigation on an enterprise local area network, network monitoring tools record a high volume of traffic originating from a host connected to switch port Fa0/12. Analysis reveals that the host flooded the switch with thousands of Ethernet frames containing randomized source MAC addresses, completely filling the switch Content Addressable Memory (CAM) table. Immediately following this flood, analysts observe that confidential unicast traffic intended for a specific internal database server is being replicated and sent out all active ports on the VLAN. Which of the following statements accurately describe the underlying mechanics of this network attack and the appropriate Layer 2 countermeasures? (Select TWO)

Select all that apply

Show answer & explanation

Answer: The attack forces the switch into a fail-open state (unicast flooding), causing it to act like a hub and broadcast unicast frames across all ports in the VLAN when destination MAC addresses cannot be found in the CAM table.; Configuring Port Security on switch interfaces to limit the maximum number of learned MAC addresses and specify violation actions effectively prevents MAC flooding attacks.

Answer

The attack forces the switch into a fail-open state (unicast flooding) due to CAM table exhaustion, and configuring Port Security with MAC address limits on switch interfaces is the primary Layer 2 mitigation.
The scenario describes a classic MAC flooding (CAM table exhaustion) attack. By overwhelming the switch with spoofed source MAC addresses, the switch's forwarding table fills up, causing it to fall back to flooding unknown unicast frames out all ports in the VLAN (behaving like a hub). Implementing Port Security on switch access ports restricts the allowed MAC addresses per port, preventing an attacker from injecting thousands of fake MAC addresses.

Step-by-Step Solution

1
Analyze the observed attack mechanics described in the scenario.
The continuous generation of frames with randomized source MAC addresses exhausts the fixed storage space of the switch CAM table.
Once the CAM table is full, legitimate MAC-to-port bindings are flushed, and the switch cannot store new valid bindings.
2
Evaluate how a switch handles frames with destination MAC addresses missing from the CAM table.
The switch enters a fail-open condition known as unknown unicast flooding.
Because the switch cannot look up the destination port in its table, it floods unicast frames to every port in the same VLAN except the ingress port, allowing an attacker on any port to capture the traffic.
3
Identify the proper switch configuration control to mitigate this specific Layer 2 attack vector.
Port Security with strict MAC address limits effectively blocks MAC flooding.
Port Security bounds the number of MAC addresses learned on access ports (e.g., maximum of 1 or 2 MACs per port) and triggers a shutdown or restrict action if unknown MAC addresses are received.

Key Concept

MAC Flooding / CAM Table Exhaustion and Port Security Mitigation
Question 56Question

Match each centralized authentication protocol or access control framework component to its corresponding transport layer behavior, encryption boundary, or operational function.

Click a left item, then click its matching right item

Items

RADIUS Protocol
TACACS+ Protocol
802.1X Supplicant
EAP-TLS Framework

Matches

Show answer & explanation

Answer

RADIUS Protocol pairs with UDP 1812/1813 password-only encryption; TACACS+ Protocol pairs with TCP port 49 full payload encryption; 802.1X Supplicant pairs with client-side software credential agent; EAP-TLS Framework pairs with mutual certificate-based authentication.
Each security protocol and architectural term is matched accurately according to its transport protocol layer, payload encryption scope, endpoint role, or cryptographic verification mechanism.

Step-by-Step Solution

1
Analyze transport protocols and security boundaries for AAA frameworks.
RADIUS uses UDP ports 1812/1813 and encrypts only the user password field. TACACS+ uses TCP port 49 and encrypts the entire packet payload.
Differentiating transport types (UDP vs TCP) and encryption scope is crucial for evaluating network authentication architecture security.
2
Identify roles within 802.1X network access control.
The Supplicant represents the client end-node software requesting access, whereas the switch or wireless access point functions as the Authenticator.
Establishing explicit boundaries between endpoint client software, access devices, and AAA backends defines the 802.1X topology.
3
Evaluate Extensible Authentication Protocol (EAP) variants.
EAP-TLS requires client-side and server-side PKI digital certificates to validate both parties.
EAP-TLS is distinct from password-based or outer-tunnel EAP methods due to its mandatory mutual certificate requirement.

Key Concept

Centralized AAA Framework mechanisms, protocol transport differences, and 802.1X/EAP architecture components
Question 57Question

A network administrator needs to configure a wireless access point for a company office. Policy mandates that every employee must authenticate using their own unique corporate credentials managed by a centralized RADIUS server, rather than sharing a static password. Which wireless security mode should be configured on the access point?

Show answer & explanation

Answer: WPA3-Enterprise

Answer

WPA3-Enterprise
WPA3-Enterprise specifies the use of IEEE 802.1X authentication, allowing clients to authenticate individually against a backend RADIUS server using personalized credentials.

Step-by-Step Solution

1
Identify the authentication requirement described in the scenario
The requirement calls for individual user credentials authenticated against a centralized RADIUS server via 802.1X.
Enterprise wireless modes integrate with 802.1X/RADIUS to support central user account management.
2
Distinguish between Personal (PSK/SAE) and Enterprise (802.1X) wireless security modes
Personal modes use a shared passphrase, whereas Enterprise modes utilize 802.1X authentication servers.
Choosing an Enterprise wireless mode satisfies the requirement for central RADIUS authentication.

Key Concept

WPA3 Enterprise vs. Personal Authentication Modes
Question 58Question

An enterprise monitors its internal data center network using a passive Network Intrusion Detection System (NIDS) connected to a switch SPAN port. During a security incident, an attacker successfully exploits a vulnerability on a Linux target server by transmitting crafted TCP packets containing overlapping sequence numbers with conflicting data payloads (a TCP stream segmentation evasion attack). Although traffic reached the sensor, the NIDS failed to generate an alert because its stream reassembly engine interpreted the overlapping segments differently than the target server's IP/TCP protocol stack. Which of the following actions best addresses this detection failure while maintaining zero impact on network latency?

Show answer & explanation

Answer: Tune the NIDS stream reassembly engine's target-oriented policy to match the reassembly behavior of the target host's operating system.

Answer

Tune the NIDS stream reassembly engine's target-oriented policy to match the reassembly behavior of the target host's operating system.
When attackers craft overlapping TCP segments, different host operating systems apply distinct rules to decide whether original or newer overlapping bytes take precedence. A passive NIDS uses stream normalization engines with target-oriented policies to align its reassembly logic with the exact operating system of the target destination host. Tuning these policies ensures the NIDS reassembles the payload identically to the target host, detecting evasive attacks out-of-band without introducing inline latency.

Step-by-Step Solution

1
Analyze the attack mechanism and NIDS failure mode.
Identified that the attacker used TCP stream segmentation evasion (overlapping sequence numbers), which caused the passive NIDS engine to reconstruct a benign payload while the target OS reconstructed the malicious payload.
Different operating systems (e.g., Linux vs. Windows) resolve overlapping TCP sequence numbers using different prioritization rules (e.g., favoring original vs. subsequent segments).
2
Evaluate deployment constraints.
The solution must maintain zero impact on network propagation delay and latency.
Converting to an inline network intrusion prevention system (NIPS) introduces processing delay and single points of failure, violating the requirement.
3
Select the appropriate NIDS configuration fix.
Configure target-oriented session reassembly policies on the out-of-band NIDS.
Target-oriented reassembly allows the passive sensor to apply host-specific TCP reassembly rules per target IP address, neutralizing evasion attacks out-of-band without adding network latency.

Key Concept

Target-Oriented TCP Stream Reassembly in Out-of-Band NIDS
Question 59Question

A network security administrator is deploying a client-based SSL/TLS remote access VPN solution with host posture assessment and Multi-Factor Authentication (MFA). In what chronological order do the following operational steps occur during a successful client connection sequence from initial packet transmission to secure internal network access?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with negotiating the TLS handshake over TCP port 443 to secure the control plane, followed by authenticating user credentials and MFA tokens via RADIUS, performing host posture compliance assessment, and concluding with virtual inner IP assignment and encrypted tunnel establishment.
In a secure remote access SSL/TLS VPN workflow, the sequence follows strict dependency ordering: First, transport security is established via a TLS handshake on TCP port 443. Second, user identity and MFA credentials are validated against an enterprise AAA/RADIUS server. Third, Network Access Control (NAC) posture evaluation checks endpoint compliance (antivirus, patches, host firewall). Fourth, once both user identity and device posture pass validation, the gateway assigns an internal IP address and instantiates the encrypted data tunnel.

Step-by-Step Solution

1
Establish transport-layer encrypted control channel
TLS session established on TCP port 443 with server certificate validation.
The client must first verify the identity of the VPN gateway and establish cryptographic privacy before sending sensitive login credentials.
2
Authenticate user identity with multi-factor authentication
RADIUS AAA server validates primary credentials and TOTP token.
Verifying user identity ensures that unauthenticated users cannot consume gateway resources or submit health telemetry.
3
Execute endpoint posture and health compliance check
Posture agent verifies OS patches, local firewall state, and AV signatures, transmitting compliance confirmation to the gateway.
Endpoint health checks prevent non-compliant or compromised devices from bridging malware onto the internal corporate network.
4
Allocate virtual inner IP address and establish network tunnel
Gateway assigns internal virtual IP address and binds network-layer encapsulation to the client virtual adapter.
Tunnel interface creation and inner address assignment complete the connection pipeline after all authentication and authorization barriers pass.

Key Concept

SSL/TLS VPN Connection Sequence, AAA Integration, and Endpoint Posture Assessment
Question 60Question

A network technician is configuring a secure wireless network for a regional field office. Management mandates enhancing security beyond WPA2-Personal to protect against offline dictionary attacks and wireless management frame spoofing, but the site lacks the infrastructure required for centralized RADIUS authentication. Which TWO of the following features or protocols must be implemented to fulfill these requirements under WPA3-Personal?

Select all that apply

Show answer & explanation

Answer: Simultaneous Authentication of Equals (SAE) to replace the legacy pre-shared key handshake and defend against offline dictionary attacks; Mandatory integration of Protected Management Frames (PMF / IEEE 802.11w) to safeguard unicast and multicast management traffic against spoofing

Answer

Simultaneous Authentication of Equals (SAE) and mandatory Protected Management Frames (PMF / IEEE 802.11w) must be implemented for WPA3-Personal.
WPA3-Personal enhances wireless security by introducing Simultaneous Authentication of Equals (SAE) to eliminate vulnerability to offline dictionary attacks without requiring a RADIUS infrastructure. Additionally, WPA3 makes Protected Management Frames (PMF / IEEE 802.11w) mandatory to protect wireless management traffic from deauthentication spoofing.

Step-by-Step Solution

1
Analyze site constraints and security requirements
The scenario specifies a WPA3-Personal deployment without RADIUS infrastructure, requiring protection against offline dictionary attacks and management frame spoofing.
Identifying the target security standard and lack of 802.1X enterprise authentication eliminates 802.1X / RADIUS features.
2
Identify the key authentication upgrade in WPA3-Personal
Simultaneous Authentication of Equals (SAE) replaces WPA2 PSK.
SAE utilizes the Dragonfly Key Exchange to ensure forward secrecy and protect against offline dictionary attacks without requiring user-specific certificates.
3
Identify the management frame protection requirement
Protected Management Frames (PMF / IEEE 802.11w) are mandatory in WPA3.
PMF authenticates management frames such as deauthentication and disassociation, mitigating wireless spoofing attacks.

Key Concept

WPA3-Personal Security Enhancements (SAE and PMF)
PreviousPage 3 / 22Next
Network Security Practice Questions — CompTIA Network+ — Page 3 | Examkin