Network Security

427 questions

Question 21Question

Match each authentication protocol or security standard to its core operational characteristic.

Click a left item, then click its matching right item

Items

RADIUS
TACACS+
Kerberos
802.1X

Matches

Show answer & explanation

Answer

RADIUS matches with combining authentication and authorization while encrypting only passwords over UDP; TACACS+ matches with separating AAA services and encrypting the full payload over TCP port 49; Kerberos matches with using ticket-granting tokens for mutual authentication; 802.1X matches with providing port-based network access control.
Each term is correctly matched according to its underlying transport protocol, encryption scope, AAA architecture, or access control mechanism.

Step-by-Step Solution

1
Identify the protocol that combines authentication/authorization and encrypts passwords over UDP.
RADIUS matches this operational profile.
RADIUS uses UDP ports 1812/1813 and obscures only the password payload.
2
Identify the protocol that separates all AAA pillars and encrypts the full payload over TCP port 49.
TACACS+ matches this operational profile.
TACACS+ operates over TCP port 49 and encrypts the entire packet body following the header.
3
Identify the authentication system based on tickets and mutual authentication.
Kerberos matches this operational profile.
Kerberos uses Ticket Granting Services to authenticate clients without transmitting passwords over the network.
4
Identify the standard responsible for port-based network authentication.
802.1X matches this operational profile.
802.1X blocks unauthorized network traffic at Layer 2 until credentials are confirmed by an authentication server.

Key Concept

AAA Framework and Authentication Methods
Question 22Question

A network administrator implements cryptographic hashing algorithms to verify that transmitted configuration files are not altered or tampered with during transit. Which core pillar of the CIA triad is the administrator primarily protecting?

Show answer & explanation

Answer: Integrity

Answer

Integrity
Integrity ensures that information is protected against unauthorized modification, tampering, or corruption. Using cryptographic hashes to verify that files arrive unaltered directly fulfills the integrity requirement of the CIA triad.

Step-by-Step Solution

1
Analyze the technical control described in the scenario.
The control uses cryptographic hashing to detect whether configuration files have been altered or modified in transit.
Hashing produces a unique checksum value that changes if any bit of data is altered.
2
Map the control's objective to the pillars of the CIA triad.
Preventing unauthorized alteration and guaranteeing data trustworthiness directly maps to Integrity.
Integrity focuses on guarding against improper data modification or destruction.

Key Concept

Data Integrity and Cryptographic Hashing
Question 23Question

An enterprise organization is updating its security architecture to protect internal application servers. The solution must achieve two primary objectives: first, detect zero-day exploit attempts against server kernel processes that receive encrypted transport payloads; second, monitor network-wide bandwidth and protocol utilization patterns without introducing packet delivery latency or creating a single point of failure on the network link. Which of the following deployment choices will meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy Host-based Intrusion Prevention Systems (HIPS) using anomaly-based detection on the application servers.; Deploy a Network-based Intrusion Detection System (NIDS) connected out-of-band via a hardware network TAP.

Answer

The organization should deploy Host-based Intrusion Prevention Systems (HIPS) with anomaly-based detection on the application servers and deploy a Network-based Intrusion Detection System (NIDS) connected out-of-band via a hardware network TAP.
Deploying HIPS with anomaly detection directly on the servers allows inspection of unencrypted host operations and system calls, permitting active blockage of novel zero-day exploits. Deploying NIDS out-of-band via a hardware TAP delivers full network visibility for monitoring traffic trends without placing any processing delay on the inline path.

Step-by-Step Solution

1
Analyze the host security requirement for encrypted payloads and zero-day threat prevention.
Network-based devices cannot inspect encrypted payloads without TLS termination, whereas host-based systems (HIPS) inspect data after decryption. Anomaly-based detection is required because signature-based detection cannot identify zero-day attacks.
Host-based prevention operates at the system call/process level, allowing it to actively block behavior anomalies on the server itself.
2
Analyze the network monitoring requirement for zero latency and high availability.
Inline deployments (such as NIPS) introduce processing delay and risk becoming a single point of failure. Out-of-band deployments using hardware TAPs or SPAN ports eliminate latency.
NIDS connected to a hardware TAP passively analyzes copied traffic without impacting inline link latency or network availability.

Key Concept

HIDS/HIPS vs NIDS/NIPS Placement and Detection Logic
Question 24Question

A network security administrator is evaluating an automated log collection architecture. Network routers and switches are configured to transmit syslog messages to a centralized syslog server over an encrypted TLS connection. However, the syslog server writes the received log streams directly to a disk volume without generating message digests, cryptographic hashes, or digital signatures. During a post-incident investigation, security analysts discover that an attacker compromised local host credentials on the log server and modified historic log entries to erase evidence of lateral movement. Which security pillar of the CIA triad was directly compromised due to the lack of log hashing or cryptographic validation?

Show answer & explanation

Answer: Integrity, because the storage mechanism lacks controls to detect or prevent unauthorized modification of the log data.

Answer

Integrity, because the storage mechanism lacks controls to detect or prevent unauthorized modification of the log data.
The correct answer highlights Integrity because the core security gap stems from the storage repository failing to apply cryptographic hashing (such as SHA-256) or digital signatures to stored log files. Integrity ensures that data remains whole, accurate, and protected against unauthorized modification or tampering.

Step-by-Step Solution

1
Analyze the security controls active during transit and storage.
TLS protects syslog messages while in transit (Confidentiality and basic transit protection), but no cryptographic hashes or signatures are applied upon disk storage.
Identifying missing security controls pinpoints which phase of the data lifecycle is vulnerable.
2
Evaluate the nature of the security incident described in the scenario.
An attacker altered historical log entries to remove evidence of lateral movement.
Unauthorized alteration of data directly impacts the trustworthiness and authenticity of stored information.
3
Map the specific failure and control gap to the CIA Triad pillars.
The inability to verify data authenticity or detect tampering represents a failure of Integrity.
Integrity guarantees that data has not been modified, altered, or destroyed in an unauthorized manner.

Key Concept

CIA Triad: Integrity and Data Immutability Controls
Question 25Question

A network engineer is configuring an extended IPv4 Access Control List (ACL) on a stateless router interface filtering outbound traffic leaving a DMZ subnet (192.168.100.0/24192.168.100.0/24) toward an internal corporate LAN (10.0.0.0/810.0.0.0/8). DMZ web servers (192.168.100.10192.168.100.10192.168.100.20192.168.100.20) must respond to HTTPS client requests initiated from the internal LAN and send syslog telemetry to an internal monitoring server (10.2.2.50/3210.2.2.50/32) over UDP port 514. Which of the following ACL configuration entries are required on this interface to satisfy these requirements while accounting for stateless filtering mechanics? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: An entry permitting TCP traffic from source network 192.168.100.0/24 with source port 443 to destination network 10.0.0.0/8 on ports greater than 1023; An entry permitting UDP traffic from source network 192.168.100.0/24 to destination IP 10.2.2.50/32 with destination port 514

Answer

The required entries are the rule permitting TCP traffic from source network 192.168.100.0/24 with source port 443 back to destination network 10.0.0.0/8 on ports greater than 1023, and the rule permitting UDP traffic from source network 192.168.100.0/24 to destination host 10.2.2.50/32 on destination port 514.
In a stateless firewall or router extended ACL configuration, return traffic for established sessions is not tracked automatically. HTTPS uses TCP (port 443), so allowing response packets from DMZ servers back to client dynamic ports (> 1023) on the 10.0.0.0/8 network requires an explicit TCP permit entry. Additionally, syslog sends log data over UDP port 514, requiring a targeted UDP permit entry to the monitoring server at 10.2.2.50.

Step-by-Step Solution

1
Analyze the stateless nature of the router ACL filter
Unlike stateful firewalls, stateless extended ACLs evaluate packets individually and do not automatically allow return traffic for established sessions.
Because internal users initiate HTTPS connections to DMZ web servers, return traffic from DMZ servers back to clients must be explicitly permitted outbound from the DMZ interface.
2
Determine protocol and port parameters for HTTPS return traffic
HTTPS uses TCP. Return traffic originates from the DMZ server IP block (192.168.100.0/24192.168.100.0/24) on source port TCP 443 and targets internal client IP space (10.0.0.0/810.0.0.0/8) on dynamic/ephemeral destination ports (>1023> 1023).
Correctly matching transport layer protocols and directional port assignments is essential for valid stateless ACL filtering.
3
Determine protocol and port parameters for outbound syslog telemetry
Syslog uses UDP port 514. Outbound telemetry originates from DMZ hosts (192.168.100.0/24192.168.100.0/24) targeting the specific log server (10.2.2.50/3210.2.2.50/32) on destination port UDP 514.
Syslog is a connectionless service utilizing UDP port 514.

Key Concept

Stateless Access Control List (ACL) Traffic Directionality and Port Selection
Question 26Question

A network administrator is evaluating central authentication services for an enterprise network to support both remote access users and administrative switch management. Which of the following characteristics accurately describe operational differences between the RADIUS and TACACS+ protocols? (Select TWO).

Select all that apply

Show answer & explanation

Answer: RADIUS encrypts only the password field within packets, whereas TACACS+ encrypts the entire packet body after the header.; TACACS+ operates over TCP port 49, whereas standard RADIUS authentication traffic operates over UDP port 1812.

Answer

The correct statements indicate that RADIUS encrypts only the password field while TACACS+ encrypts the entire payload body, and that TACACS+ operates over TCP port 49 while standard RADIUS authentication uses UDP port 1812.
The correct options accurately identify protocol characteristics: RADIUS encrypts solely the password field using a shared secret and MD5 stream cipher, whereas TACACS+ encrypts the entire packet body following the header. Furthermore, TACACS+ uses TCP port 49 for connection-oriented transport, while RADIUS uses UDP port 1812 for authentication and UDP port 1813 for accounting.

Step-by-Step Solution

1
Analyze encryption coverage differences between RADIUS and TACACS+.
RADIUS encrypts only the user password field within Access-Request attributes. TACACS+ encrypts the full payload of every packet following the header, providing stronger overall confidentiality.
Security protocol differentiation is key to matching requirements for Administrative AAA vs Network Access AAA.
2
Analyze transport protocol and port assignments for both AAA protocols.
TACACS+ uses TCP port 49 for reliable packet delivery. RADIUS uses UDP ports 1812 (authentication/authorization) and 1813 (accounting).
Identifying transport layer protocols (TCP vs UDP) and standard port numbers is necessary for firewall rule configuration and protocol identification.
3
Evaluate AAA service coupling characteristics.
RADIUS combines authentication and authorization into single attribute exchanges (Access-Request / Access-Accept), whereas TACACS+ strictly separates AAA functions into independent processes.
This modularity allows TACACS+ to enforce per-command authorization on network devices, which RADIUS cannot natively achieve.

Key Concept

RADIUS vs TACACS+ Protocol Architecture and Operational Differences
Question 27Question

An administrator is configuring 802.1X port-based authentication on an enterprise network switch. Which component in the 802.1X architecture refers to the client workstation or software requesting access to the network?

Show answer & explanation

Answer: Supplicant

Answer

Supplicant
Under the IEEE 802.1X standard, the supplicant is the software daemon or client device attempting to gain network authorization through an authenticator.

Step-by-Step Solution

1
Identify the primary structural components of the IEEE 802.1X standard.
802.1X defines three key entities: the Supplicant, the Authenticator, and the Authentication Server.
Clear segregation of client software, access control hardware, and central credential databases is mandatory for 802.1X port security.
2
Determine which role corresponds to the host or software initiating the connection request.
The host endpoint or client agent running on the connecting system is designated as the supplicant.
The supplicant presents credentials to the authenticator (switch/AP), which encapsulated EAP messages to pass to the backend authentication server.

Key Concept

802.1X Framework Roles
Question 28Question

An enterprise security monitoring system generates an alert after detecting an unexpected surge in incoming UDP traffic targeted at a company's public-facing web server. Analysis of packet captures reveals thousands of external open recursive DNS servers sending large response payloads for ANY and TXT queries that were never initiated by the web server. The source IP address in the initial queries was forged to match the public IP address of the target server, causing severe link congestion. Which type of network attack is occurring?

Show answer & explanation

Answer: DNS amplification attack

Answer

The attack being conducted is a DNS amplification attack.
The correct answer describes a DNS amplification attack. In this attack vector, the threat actor sends small DNS queries for resource-heavy records (such as TXT or ANY) to third-party open DNS resolvers while forging (spoofing) the source IP address to be that of the victim. The resolvers reply to the victim with enlarged responses, resulting in volumetric bandwidth saturation.

Step-by-Step Solution

1
Analyze the observed attack mechanism described in the packet capture.
Unsolicited large DNS response traffic (such as TXT/ANY records) is arriving from multiple external open resolvers.
The attacker sent queries requesting large responses while spoofing the victim server's source IP address.
2
Evaluate how traffic amplification causes network degradation.
A small request generates a significantly larger response payload delivered directly to the spoofed victim IP address.
This disparity in request vs. response size amplifies the total attack volume, leading to denial of service via bandwidth starvation.
3
Identify the specific attack classification based on these characteristics.
The scenario describes a DNS amplification attack, which is a reflective DDoS attack vector.
It relies on open recursive DNS resolvers and IP spoofing to reflect amplified traffic onto the target.

Key Concept

DNS Amplification and Reflective DDoS Attacks
Estimated Time:1m 15s
Question 29Question

Match each authentication and access control protocol with its corresponding transport and security characteristics.

Click a left item, then click its matching right item

Items

RADIUS
TACACS+
Kerberos
802.1X

Matches

Show answer & explanation

Answer

RADIUS pairs with UDP transport and password-only encryption; TACACS+ pairs with TCP port 49 and full payload encryption; Kerberos pairs with port 88 and time-stamped ticketing; 802.1X pairs with EAPOL port-based framework encapsulation.
Each protocol maps directly to its specific network characteristics: RADIUS relies on UDP with password-only encryption; TACACS+ uses TCP port 49 with full payload encryption; Kerberos relies on time-stamped ticket granting over port 88; and 802.1X provides Layer 2 port-based access control via EAPOL encapsulation.

Step-by-Step Solution

1
Analyze transport and payload encryption features of RADIUS.
RADIUS operates on UDP ports 1812/1813 and encrypts only the password field within packets.
RADIUS was designed as a lightweight client/server network access protocol that combines authentication and authorization.
2
Analyze TACACS+ specifications.
TACACS+ operates over TCP port 49, encrypts the full payload, and separates AAA functions for granular command accounting and authorization.
TACACS+ provides high security for administrative access to network infrastructure.
3
Identify ticket-based single sign-on protocol characteristics.
Kerberos utilizes TCP/UDP port 88 and relies on Key Distribution Center (KDC) ticket granting and timestamp validation.
Kerberos avoids sending secrets over the network by issuing cryptographically signed tickets.
4
Identify port-based access control framework characteristics.
802.1X encapsulates Extensible Authentication Protocol over LAN (EAPOL) to authenticate endpoints at Layer 2.
802.1X regulates physical or wireless port connectivity before network privileges are granted.

Key Concept

AAA Framework Protocol and Transport Matrix Characteristics
Question 30Question

A security operations team requires a centralized AAA solution for managing network device administrative sessions. The requirements specify that authentication and authorization functions must be separated to allow granular command-level authorization, and the entire packet payload between the switch and AAA server must be encrypted. Which protocol and transport layer combination meets these security requirements?

Show answer & explanation

Answer: TACACS+ using TCP port 49

Answer

TACACS+ using TCP port 49
TACACS+ is designed for network device management because it decouples authentication and authorization, permitting per-command authorization policies. It also encrypts the entire packet body (everything past the header) and utilizes connection-oriented TCP port 49 for reliable transport.

Step-by-Step Solution

1
Evaluate protocol payload encryption and AAA modularity features
TACACS+ decouples authentication and authorization (enabling command-by-command authorization) and encrypts the entire payload following the TACACS+ header
RADIUS combines authentication and authorization and only encrypts the password field in Access-Request packets
2
Identify transport protocol and standard port association
TACACS+ uses TCP port 49 for reliable connection delivery
UDP is employed by RADIUS (ports 1812 and 1813), whereas TACACS+ relies on TCP

Key Concept

AAA Protocol Architectural Differences (TACACS+ vs RADIUS)
Question 31Question

A security engineer is configuring a site-to-site Virtual Private Network (VPN) between two gateway routers across an untrusted public network. The mandate requires that the entire original IP packet—including both its header and payload—must be fully encrypted and encapsulated within a new outer IP header for gateway-to-gateway transit. Which IPsec operational mode and protocol combination must be deployed to satisfy these requirements?

Show answer & explanation

Answer: IPsec Tunnel mode using Encapsulating Security Payload (ESP)

Answer

IPsec Tunnel mode using Encapsulating Security Payload (ESP) is the correct choice because Tunnel mode encapsulates the complete original IP packet in a new IP header for site-to-site gateway transport, and ESP provides the required confidentiality through payload encryption.
IPsec Tunnel mode is designed for site-to-site security gateways. It encapsulates the entire original IP packet inside a new outer IP header. Encapsulating Security Payload (ESP) encrypts the inner packet payload, ensuring total confidentiality across untrusted networks.

Step-by-Step Solution

1
Identify the required IPsec mode based on network architecture and header treatment.
Tunnel mode is required because the scenario calls for site-to-site encapsulation of the entire original IP packet (header + payload) inside a new outer IP header between gateway routers.
Transport mode only protects the IP payload and preserves the original IP header, making it suitable only for end-to-end host scenarios.
2
Identify the required IPsec security protocol based on cryptographic services needed.
Encapsulating Security Payload (ESP) is required because confidentiality (encryption) of the data is requested.
Authentication Header (AH) provides integrity and anti-replay protection but provides no encryption/confidentiality.
3
Combine the mode and protocol selection.
IPsec Tunnel mode + ESP fulfills both requirements: complete packet encapsulation for gateway transit and encryption for data privacy.
This combination forms the standard foundation for site-to-site IPsec VPN tunnels.

Key Concept

IPsec Modes (Tunnel vs. Transport) and Protocols (ESP vs. AH)
Question 32Question

A network administrator observes a flood of incoming ICMP Echo Reply packets targeting a key internal server. Investigation reveals that an external attacker sent ICMP Echo Requests to a network broadcast address with the source IP address spoofed to match the target server's IP address. Which type of network attack is taking place?

Show answer & explanation

Answer: Smurf attack

Answer

Smurf attack
The correct option describes a Smurf attack, which is a legacy form of denial-of-service (DoS) attack where an attacker broadcasts ICMP Echo Requests containing a spoofed source IP belonging to the target host. Every active host receiving the broadcast responds to the target host, creating a massive influx of ICMP Echo Reply traffic.

Step-by-Step Solution

1
Analyze the attack signature described in the scenario
Traffic consists of ICMP Echo Requests sent to a broadcast IP address with a spoofed source IP address.
Identifying the combination of ICMP traffic, IP spoofing, and broadcast addressing reveals the specific amplification mechanism.
2
Match the mechanism to the correct network attack type
The target system is overwhelmed by ICMP Echo Replies from multiple hosts on the network.
This specific technique of using network broadcast addresses to amplify ICMP traffic against a victim defines a Smurf attack.

Key Concept

Common Network Attack Types - Smurf Attack
Question 33Question

A network security team investigates an incident where an internal server crashed due to an IP fragmentation reassembly attack (Teardrop attack). Although an out-of-band Network Intrusion Detection System (NIDS) was actively monitoring traffic via a switch SPAN port with up-to-date threat signatures, it generated no alerts during the attack. Subsequent packet capture analysis reveals that the attacker intentionally transmitted overlapping IPv4 fragments with inconsistent offset values. Which of the following statements correctly explain why the passive NIDS failed to trigger an alert, and which architectural adjustment would directly prevent this evasion technique? (Select TWO)

Select all that apply

Show answer & explanation

Answer: The passive NIDS reassembled the overlapping fragments using different OS-specific reassembly logic than the target server host, causing the NIDS to inspect a harmless payload stream while the host reassembled a malicious one.; Deploying an inline Network Intrusion Prevention System (NIPS) capable of active packet normalization to reassemble, defragment, and sanitize traffic before it reaches target servers.

Answer

The NIDS failed to alert because passive sensors may utilize a different IP fragment reassembly algorithm (operating system target policy) than the target host, allowing overlapping fragments to construct a benign payload on the NIDS while forming a crash-inducing payload on the host. To directly resolve this evasion vulnerability, the organization should deploy an inline NIPS with packet normalization capabilities, which actively defragments, cleans, and sanitizes IP fragment streams before delivering packets to the host.
Passive out-of-band NIDS sensors process duplicated traffic via SPAN/TAP ports and must maintain target host operating system profile policies to reassemble IP fragments accurately. When fragment overlaps occur, an OS-policy mismatch between the NIDS engine and the destination host allows malformed payloads to bypass NIDS signature engines undetected. Replacing or supplementing this with an inline Network Intrusion Prevention System (NIPS) configured for packet normalization resolves the vulnerability by actively enforcing uniform fragment reassembly and dropping illegal overlapping offset sequences before they reach internal endpoints.

Step-by-Step Solution

1
Analyze why a passive NIDS fails during overlapping IP fragment attacks.
Identify that passive NIDS sensors must predict host OS fragment reassembly rules (e.g., First, Last, Linux, BSD, Windows policies). Inconsistent reassembly policies between NIDS and host allow attackers to disguise malicious payloads from passive inspection.
If the NIDS reassembles fragments differently than the target server, the NIDS inspects an innocent payload stream while the host executes the exploit.
2
Evaluate technical capabilities of passive NIDS vs. inline NIPS mechanisms against evasion attacks.
Determine that passive out-of-band monitoring cannot sanitize or alter packets in transit. An inline NIPS actively intercepts and normalizes traffic.
Inline packet normalization ensures that all IP fragments are defragmented and normalized into a single predictable stream before hitting internal destination endpoints.

Key Concept

IP Fragmentation Evasion Ambiguity and NIPS Packet Normalization
Question 34Question

A network administrator is reviewing filtering methods for perimeter security devices. Which of the following statements accurately describe the operational behavior of stateless firewalls and standard packet filters? (Select TWO)

Select all that apply

Show answer & explanation

Answer: They evaluate each network packet independently using static criteria such as source/destination IP addresses and port numbers.; They require separate explicit rules to permit return traffic because connection state context is not retained.

Answer

Stateless firewalls evaluate each packet independently against static rules (such as IP addresses and port numbers) and require separate explicit rules for return traffic because they do not track connection session state.
Stateless firewalls assess each packet on its own using header fields (IP addresses, protocols, port numbers) without maintaining state tables. As a result, return traffic generated from internal requests is not automatically recognized and requires an explicit matching permit rule.

Step-by-Step Solution

1
Analyze how stateless firewalls process traffic packets.
Stateless firewalls inspect each packet individually against configured access rules without storing state tables or session context.
Stateless filtering operates at Layers 3 and 4, checking header information on a per-packet basis.
2
Determine the impact of stateless processing on return traffic flows.
Because no state table exists to identify return packets belonging to established connections, explicit rules must be defined in both directions.
Without dynamic state tracking, return traffic is evaluated like any new incoming packet.

Key Concept

Stateless Firewall Packet Inspection & Rule Processing
Question 35Question

A security analyst is auditing an edge router configured with stateless Access Control Lists (ACLs) to filter traffic between an internal management subnet (10.200.5.0/2410.200.5.0/24) and a cloud monitoring cluster (172.31.40.0/24172.31.40.0/24). The analyst notes that SNMP monitoring requests sent over UDP port 161 from the cloud cluster to internal endpoints pass successfully, but the response packets generated by the internal endpoints fail to reach the monitoring cluster.

Which TWO of the following statements correctly explain why this issue occurs and identify an appropriate resolution?

Select all that apply

Show answer & explanation

Answer: Stateless ACLs evaluate packets individually without tracking connection state, requiring an explicit reverse ACL rule to permit return UDP traffic from source port 161 back to the monitoring cluster.; Migrating the filtering mechanism to a stateful firewall would resolve the issue because stateful inspection dynamically allows return traffic by referencing an entry created in its state table during outbound transmission.

Answer

The issue occurs because stateless ACLs inspect packets individually without maintaining connection tables, requiring an explicit reverse permit rule for returning traffic. Alternatively, replacing the stateless ACL with a stateful firewall resolves the issue by dynamically tracking sessions and automatically permitting return packets matching an active state table entry.
Stateless ACLs evaluate every packet independently without storing state history. Consequently, permitting outbound queries from a monitoring cluster does not automatically permit the response packets returning from internal hosts; an explicit reverse ACL entry is required to allow traffic flowing back. Alternatively, deploying a stateful firewall resolves this limitation because stateful devices monitor communication flows and dynamically permit return packets corresponding to active session entries.

Step-by-Step Solution

1
Analyze the filtering architecture
Identified that the edge router uses stateless Access Control Lists (ACLs).
Stateless devices treat every packet as an independent event and do not keep memory of previous packets or established connections.
2
Evaluate why return packets are dropped
Outbound SNMP queries from 172.31.40.0/24172.31.40.0/24 to 10.200.5.0/2410.200.5.0/24 match an outbound permit rule, but returning response traffic moving in the opposite direction hits the implicit deny rule because no matching inbound rule exists.
Stateless ACLs require symmetric, bidirectional rule definitions for bidirectional communication.
3
Determine valid remediation approaches
Two solutions exist: (1) Add an explicit reverse ACL rule for return traffic, or (2) replace the stateless ACL with a stateful firewall.
Stateful firewalls maintain connection tables (even creating pseudo-state entries for UDP flows) to dynamically permit returning response packets.

Key Concept

Stateless vs. Stateful Packet Filtering and ACL Directionality
Question 36Question

During a security audit, a network analyst discovers that a host connected to an access port on VLAN 10 successfully transmitted unauthorized frames directly to a critical server on VLAN 30 without passing through an inter-VLAN routing firewall. The two hosts reside on separate switches connected by an 802.1Q trunk link, where VLAN 10 is designated as the native VLAN. Which of the following statements correctly identify the mechanism behind this security breach and the appropriate remediation step? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: The attacker crafted frames with dual 802.1Q tags; the first switch stripped the outer tag matching its native VLAN and forwarded the frame with the inner target tag across the trunk.; The attack can be prevented by reassigning the native VLAN across all trunk links to an unused dummy VLAN ID and explicitly tagging native VLAN traffic.

Answer

The attack was executed via 802.1Q double tagging, where the first switch stripped the outer native VLAN tag and forwarded the frame with the inner tag intact. The threat is mitigated by changing the native VLAN to an unused dummy VLAN ID across all trunk interfaces.
In an 802.1Q double tagging attack, an attacker sends an Ethernet frame containing two VLAN tags (an outer tag matching the trunk's native VLAN and an inner tag specifying the target destination VLAN). When the first switch receives the frame, it strips the outer native VLAN tag before transmitting the frame over the trunk link. The secondary switch reads the remaining inner tag and delivers the frame to the destination VLAN, bypassing Layer 3 routing and firewall filtering. To remediate this risk, network administrators must configure an unused dummy VLAN ID as the native VLAN across all switch trunk ports so that incoming frames from active access VLANs are never subject to native tag stripping.

Step-by-Step Solution

1
Analyze the reported VLAN traversal anomaly.
Identified 802.1Q Double Tagging (VLAN Hopping) exploitation.
When an attacker's access VLAN matches the native VLAN of an 802.1Q trunk, crafted frames containing two 802.1Q headers will have their outer tag removed by the first switch, allowing the inner tag to dictate destination VLAN delivery on the receiving switch.
2
Evaluate mitigation controls for double tagging vulnerabilities.
Reassign native VLANs to dedicated, unused VLAN IDs.
If no user endpoints reside on the native VLAN, frames arriving from valid host VLANs will always retain explicit tags, preventing unauthorized single-tag stripping over trunk links.

Key Concept

802.1Q Double Tagging Attack and Mitigation
Question 37Question

Match each wireless security standard on the left with its corresponding primary cryptographic cipher and authentication mechanism on the right.

Click a left item, then click its matching right item

Items

WEP (Wired Equivalent Privacy)
WPA2-Personal
WPA3-Personal
WPA3-Enterprise (192-bit mode)

Matches

Show answer & explanation

Answer

WEP pairs with RC4/CRC-32; WPA2-Personal pairs with AES-CCMP with PSK; WPA3-Personal pairs with SAE with AES-CCMP-128/GCMP-128; WPA3-Enterprise (192-bit mode) pairs with GCMP-256 with 802.1X EAP.
Each wireless security standard defines specific cryptographic primitives and authentication methods: WEP uses RC4 with CRC-32; WPA2-Personal introduces AES-CCMP with a Pre-Shared Key; WPA3-Personal replaces traditional PSK with SAE while retaining/upgrading AES encryption; and WPA3-Enterprise 192-bit mode enforces GCMP-256 alongside enterprise 802.1X EAP authentication.

Step-by-Step Solution

1
Identify legacy protocol primitives
WEP relies on the RC4 stream cipher and CRC-32.
WEP is the legacy standard utilizing static keys and RC4 encryption.
2
Distinguish WPA2 pre-shared key standards
WPA2-Personal pairs AES-CCMP with PSK authentication.
AES-CCMP replaced TKIP/RC4 as the mandatory cipher suite under IEEE 802.11i/WPA2.
3
Map WPA3 personal key exchange mechanisms
WPA3-Personal utilizes Simultaneous Authentication of Equals (SAE).
SAE provides forward secrecy and resistance to offline dictionary attacks.
4
Map enterprise high-security profile requirements
WPA3-Enterprise 192-bit mode maps to GCMP-256 with 802.1X EAP.
The 192-bit security mode specified in WPA3 requires GCMP-256 and robust EAP authentication methods.

Key Concept

Wireless Security Standards and Encryption Protocol Mapping
Question 38Question

Match each AAA protocol or network authentication framework to its corresponding operational characteristic.

Click a left item, then click its matching right item

Items

TACACS+
RADIUS
Kerberos
IEEE 802.1X

Matches

Show answer & explanation

Answer

TACACS+ matches with whole-payload TCP encryption and separated AAA functions; RADIUS matches with UDP password-only encryption and combined auth/authz; Kerberos matches with ticket-granting service mutual authentication; and IEEE 802.1X matches with Layer 2 EAP-based port access control.
Each authentication solution corresponds directly to its architectural features: TACACS+ delivers connection-oriented TCP administration with complete payload encryption and granular AAA separation; RADIUS operates over UDP with password-only encryption; Kerberos enforces ticket-granting mutual authentication; and IEEE 802.1X serves as a Layer 2 port-level access framework utilizing EAP encapsulation.

Step-by-Step Solution

1
Analyze TACACS+ operational properties
Identify TACACS+ characteristics: TCP port 49, full packet payload encryption, modular separation of AAA functions.
TACACS+ is primarily used for network device administration, allowing granular authorization of individual command-line instructions.
2
Analyze RADIUS operational properties
Identify RADIUS characteristics: UDP transport (ports 1812/1813), password-only obfuscation, combined authentication and authorization response.
RADIUS is designed for wide-scale user network access, such as VPNs and wireless authentications, leaving headers and attribute-value pairs unencrypted.
3
Analyze Kerberos operational properties
Identify Kerberos characteristics: Key Distribution Center (KDC), Ticket Granting Service (TGS), ticket-based single sign-on (SSO).
Kerberos authenticates identity across enterprise directory services (such as Active Directory) through symmetric session keys.
4
Analyze IEEE 802.1X operational properties
Identify IEEE 802.1X characteristics: Layer 2 port control, EAP encapsulation (EAPoL), supplicant-authenticator-server architecture.
802.1X prevents unauthorized endpoints from passing network traffic through a switch port or wireless access point until validated.

Key Concept

AAA Protocols and Authentication Framework Mechanics
Question 39Question

A network administrator needs to enable centralized remote monitoring on core network switches. The corporate security baseline mandates that management traffic must enforce both cryptographic user authentication and encryption (privacy) of transmitted payload data across the management network. Which SNMP configuration should the administrator implement to satisfy these security requirements?

Show answer & explanation

Answer: SNMPv3 using the authPriv security level

Answer

SNMPv3 using the authPriv security level
To satisfy requirements for both authentication and encryption of management data, SNMPv3 must be deployed using the authPriv (Authentication with Privacy) security level. This mode authenticates communication using algorithms such as SHA/MD5 and encrypts management payloads using AES or DES.

Step-by-Step Solution

1
Identify security policy requirements
Requirements are dual-fold: cryptographic authentication and privacy (encryption).
Hardening best practices dictate matching the exact security level supported by management protocols.
2
Evaluate SNMP version capabilities
SNMPv1 and SNMPv2c lack native cryptographic encryption; only SNMPv3 supports configurable security levels.
Legacy SNMP versions send community strings and data in cleartext.
3
Select the appropriate SNMPv3 security level
Select authPriv mode.
noAuthNoPriv offers no authentication/privacy, authNoPriv offers authentication without privacy, while authPriv provides both authentication and data encryption.

Key Concept

SNMP Protocol Hardening and Security Levels
Estimated Time:1m 15s
Question 40Question

During an incident response investigation, a network security analyst discovers that internal users attempting to connect to a partner organization's remote server were redirected to an untrusted external host. Analysis reveals that client workstations issued standard domain name lookup requests, but the enterprise's recursive resolver returned forged IP address records that had been injected into its local cache. Which of the following attack types best describes this security incident?

Show answer & explanation

Answer: DNS cache poisoning

Answer

DNS cache poisoning is the correct attack type, as it involves injecting invalid IP address resolutions into a caching DNS server to redirect user traffic.
DNS cache poisoning (also known as DNS spoofing) occurs when an attacker introduces false resolution data into a DNS resolver's cache. As a result, subsequent queries for the compromised domain return the attacker's fake IP address, redirecting legitimate users to malicious sites without modifying client configurations.

Step-by-Step Solution

1
Analyze the incident symptoms presented in the scenario.
Identified that client workstations issued standard domain name requests, but received corrupted IP address mappings cached on the internal resolver.
Understanding the precise vector differentiates Layer 2 address resolution attacks from Layer 7 domain resolution attacks.
2
Compare candidate attack vectors against domain name resolution mechanisms.
Confirmed that malicious injection of false domain-to-IP mappings into a recursive DNS server is defined as DNS cache poisoning (DNS spoofing).
Corrupting nameserver lookup entries diverts user connections at the domain resolution phase.

Key Concept

DNS Cache Poisoning and Network Attack Vectors
Estimated Time:1m 15s
PreviousPage 2 / 22Next
Network Security Practice Questions — CompTIA Network+ — Page 2 | Examkin