All practice questions

2237 questions

Question 781Question

A network administrator configures a pair of routers using a First Hop Redundancy Protocol (FHRP) to ensure high availability for a subnet. During scheduled maintenance on the primary router, the secondary router successfully assumes the active role according to the system logs. However, workstations on the subnet immediately lose access to external networks. Which of the following is the most likely cause of this connectivity failure?

Show answer & explanation

Answer: Workstations were configured with the physical IP address of the primary router as their default gateway instead of the shared virtual IP address.

Answer

Workstations were configured with the physical IP address of the primary router as their default gateway instead of the shared virtual IP address.
First Hop Redundancy Protocols rely on clients directing default gateway traffic to a designated Virtual IP (VIP). If workstations are manually or dynamically configured with the physical IP address of one router, failover mechanisms will not redirect host traffic when that specific physical router goes offline.

Step-by-Step Solution

1
Analyze the FHRP deployment model and host default gateway assignments.
FHRP protocols (such as HSRP or VRRP) create a single shared Virtual IP (VIP) and Virtual MAC address for host redundant default gateway operations.
For high availability to function seamlessly, end devices must point to the Virtual IP rather than any single physical router interface IP address.
2
Evaluate the reported symptom against host network settings.
Although the secondary router transitioned to active state correctly, host traffic reached a dead physical IP address because clients targeted the physical interface IP of the primary router.
If hosts use a physical IP, traffic destined for external networks fails as soon as that physical router is taken offline.

Key Concept

FHRP Virtual IP vs Physical IP Gateway Configuration
Question 782Question

A network engineer observes anomalous latency spikes on a critical web application server following a recent security upgrade. Upon investigation, the engineer discovers that security software deployed directly on the web server is performing deep packet inspection on all local system calls and application memory buffers, creating processing overhead under high traffic load. Which security control is actively causing this host-level performance degradation?

Show answer & explanation

Answer: Host-based Intrusion Prevention System (HIPS)

Answer

Host-based Intrusion Prevention System (HIPS)
The scenario describes a security agent installed directly on the host machine inspecting operating system calls and memory buffers in real time. A Host-based Intrusion Prevention System (HIPS) provides active protection at the host level, which can introduce noticeable CPU and latency overhead on high-traffic servers due to deep host-level inspection.

Step-by-Step Solution

1
Analyze the location of execution and inspection targets described in the scenario.
The control is executing directly on the web server host and inspecting host-level resources (system calls and memory buffers).
Host-based controls run as agents on individual endpoints rather than monitoring network interfaces.
2
Differentiate between detection (passive) and prevention (active inline/intervening) mechanisms.
Because the control actively inspects and acts upon host system calls during execution, it operates as an active inline host control.
Intrusion Prevention Systems (IPS) intercept and analyze actions before permitting execution, adding local host CPU/memory processing overhead.
3
Synthesize the architecture and deployment type to select the correct system.
A Host-based Intrusion Prevention System (HIPS) matches both host-level deployment and active inspection characteristics.
HIPS provides real-time protection at the OS/application layer on host devices.

Key Concept

Host-based Intrusion Prevention System (HIPS) operation and host resource impact
Estimated Time:2m 0s
Question 783Question

During a scheduled maintenance window, a network technician updates the operating system of a primary enterprise router. Immediately after the device reboots with the newly installed firmware image, all recent ACL modifications and custom static routes disappear, causing routing failures across multiple subnets. An audit reveals that recent configuration changes resided solely in volatile memory when the firmware installer triggered the system reload. Which critical pre-patch maintenance procedure was omitted prior to executing the software update?

Show answer & explanation

Answer: Saving the running configuration to non-volatile startup storage and capturing a baseline configuration backup

Answer

Saving the running configuration to non-volatile startup storage and capturing a baseline configuration backup
The correct option correctly identifies that running configurations stored only in volatile RAM are erased upon a device reboot. To prevent data loss during patch management, engineers must copy the running configuration to persistent startup memory and export a baseline backup prior to initiating software upgrades.

Step-by-Step Solution

1
Analyze the operational failure mode post-update
Unsaved routing changes were stored only in RAM (running-config) and lost when the firmware update reloaded the appliance.
Firmware upgrades require a system reboot, which clears volatile memory.
2
Identify the mandatory pre-patch preparation standard
Commit all active changes (`copy running-config startup-config`) and export an off-box baseline configuration file.
Ensures active settings persist across reboots and provides a rollback point if the new patch behaves unexpectedly.

Key Concept

Pre-patch staging and configuration baseline persistence in patch management lifecycles.
Question 784Question

Following an emergency vulnerability disclosure, a network engineering team must apply a critical operating system patch to a high-availability core switch cluster without causing network downtime. Which of the following procedures should the team execute to ensure continuous service availability and full recovery capability during this maintenance operation? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Perform a rolling upgrade by patching the standby secondary chassis first and validating traffic failover prior to patching the active primary chassis.; Verify out-of-band management connectivity and capture verified system configuration and firmware image backups before initiating the installation.

Answer

The correct procedures are executing a rolling upgrade by updating the standby node first while verifying failover, and establishing out-of-band management access alongside complete configuration and image backups prior to update initiation.
To maintain zero downtime in high-availability enterprise environments, patch management protocols require rolling upgrades (updating the standby unit first, testing failover, then updating the active unit). Additionally, operational best practices dictate verifying out-of-band management pathways and taking complete image and configuration snapshots before modifying production software to guarantee rollback capability.

Step-by-Step Solution

1
Establish out-of-band access and complete baseline system state backups
Guarantees administrative access independent of production data paths and provides a full rollback point.
Network operations procedures require securing recovery tools before applying changes to critical core infrastructure.
2
Execute a phased rolling software update across the redundant cluster
Production traffic continues flowing through the active node while the secondary standby node is upgraded and verified.
Staggering updates across high-availability pairs preserves fault tolerance and prevents downtime during patch cycles.

Key Concept

High-Availability Rolling Upgrades and Pre-Patch Risk Mitigation
Question 785Question

Match each AAA authentication protocol or access control framework to its defining 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 full payload encryption over TCP port 49 with decoupled AAA; RADIUS matches password-only encryption over UDP ports 1812/1813 with combined authentication and authorization; Kerberos matches ticket-granting tokens over port 88 for single sign-on; IEEE 802.1X matches port-based access control encapsulating EAPOL.
Each protocol is accurately matched based on its transport protocol, default ports, encryption scope, and functional place in the AAA framework.

Step-by-Step Solution

1
Analyze transport layer protocols and encryption boundaries for TACACS+ and RADIUS.
TACACS+ uses TCP 49 with full packet payload encryption and decoupled AAA. RADIUS uses UDP 1812/1813 with password-only encryption.
Differentiating AAA server protocols relies on transport mode (TCP vs UDP), encryption scope, and functional separation.
2
Identify the ticket-based SSO authentication protocol.
Kerberos uses Ticket-Granting Services and symmetric key cryptography operating over port 88.
Kerberos is designed for domain single sign-on rather than network device management or RADIUS/TACACS+ remote access.
3
Identify the port-based access control framework standard.
IEEE 802.1X provides switch and wireless AP port-based security using EAPOL frames.
802.1X acts as an architectural framework connecting supplicants, authenticators, and backend AAA servers.

Key Concept

AAA Framework Operational Matrix (RADIUS, TACACS+, Kerberos, and 802.1X)
Question 786Question

A network security engineer is designing a centralized AAA solution for administrative management access to core switches and firewalls. Organization security policies dictate that authentication and authorization functions must be decoupled to allow granular per-command authorization rules, the complete packet payload (including administrative commands) must be encrypted over the wire, and the protocol must use connection-oriented transport on standard port 49. Which protocol should the engineer select to meet all of these compliance requirements?

Show answer & explanation

Answer: TACACS+, because it decouples AAA services, encrypts the entire packet payload, and operates over TCP port 49.

Answer

TACACS+ is the correct protocol choice because it decouples AAA functions, encrypts the full packet body, and uses TCP port 49.
TACACS+ (Terminal Access Controller Access-Control System Plus) strictly satisfies all three requirements specified in the scenario. It decouples authentication, authorization, and accounting into independent processes, enabling fine-grained, command-by-command authorization for device management. Furthermore, TACACS+ encrypts the entire body of every packet (excluding only the standard TACACS+ header), protecting sensitive administrative data and commands in transit. Finally, TACACS+ operates over connection-oriented TCP on standard port 49.

Step-by-Step Solution

1
Analyze the functional decoupling requirement
TACACS+ decouples authentication, authorization, and accounting, allowing separate authorization checks per command. RADIUS combines authentication and authorization into one workflow.
Administrative device access control requires per-command authorization checks after successful user authentication.
2
Evaluate the encryption scope requirement
TACACS+ encrypts the entire body of the packet (all AAA parameters and payload data). RADIUS encrypts only the password field within the Access-Request frame.
Full payload encryption ensures sensitive administrative command strings sent over the wire are protected from eavesdropping.
3
Verify transport protocol and port requirements
TACACS+ relies on TCP port 49 for connection-oriented delivery. RADIUS primarily uses connectionless UDP ports 1812 (Authentication) and 1813 (Accounting).
Connection-oriented TCP guarantees reliable delivery and session tracking for AAA operations.

Key Concept

RADIUS vs TACACS+ AAA Architectural Differences
Question 787Question

During a post-incident audit of a multi-tier data center environment, an engineer discovers that inter-VLAN routing failure and unexpected high-availability failovers occurred because secondary database nodes were improperly connected to trunk ports missing native VLAN tags, while hosts were statically configured with individual physical interface IP addresses rather than shared gateway abstractions. Additionally, technicians were unable to physically locate the corresponding patch panel switchports during the outage due to missing physical layout records. Which of the following documentation components and procedural updates must be corrected and updated to fully remediate this environment? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Update the logical network topology diagram to clearly reflect VLAN IDs, subnet boundaries, 802.1Q trunking parameters, and the First Hop Redundancy Protocol (FHRP) Virtual IP (VIP) addresses used for default gateways.; Update physical rack elevation diagrams and cable run schedules detailing switch U-positions, patch panel port mappings, and cable labeling standards across all equipment racks.

Answer

The correct updates are updating the logical network topology diagram (to document VLANs, subnets, trunking parameters, and FHRP Virtual IPs) and updating the physical rack elevation diagrams and cable run schedules (to detail U-positions, patch panel mappings, and port labeling).
To fully document and remediate the environment, both logical and physical documentation must be updated. Updating the logical network topology diagram ensures that VLAN IDs, subnets, trunk configurations, and FHRP Virtual IP (VIP) addresses are accurately mapped for layer 2/3 operations and high-availability failover. Updating physical rack elevation diagrams and cable run schedules ensures that physical hardware positioning, patch panel terminations, and cable runs can be quickly audited and traced during physical maintenance.

Step-by-Step Solution

1
Analyze the logical network issues in the scenario.
Identified misconfigurations involving VLAN tags, trunking, subnets, and default gateway failovers.
Resolving logical routing and gateway issues requires an accurate logical network topology diagram showing subnets, trunk ports, and FHRP Virtual IPs.
2
Analyze the physical layer issues in the scenario.
Identified missing records for switchport and patch panel physical locations during troubleshooting.
Resolving physical tracing issues requires detailed rack elevation diagrams and cable run schedules mapping switch U-positions and patch panel ports.
3
Evaluate and eliminate distractors.
Rejected assigning physical interface IPs as default gateways, using unencrypted SNMPv1, and selecting simple continuity testers for distance-to-fault measurements.
These options introduce security vulnerabilities, break gateway redundancy, or misapply physical testing tools.

Key Concept

Differentiation between logical network topology diagrams and physical rack/cabling documentation
Estimated Time:3m 0s
Question 788Question

A network operations team is auditing the event management and polling security parameters on core routers to meet strict regulatory compliance mandates. The regulatory framework requires two key controls: all remote system logging messages must be delivered using a connection-oriented protocol that guarantees transport-layer encryption, and all telemetry polling performed by network management stations must enforce both cryptographic user authentication and packet payload encryption.

Which of the following configuration steps must the administrator perform to satisfy these auditing mandates? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure Syslog forwarding to use TCP port 6514 with Transport Layer Security (TLS) encapsulation.; Configure SNMPv3 polling using the authPriv security level.

Answer

The administrator must enable Syslog forwarding over TCP port 6514 with TLS encapsulation and configure SNMPv3 using the authPriv security level.
Enabling Syslog over TCP port 6514 with TLS encapsulation satisfies the requirement for connection-oriented, encrypted system log transport. Configuring SNMPv3 with the authPriv security level satisfies the requirement for authenticated and encrypted network telemetry polling.

Step-by-Step Solution

1
Analyze transport and security requirements for remote log collection.
Standard Syslog operates over UDP port 514 without native encryption. To enforce reliable connection-oriented transport and payload confidentiality, Syslog over TLS (TCP port 6514) must be specified.
RFC 5425 defines secure Syslog transmission over TLS using TCP port 6514.
2
Analyze security models for SNMP network management polling.
SNMPv1 and SNMPv2c use cleartext community strings. SNMPv3 introduces three User-based Security Model (USM) levels: noAuthNoPriv (no auth, no encryption), authNoPriv (authentication, no encryption), and authPriv (authentication and encryption).
Only authPriv satisfies the mandate requiring both identity verification and payload privacy/encryption.

Key Concept

Secure Network Logging (Syslog over TLS) and SNMPv3 Security Models (authPriv)
Question 789Question

An enterprise deployment connects dual-homed application servers to two separate top-of-rack access switches using LACP (IEEE 802.3ad) NIC teaming for link redundancy, while two core routers run Virtual Router Redundancy Protocol (VRRP) to provide default gateway resiliency. Following a network migration, users report intermittent traffic loss during router failover tests, and LACP bundles on the servers fail to form properly. Which TWO of the following technical misconfigurations or architectural oversights are the primary causes of these issues?

Select all that apply

Show answer & explanation

Answer: LACP was configured across two independent, non-stacked access switches without implementing Multi-Chassis Link Aggregation (mLAG) or switch stacking between them.; Host default gateway addresses were statically configured with the physical IP address of the primary router instead of the VRRP Virtual IP (VIP) address.

Answer

The primary causes are that LACP was configured across separate standalone switches without Multi-Chassis Link Aggregation (mLAG), and host default gateways were set to the physical router IP address rather than the VRRP Virtual IP (VIP).
LACP requires a single logical switch plane (achieved via switch stacking or multi-chassis link aggregation / mLAG) when bundling interfaces connected across physical switch chassis. Furthermore, VRRP requires endpoints to target the shared Virtual IP (VIP) address rather than physical interface IP addresses to maintain seamless default gateway failover.

Step-by-Step Solution

1
Analyze the LACP negotiation failure across distinct access switches.
Standard LACP (IEEE 802.3ad) requires all bundle members to terminate on a single logical control plane. Split connections across non-stacked standalone switches fail to establish a combined aggregation bundle without mLAG or stacking technology.
LACP Control Protocol Data Units (LACPDUs) from different physical switches carry different system IDs, preventing unified link group formation.
2
Evaluate host gateway reachability during VRRP failover.
Hosts configured with the physical interface IP of the primary router continue directing traffic to that specific hardware address during failover, causing connection drops.
VRRP relies on hosts sending default gateway traffic to the shared Virtual IP (VIP) and virtual MAC address so the backup router can take over seamlessly upon primary device failure.

Key Concept

Multi-Chassis Link Aggregation (mLAG) requirements and First Hop Redundancy Protocol (FHRP) Virtual IP host configuration.
Question 790Question

A security analyst needs to monitor critical database servers for unauthorized local file integrity modifications and zero-day memory exploits that lack known attack signatures. Which security solution best addresses these requirements?

Show answer & explanation

Answer: Host-based Intrusion Detection System (HIDS) utilizing anomaly-based detection logic

Answer

A Host-based Intrusion Detection System (HIDS) utilizing anomaly-based detection logic is the correct solution.
Deploying a Host-based Intrusion Detection System (HIDS) with anomaly-based detection directly monitors local operating system activities, including system call sequences and file integrity changes on the server. Anomaly-based logic compares real-time host activity against an established baseline of normal operations, allowing it to detect unknown zero-day attacks that do not match existing signatures.

Step-by-Step Solution

1
Identify the scope of monitoring required by the scenario.
The requirement specifies host-level monitoring, including local file modifications and process execution, which requires endpoint visibility rather than network link visibility.
Network-based systems (NIDS/NIPS) analyze packet streams across network interfaces and cannot monitor internal host OS processes or local file integrity.
2
Determine the appropriate detection mechanism for zero-day threats.
Anomaly-based (behavioral) detection establishes a baseline of normal system activity and flags deviations, making it effective against unknown threats.
Signature-based detection requires pre-existing pattern definitions, which are unavailable for novel zero-day attacks.
3
Synthesize placement and mechanism to select the correct technology.
Combining host-level placement (HIDS) with behavioral detection (anomaly-based) satisfies both monitoring requirements.
HIDS operates on the host OS to observe file modifications and kernel calls while anomaly detection identifies novel exploits.

Key Concept

HIDS vs NIDS/NIPS placement and Anomaly-based vs Signature-based detection mechanisms
Question 791Question

A network security architect is reviewing the deployment of centralized authentication protocols across a global enterprise network infrastructure. The architecture requires separate handling for administrative access to network edge routers and user authentication for 802.1X wireless access. Which TWO of the following statements correctly evaluate the operational and security characteristics of RADIUS and TACACS+ in this deployment?

Select all that apply

Show answer & explanation

Answer: TACACS+ decouples authentication, authorization, and accounting, allowing granular command-by-command authorization rules for administrative device management over TCP port 49.; RADIUS combines authentication and authorization into a single functional framework, utilizing UDP transport for network access control such as 802.1X enterprise Wi-Fi.

Answer

The correct statements are that TACACS+ decouples AAA functions for granular administrative command authorization over TCP port 49, and RADIUS combines authentication/authorization into a single framework using UDP transport for network access control.
TACACS+ is designed for administrative device management because it separates AAA components, allowing independent authorization of individual CLI commands, and uses TCP port 49 with full payload encryption. RADIUS is designed for network access control (such as 802.1X enterprise Wi-Fi), combining authentication and authorization responses while utilizing UDP ports 1812/1813.

Step-by-Step Solution

1
Analyze AAA functional separation requirements
TACACS+ separates authentication, authorization, and accounting into distinct operations, enabling command-level authorization. RADIUS combines authentication and authorization in access-accept/reject responses.
Administrative device management requires granular command authorization, whereas network access control requires unified pass/fail authentication.
2
Evaluate transport layer protocols and port assignments
TACACS+ relies on TCP port 49 for reliable connection-oriented transport. RADIUS relies on UDP ports 1812 (authentication) and 1813 (accounting) for low-overhead packet delivery.
Transport protocol selection determines connection handling and port specifications in AAA deployment.
3
Verify encryption boundary characteristics
TACACS+ encrypts the entire body of the packet following the header, whereas RADIUS only encrypts the password attribute in the Access-Request packet.
Distinction in payload encryption is critical for evaluating security posture during administrative sessions versus user network access.

Key Concept

AAA Protocol Differentiation (RADIUS vs TACACS+)
Question 792Question

A network engineer is upgrading an enterprise log auditing and monitoring infrastructure. Corporate compliance policies require that all network event logs sent to the central server, as well as SNMP polling traffic, provide confidentiality and integrity verification in transit. Which of the following configuration choices should the engineer implement to fulfill these security requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Encapsulate Syslog traffic using Transport Layer Security (TLS) over TCP port 6514.; Configure SNMPv3 using the authPriv security level for remote device monitoring.

Answer

The secure configuration requires using Syslog over TLS (TCP port 6514) and configuring SNMPv3 with the authPriv security level.
Securing log messages and network telemetry in transit requires protocols that support cryptographic encryption and message integrity. Encapsulating Syslog via TLS over TCP port 6514 secures log records from unauthorized interception. For SNMP polling, SNMPv3 under the authPriv security model ensures authentication and payload encryption.

Step-by-Step Solution

1
Evaluate secure Syslog transport protocols
Standard Syslog over UDP port 514 transmits messages in unencrypted plaintext. Secure log aggregation requires Syslog over TLS using TCP port 6514.
Compliance policies demand encryption and tamper-evident transport for event logs.
2
Evaluate SNMP versions and security levels
SNMPv1 and SNMPv2c use cleartext community strings without payload encryption. SNMPv3 with authPriv provides both authentication and privacy (encryption).
authPriv satisfies both confidentiality and integrity requirements for SNMP telemetry.

Key Concept

Secure Network Logging and SNMP Audit Protocols
Question 793Question

A network technician is preparing to update the operating system firmware on several enterprise switches. Which of the following actions should the technician take prior to applying the update in the production environment? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a complete backup of device configuration files and existing firmware images.; Evaluate the firmware update within an isolated sandbox or staging environment.

Answer

The technician should create a complete backup of switch configuration files and current firmware images, as well as evaluate the update inside an isolated sandbox or staging environment before live deployment.
Proper patch maintenance requires creating full backups of configuration files and existing software images to ensure rollback capability, while staging the update in an isolated environment prevents untested code from causing live network outages.

Step-by-Step Solution

1
Identify fundamental risk-mitigation steps in the network patch lifecycle.
Recognize that establishing a known baseline backup and testing in a safe environment are mandatory pre-patch steps.
Backing up configurations guarantees a rollback path, while staging tests verify patch stability before affecting production traffic.

Key Concept

Pre-deployment patch management lifecycle and risk mitigation practices
Question 794Question

A network technician is deploying high availability for enterprise servers connected to redundant access switches. Which TWO of the following technologies or mechanisms directly provide link aggregation and adapter redundancy at Layer 2?

Select all that apply

Show answer & explanation

Answer: Link Aggregation Control Protocol (LACP) configured on connected switch ports to bundle physical links into a single logical channel.; NIC Teaming (network interface card bonding) enabled on the servers to combine multiple physical adapters into a redundant group.

Answer

The correct options are Link Aggregation Control Protocol (LACP) on switch ports and NIC Teaming on server network adapters.
Link Aggregation Control Protocol (LACP) aggregates physical switch links into a single logical EtherChannel, maintaining network connectivity if an individual cable or port fails. NIC Teaming joins multiple server network adapters together in active-active or active-passive arrangements to shield the server from single network card failures.

Step-by-Step Solution

1
Identify the high availability requirements specified in the scenario
The requirement specifies Layer 2 link aggregation and network adapter redundancy between host servers and access switches.
High availability at the physical and data link layers requires redundancy for both the host interfaces and the switch port channels.
2
Evaluate technologies that bundle physical links between switches and servers
LACP combines multiple physical switch ports into a single logical channel, providing link failover and aggregate bandwidth. NIC Teaming binds multiple server network interface cards into a fault-tolerant group.
Together, LACP and NIC Teaming eliminate single cable or network adapter points of failure at Layer 2.

Key Concept

Layer 2 High Availability and Link Aggregation (LACP & NIC Teaming)
Question 795Question

A network security administrator is assessing the centralized access control deployment for an enterprise infrastructure. The administrator needs to evaluate the architectural and transport differences between RADIUS and TACACS+ protocols. Which of the following statements correctly distinguish TACACS+ from RADIUS? (Select TWO).

Select all that apply

Show answer & explanation

Answer: TACACS+ encrypts the complete body of the transmission payload, whereas RADIUS encrypts only the user password attribute.; TACACS+ decouples authentication, authorization, and accounting into distinct interactions, whereas RADIUS combines authentication and authorization into a single service exchange.

Answer

The correct statements are that TACACS+ encrypts the complete packet payload while RADIUS encrypts only the password attribute, and TACACS+ decouples AAA functions whereas RADIUS combines authentication and authorization into a single exchange.
TACACS+ provides full-payload encryption past the header and modular separation of AAA functions, making it ideal for granular switch/router administration. RADIUS encrypts only the password attribute and combines authentication and authorization into unified transaction packets.

Step-by-Step Solution

1
Analyze encryption boundaries for both protocols
TACACS+ encrypts the entire packet payload (except the header), whereas RADIUS encrypts only the user password field.
Security protocol specifications define different payload encryption scopes for TACACS+ versus RADIUS.
2
Evaluate AAA architectural separation
TACACS+ separates authentication, authorization, and accounting into granular, independent transactions, while RADIUS merges authentication and authorization into unified response messages.
TACACS+ was engineered specifically for granular device administration, requiring separate authorization queries per command.
3
Verify transport layer protocols and port numbers
TACACS+ uses TCP port 49, whereas RADIUS uses UDP ports 1812 (authentication) and 1813 (accounting).
This confirms that options suggesting RADIUS uses TCP 49 or TACACS+ uses UDP 1812/1813 are incorrect.

Key Concept

RADIUS vs TACACS+ Protocol Architecture and Security Boundaries
Question 796Question

A network security team is designing a monitoring strategy for a high-frequency trading subnetwork and a remote branch office. The trading network requires absolute zero added latency on active traffic paths while maintaining detection capability for novel, unknown protocol exploits. Meanwhile, the branch office needs comprehensive visibility into mirrored VLAN traffic captured by a switch SPAN port. Which of the following design choices correctly fulfill these architecture and detection requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Deploying an out-of-band Network Intrusion Detection System (NIDS) connected to a switch SPAN port allows passive traffic analysis without introducing packet processing delays to active network streams.; Implementing anomaly-based detection mechanisms enables the security system to identify zero-day attacks by detecting deviations from an established baseline of normal network behavior.

Answer

The correct architectural choices are deploying an out-of-band NIDS via SPAN ports for zero-latency passive visibility and implementing anomaly-based detection mechanisms to identify unknown zero-day threats.
Out-of-band NIDS connected via SPAN or network TAP receives duplicate frames, providing passive security monitoring without inserting processing overhead into active network paths. Furthermore, anomaly-based (or behavior-based) detection compares current traffic against historical baseline metrics, enabling the identification of unknown zero-day attacks that lack established signatures.

Step-by-Step Solution

1
Analyze deployment topology requirements for low-latency network segments
In-band (inline) NIPS devices inspect packets synchronously and introduce queueing latency, whereas out-of-band NIDS passively analyzes frame copies mirrored via SPAN/TAP without impacting inline latency.
Out-of-band placement preserves original packet timing on high-frequency trading lines.
2
Evaluate detection engine logic for identifying unknown attacks
Signature-based detection matches traffic against known malicious patterns and fails against zero-day threats. Anomaly-based detection compares real-time traffic to a baseline profile to flag unexpected behavior.
Novel zero-day exploits lack pre-defined signature patterns and require statistical anomaly detection.

Key Concept

Passive out-of-band IDS placement versus inline IPS prevention, and anomaly-based baseline detection versus signature matching.
Question 797Question

A network security administrator is deploying a dual centralized AAA architecture to support both network infrastructure management and 802.1X wireless user authentication. Which TWO of the following statements accurately distinguish the operational and transport properties of TACACS+ and RADIUS in this implementation?

Select all that apply

Show answer & explanation

Answer: TACACS+ encrypts the entire packet body following the header and operates over TCP port 49 for administrative sessions.; RADIUS encrypts only the password attribute in the payload and operates over UDP transport protocols.

Answer

The correct statements are that TACACS+ encrypts the entire packet body following the header while operating over TCP port 49, and RADIUS encrypts only the password attribute in the payload while operating over UDP transport protocols.
TACACS+ encrypts the complete packet payload (excluding the TACACS+ header) and uses TCP port 49 for reliable connection-oriented administrative tracking. RADIUS combines authentication and authorization, encrypting only the password field within the Access-Request packet and using UDP for connectionless transport.

Step-by-Step Solution

1
Analyze TACACS+ transport and cryptographic boundaries
TACACS+ uses TCP port 49 and encrypts the entire packet body (payload), separating authentication, authorization, and accounting.
Administrative device management requires granular command authorization and reliable TCP connections.
2
Analyze RADIUS transport and cryptographic boundaries
RADIUS uses UDP (ports 1812/1813) and encrypts only the password attribute, combining authentication and authorization.
RADIUS is designed for high-throughput network access control where packet overhead is minimized.
3
Evaluate options against verified protocol characteristics
Identify the two accurate statements describing TACACS+ full payload encryption over TCP and RADIUS password-only encryption over UDP.
Matches the verified operational standards for both AAA protocols.

Key Concept

AAA Framework Protocol Differentiation (RADIUS vs. TACACS+)
Estimated Time:1m 30s
Question 798Question

A network administrator is designing a high-availability infrastructure for a datacenter rack connected to dual switches and redundant edge routers. The design must support link aggregation across physical network interfaces on dual-homed servers while also ensuring rapid Layer 3 gateway failover if an upstream WAN link drops. Which TWO of the following technical configurations should the administrator implement to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Configure Link Aggregation Control Protocol (LACP) in conjunction with multi-chassis or stacked switches to provide dual-homed NIC redundancy and combined link capacity.; Enable interface tracking and preemption within a First Hop Redundancy Protocol (FHRP) on the primary edge router to trigger gateway failover if the upstream uplink fails.

Answer

The administrator should implement Link Aggregation Control Protocol (LACP) across stacked or multi-chassis switches for server NIC redundancy, and enable FHRP interface tracking with preemption on the edge routers for upstream-aware gateway failover.
Combining LACP across stackable/multi-chassis switches provides resilient, bandwidth-aggregated Layer 2 connections for servers. Paired with FHRP interface tracking and preemption on Layer 3 edge routers, the network achieves both switch link redundancy and dynamic gateway failover triggered by upstream connection drops.

Step-by-Step Solution

1
Identify the requirement for Layer 2 link aggregation and switch redundancy for dual-homed servers.
Selected LACP combined with switch stacking/MCLAG to bundle multiple physical interfaces into a logical link across separate physical switch chassis.
LACP provides dynamic link aggregation and fault tolerance, while switch stacking/MCLAG permits cross-switch link termination without creating Layer 2 loops.
2
Identify the requirement for upstream-aware Layer 3 gateway redundancy.
Selected FHRP interface tracking and preemption.
Interface tracking lowers the active router's priority upon WAN interface failure, and preemption allows the secondary router to take over the active Virtual IP (VIP) role dynamically.

Key Concept

Multi-Layer High Availability & FHRP Tracking
Estimated Time:1m 30s
Question 799Question

An enterprise network engineering team is designing a high-security log forwarding and auditing infrastructure across multi-site edge routers. The compliance policy mandates that event log forwarding to the centralized SIEM must guarantee transport reliability and payload encryption, while active remote device telemetry queries must enforce both cryptographic user authentication and data payload privacy encryption. Which of the following configuration choices and protocols satisfy these requirement criteria? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Forward Syslog events using TCP port 6514 encapsulated with Transport Layer Security (TLS); Configure SNMPv3 polling and trap generation using the authPriv security model

Answer

The correct configurations are forwarding Syslog events over TCP port 6514 using TLS encapsulation, and implementing SNMPv3 using the authPriv security model.
Secure log aggregation requiring encrypted and reliable transport must use Syslog over TLS on TCP port 6514. Device telemetry requiring both authentication and encryption mandates SNMPv3 at the authPriv security level.

Step-by-Step Solution

1
Analyze log transport encryption and reliability requirements
Syslog over TLS utilizes TCP port 6514 to deliver connection reliability, message integrity, and payload encryption.
Standard UDP port 514 lacks guaranteed delivery and transport-layer encryption capabilities.
2
Evaluate SNMPv3 security levels for authentication and privacy
SNMPv3 authPriv enforces both cryptographic user authentication (HMAC-SHA/MD5) and packet privacy encryption (AES/DES).
The authNoPriv level provides authentication without encryption, failing the requirement for payload privacy.

Key Concept

Secure Logging and SNMP Security Models
Question 800Question

A network team is preparing a maintenance window to perform a software operating system update on a high-availability core switch cluster operating in an active/standby state. Which TWO actions must the engineers execute to maintain service continuity and ensure rapid recovery if an issue arises?

Select all that apply

Show answer & explanation

Answer: Export current configuration files off-box and verify the software image file integrity against vendor checksums prior to installation; Execute a rolling upgrade by applying the software patch to the standby node first, verifying system stability, and triggering a controlled failover

Answer

The correct procedures are exporting configuration files off-device and verifying image checksums prior to installation, as well as performing a rolling upgrade by patching the standby node first before failing over active traffic.
Safe software maintenance on high-availability network infrastructure requires a rolling upgrade strategy. Patching the standby node first maintains active traffic processing on the primary node. Confirming image hashes and exporting configuration backups off-device guarantees that corrupted code is not flashed and that device state can be restored immediately in a recovery scenario.

Step-by-Step Solution

1
Perform pre-upgrade baseline data preservation and image integrity checks.
System configurations are backed up to secure external storage and software images are confirmed non-corrupt.
If an upgrade fails or corrupts system state, having an external configuration backup and confirmed binary hash guarantees rollback feasibility.
2
Apply software update to the standby cluster node.
The passive node is updated while active network traffic continues uninterrupted on the primary node.
Sequential node updating maintains overall cluster operational readiness and prevents network-wide outages.
3
Verify secondary node health and initiate controlled failover.
Active traffic shifts seamlessly to the newly updated node, allowing the remaining node to undergo software maintenance.
Controlled switchover tests the stability of the upgraded image under live load while preserving fault tolerance.

Key Concept

High-Availability Rolling Upgrades and Pre-Maintenance Validation
PreviousPage 40 / 112Next
All practice questions — CompTIA Network+ | Examkin