All practice questions

2237 questions

Question 761Question

Match each centralized authentication protocol or framework to its corresponding architectural design and operational characteristic.

Click a left item, then click its matching right item

Items

TACACS+
RADIUS
Kerberos
EAP-TLS

Matches

Show answer & explanation

Answer

TACACS+ matches the description of TCP port 49 operation with full-payload encryption and separated AAA services. RADIUS matches UDP ports 1812/1813 with combined authentication/authorization and password-only encryption. Kerberos matches the Key Distribution Center (KDC) utilizing Ticket-Granting Tickets (TGT). EAP-TLS matches mutual authentication requiring X.509 certificates on both supplicant and server.
Each protocol is accurately matched to its structural specifications: TACACS+ encrypts the entire body over TCP 49 with decoupled AAA components; RADIUS combines authentication and authorization over UDP 1812/1813 with password-only encryption; Kerberos leverages a KDC and Ticket-Granting Tickets for domain single sign-on; EAP-TLS enforces mutual authentication using dual X.509 certificates.

Step-by-Step Solution

1
Evaluate TACACS+ architectural properties
Identified TCP port 49 transport, modular AAA functional separation, and full payload body encryption.
TACACS+ separates authentication, authorization, and accounting to allow granular command authorization on network devices while securing all packet data over a reliable stream.
2
Evaluate RADIUS architectural properties
Identified UDP ports 1812/1813 transport, combined authentication/authorization packets, and password-only encryption.
RADIUS is designed for network access AAA (e.g., dial-in, VPN, 802.1X), coupling authentication and authorization responses while leaving username and accounting headers unencrypted.
3
Evaluate Kerberos authentication mechanics
Identified Key Distribution Center (KDC), Authentication Server (AS), Ticket Granting Server (TGS), and Ticket-Granting Ticket (TGT) workflow.
Kerberos relies on ticket exchange protocols authenticated via a central KDC to facilitate passwordless domain single sign-on.
4
Evaluate EAP-TLS protocol requirements
Identified mutual authentication mandatory requirement for client and server X.509 certificates.
Unlike password-based EAP methods (such as PEAP or EAP-FAST), EAP-TLS establishes a TLS tunnel based on mutual certificate verification.

Key Concept

AAA Centralized Framework Protocols and EAP Authentication Characteristics
Question 762Question

A network administrator needs to configure centralized log collection for core enterprise switches. Security policies require that all log messages sent across the network must be encrypted in transit. Which protocol and port combination should the administrator configure to securely transport Syslog data?

Show answer & explanation

Answer: Syslog over TLS on TCP port 6514

Answer

Syslog over TLS on TCP port 6514
The option specifying Syslog over TLS on TCP port 6514 correctly identifies the industry-standard protocol (RFC 5425) and port assignment for sending centralized, encrypted log messages across network infrastructure.

Step-by-Step Solution

1
Identify the logging transport requirement
The requirement specifies encrypted transmission of log messages to a central server.
Security compliance requires confidentiality in transit.
2
Select the secure version of the Syslog protocol
Syslog over TLS (RFC 5425) provides encryption and authentication.
Standard Syslog over UDP port 514 operates in plain text without encryption.
3
Verify standard port assignments
Syslog over TLS standard destination port is TCP 6514.
IANA assigns TCP port 6514 specifically for secure Syslog message delivery.

Key Concept

Secure Syslog (TLS) Port and Protocol Identification
Estimated Time:45s
Question 763Question

In enterprise network operations and security auditing, different logging protocols, severity levels, and monitoring frameworks fulfill distinct roles. Match each network auditing or logging component on the left with its correct operational description on the right.

Click a left item, then click its matching right item

Items

Syslog Facility
Syslog Severity Level 3 (Error)
NetFlow / IPFIX Export
SNMPv3 authPriv

Matches

Show answer & explanation

Answer

Syslog Facility matches the item describing software application/subsystem categorization. Syslog Severity Level 3 (Error) matches the item describing error conditions impacting single operational features. NetFlow / IPFIX Export matches the item describing statistical traffic telemetry without full payloads. SNMPv3 authPriv matches the item describing HMAC authentication alongside payload encryption.
Each logging and monitoring component is paired precisely with its defining technical function: Syslog Facility categorizes originating source subsystems; Syslog Severity 3 represents non-fatal error conditions; NetFlow exports conversation metadata without full payload contents; and SNMPv3 authPriv ensures both authentication and payload confidentiality.

Step-by-Step Solution

1
Analyze the Syslog architecture fields.
Identify that Syslog messages separate origin (Facility) from importance (Severity). Facility represents the originating subsystem.
Facility codes categorize log sources like auth, daemon, or user-defined local facilities.
2
Evaluate standard Syslog numerical severity levels.
Determine that Level 3 corresponds to 'Error', which denotes non-fatal subsystem errors.
Numerical severity ranks from 0 (Emergency) to 7 (Debug); Level 3 indicates operational component errors.
3
Differentiate network traffic monitoring protocols.
Map NetFlow/IPFIX to flow-based metadata collection rather than full packet capture or log event messages.
NetFlow aggregates connection tuples (IPs, ports, protocols, counters) for audit trails and performance baselining.
4
Verify SNMP Security Models under SNMPv3.
Confirm authPriv enforces both cryptographic authentication and privacy encryption.
authNoPriv provides authentication without encryption, while authPriv adds symmetric payload encryption.

Key Concept

Network Logging & Telemetry Mechanisms (Syslog Facilities/Severities, NetFlow vs. Syslog, and SNMPv3 Security Models)
Question 764Question

Match each high availability technology or redundancy concept on the left to its correct operational description on the right.

Click a left item, then click its matching right item

Items

HSRP
VRRP
LACP
Active-Passive Clustering

Matches

Show answer & explanation

Answer

HSRP pairs with Cisco-proprietary first-hop redundancy protocol providing a virtual gateway IP address to local network hosts; VRRP pairs with Open-standard first-hop redundancy protocol enabling multiple routers to share a virtual gateway IP address; LACP pairs with IEEE standard protocol (802.3ad/802.1AX) that dynamically aggregates multiple physical network links into a single logical channel; Active-Passive Clustering pairs with Redundancy configuration where a secondary standby device monitors the primary device and assumes processing only upon primary node failure.
HSRP is a Cisco-proprietary default gateway protocol, VRRP is an open-standard default gateway protocol, LACP provides Layer 2 multi-link aggregation under IEEE standards, and Active-Passive clustering designates a standby node for failover capability.

Step-by-Step Solution

1
Differentiate between First Hop Redundancy Protocols based on vendor ownership.
Match HSRP to Cisco-proprietary gateway redundancy and VRRP to open-standard gateway redundancy.
HSRP was created by Cisco, while VRRP was standardized by the IETF for vendor-agnostic deployments.
2
Identify link aggregation protocols operating at Layer 2.
Match LACP to the IEEE 802.3ad/802.1AX standard for combining physical switch ports.
LACP bundles physical interfaces into a unified logical link to increase bandwidth and provide link failover.
3
Identify system failover operational modes.
Match Active-Passive Clustering to standby failover behavior.
In active-passive setups, the passive node remains idle regarding traffic processing until a failover event occurs.

Key Concept

First Hop Redundancy Protocols and Link Aggregation Concepts
Question 765Question

A network security engineer is evaluating security monitoring controls and deployment topologies across an enterprise network. Match each intrusion detection or prevention architecture on the left with its defining operational characteristic or monitoring mechanism on the right.

Click a left item, then click its matching right item

Items

Passive Out-of-Band NIDS (via SPAN/TAP)
Inline In-Band NIPS
Host-based Intrusion Detection System (HIDS)
Behavior/Anomaly-based Detection Engine

Matches

Show answer & explanation

Answer

Passive Out-of-Band NIDS matches with processing copied network frames without introducing path latency; Inline In-Band NIPS matches with sitting directly in the active data transit stream to drop or reset malicious packets; Host-based IDS matches with monitoring local OS system call tables, memory, file integrity, and host logs; Behavior/Anomaly-based Detection matches with establishing a baseline of standard network traffic and triggering alerts upon statistical deviations.
Passive out-of-band NIDS receives mirrored data from SPAN/TAPs to evaluate traffic without introducing latency or failure risks. Inline NIPS sits in the direct network flow to block threats in real time. Host-based IDS monitors internal OS events, registry keys, and file modifications on an endpoint. Anomaly-based detection compares current behavior against learned historical baselines.

Step-by-Step Solution

1
Analyze deployment topology for network-level passive monitoring.
Identify that SPAN/TAP connections feed duplicated traffic to passive devices (out-of-band NIDS), adding zero operational latency and eliminating single-point-of-failure risks.
Out-of-band systems receive copies of frames rather than handling active inline routing or switching.
2
Analyze deployment topology for active prevention.
Identify that inline NIPS devices sit in-band across the wire to intercept traffic flow and execute immediate packet drops or TCP resets.
Real-time prevention requires physical or logical placement in the direct data path.
3
Distinguish between network-level and host-level inspection scopes.
Identify that HIDS inspects endpoint-specific elements such as system call tables, memory segments, and file system integrity rather than transit wire packets.
Host software agents focus on OS-level anomalies and system modification indicators.
4
Evaluate detection engine mechanisms.
Identify that anomaly/behavior-based mechanisms require initial training baseline periods to measure live statistical deviations, as opposed to static pattern matching used in signature-based systems.
Anomaly detection compares real-time telemetry against established statistical averages.

Key Concept

Intrusion Detection and Prevention Systems (IDS/IPS) Architectural Topologies and Detection Methods
Question 766Question

An enterprise network operations team needs to update the firmware across core network infrastructure following a vendor security disclosure. Place the standard operational steps of the patch management lifecycle in the correct order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct operational sequence is: 1) Evaluate security advisories and inventory, 2) Test the patch in an isolated lab environment, 3) Submit a change request to the CAB and schedule a maintenance window, 4) Perform device configuration backups, and 5) Deploy during the maintenance window and audit performance post-installation.
The standard patch management process follows a logical lifecycle designed to minimize operational risk: vulnerability discovery and asset inventory, sandbox lab testing, formal Change Advisory Board (CAB) approval with scheduled maintenance windows, pre-deployment device configuration backups, and production deployment paired with post-patch auditing.

Step-by-Step Solution

1
Vulnerability Assessment and Discovery
Scope of affected devices and priority level are determined.
Administrators must discover which network assets are affected before taking operational action.
2
Lab Staging and Validation
Patch side effects are observed without risking production infrastructure.
Sandbox testing provides empirical performance metrics and validates rollback procedures.
3
Change Management Approval
The Change Advisory Board approves the deployment schedule.
Organizational governance requires authorized authorization and scheduled downtime notification.
4
Pre-Patch Baseline Backup
Device state and configuration files are archived safely.
Backups ensure immediate rollback capability if installation issues arise.
5
Production Deployment and Post-Audit
Software updates are applied and operational integrity is verified.
Completes the patch lifecycle while confirming normal network operations have resumed.

Key Concept

Patch Management Lifecycle Operations
Estimated Time:1m 30s
Question 767Question

Match each high availability or redundancy protocol/mechanism on the left with its precise operational characteristic or implementation detail on the right.

Click a left item, then click its matching right item

Items

GLBP (Gateway Load Balancing Protocol)
LACP (Link Aggregation Control Protocol - IEEE 802.1AX)
Stateful Session Synchronization
VRRP (Virtual Router Redundancy Protocol)

Matches

Show answer & explanation

Answer

GLBP matches the mechanism utilizing an Active Virtual Gateway (AVG) to assign virtual MAC addresses to Active Virtual Forwarders (AVFs). LACP matches dynamic link bundling using LACPDUs with system priorities and operational keys. Stateful Session Synchronization matches replicating active connection and NAT tables across peer links. VRRP matches the open-standard FHRP employing virtual MAC addresses in the format 00-00-5E-00-01-XX.
GLBP uses an Active Virtual Gateway (AVG) to assign different virtual MAC addresses to Active Virtual Forwarders (AVFs) so multiple routers actively forward default gateway traffic. LACP automatically negotiates multi-link aggregation groups using LACPDUs and system priorities. Stateful Session Synchronization mirrors active connection tables across HA nodes so dynamic sessions survive failover without disconnecting users. VRRP is the open-standard FHRP that designates a Master router using the standardized IANA virtual MAC structure 00-00-5E-00-01-XX.

Step-by-Step Solution

1
Analyze GLBP operational mechanics
Identify that GLBP provides gateway load balancing by using an AVG to respond to ARP requests with distinct virtual MACs assigned to AVFs.
GLBP is unique among FHRPs because it active-active balances traffic across multiple gateways rather than operating purely in standby mode.
2
Analyze LACP link aggregation standards
Identify that LACP (IEEE 802.1AX / 802.3ad) uses LACPDUs, system IDs, port priorities, and keys to negotiate trunk formation.
LACP ensures both ends of an aggregated link agree on parameters prior to forwarding traffic.
3
Analyze stateful failover concepts
Identify that stateful session synchronization maintains active user sessions during device failover by replicating TCP state tables and NAT entries.
Without stateful synchronization, failover is stateless and requires hosts to re-establish existing TCP connections.
4
Analyze VRRP standards and addressing
Identify that VRRP is an open-standard protocol using the reserved virtual MAC range 00-00-5E-00-01-XX.
HSRP uses 0000.0c07.acXX (HSRPv1) or 0000.0c9f.fXXX (HSRPv2), whereas VRRP uses the IANA OID 00-00-5E-00-01-XX.

Key Concept

High Availability, Gateway Redundancy Protocols, and Link Aggregation Mechanics
Question 768Question

An enterprise organization needs to mitigate a newly disclosed critical vulnerability affecting the operating system of its core infrastructure network devices. To ensure business continuity and adhere to standardized patch management governance, place the following operational steps in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for enterprise patch management is: 1) Verify hash integrity and test in a staging lab environment, 2) Submit an RFC with rollback plans and test results for CAB approval, 3) Capture full configuration backups and operational baselines on target devices, 4) Apply the patch to production devices during the maintenance window, and 5) Conduct post-installation verification testing and log auditing.
Proper operational maintenance follows a rigorous lifecycle: sandbox testing and binary integrity verification must occur first to generate test evidence. Next, an RFC accompanied by test results and rollback steps is submitted for change control approval. Once approved, engineers capture pre-deployment device backups and baseline metrics immediately before applying the patch within the scheduled maintenance window. Finally, post-deployment testing and audit log reviews ensure system health before closing the change ticket.

Step-by-Step Solution

1
Verify and test the patch in isolation.
Patch integrity is confirmed via cryptographic hashes and functional behavior is validated in staging without impacting production.
Deploying unverified code directly to production risks network-wide outages.
2
Obtain change management authorization.
The Change Advisory Board reviews staging data, risk factors, and rollback procedures to approve the change schedule.
Enterprise governance mandates formal approval and verified rollback strategies prior to system alterations.
3
Establish safety baselines and backups.
Current running configurations and performance baselines are archived immediately before patch execution.
If an anomaly occurs during installation, technical teams must be able to restore the device to its exact pre-patch state.
4
Execute patch installation in production.
The software update is applied during the designated low-impact maintenance window.
Limiting implementation to approved maintenance windows minimizes user impact.
5
Perform post-patch audit and validation.
Control plane and data plane metrics are confirmed to match or exceed pre-patch baselines, and event logs show no abnormal errors.
Functional validation confirms that the update successfully remediated the issue without introducing unintended secondary errors.

Key Concept

Structured Patch Management Lifecycle and Change Management Procedures
Estimated Time:3m 0s
Question 769Question

A network administrator is evaluating deployment topologies for intrusion security controls within a corporate network architecture. Which of the following statements accurately distinguish a passive Network Intrusion Detection System (NIDS) from an inline Network Intrusion Prevention System (NIPS)? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: NIDS utilizes out-of-band traffic monitoring via SPAN or TAP ports, whereas NIPS is deployed in-band directly along the network transmission path.; NIPS can actively block or drop malicious network traffic inline, whereas NIDS primarily logs events and sends administrator alerts without stopping the traffic flow.

Answer

The correct statements are that NIDS utilizes out-of-band monitoring via SPAN/TAP ports while NIPS is deployed in-band, and NIPS can actively block or drop malicious traffic inline while NIDS primarily logs events and generates alerts.
The statement regarding NIDS using out-of-band SPAN/TAP monitoring while NIPS sits in-band is correct because NIDS receives passive copies of packets while NIPS processes live traffic directly in the network path. The statement noting that NIPS actively drops malicious traffic while NIDS generates alerts is also correct because inline placement enables real-time prevention, whereas passive placement limits response to alerting.

Step-by-Step Solution

1
Analyze placement topology differences between NIDS and NIPS.
Identify that NIDS is passive and receives mirrored traffic out-of-band via SPAN or TAP ports, whereas NIPS is physically positioned in-band (inline) along the traffic flow.
Placement topology dictates whether a system inspects traffic passively or inline.
2
Evaluate response mechanism capabilities between detection and prevention systems.
Confirm that NIPS can perform active inline mitigations such as dropping packets or resetting connections, while NIDS produces passive notifications and log entries.
Detection systems notify administrators of threats without disrupting traffic, while prevention systems actively stop threats.

Key Concept

Placement topology and response capabilities of NIDS (out-of-band, passive alerting) versus NIPS (in-band, active inline prevention).
Question 770Question

A network engineer is configuring infrastructure devices to forward event logs to a centralized Security Information and Event Management (SIEM) server for auditing. Which TWO of the following configurations will ensure that log events are accurately correlated and securely transmitted across the network? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Synchronize system clocks across all network devices using Network Time Protocol (NTP).; Forward Syslog messages over TLS using TCP port 6514.

Answer

The correct configurations are synchronizing system clocks across devices using Network Time Protocol (NTP) and forwarding Syslog messages over TLS using TCP port 6514.
Centralized logging and auditing rely on two main pillars: accurate timeline reconstruction and secure log transport. Synchronizing system clocks via NTP ensures all log events share a consistent timestamp for SIEM event correlation. Transporting Syslog messages over TLS using TCP port 6514 encrypts audit logs in transit to protect sensitive network data.

Step-by-Step Solution

1
Identify the requirement for accurate event correlation in log auditing.
Network Time Protocol (NTP) provides consistent time stamping across all devices, enabling precise sequence reconstruction during log analysis.
Without unified time sources, timestamps from different devices will mismatch, preventing accurate incident correlation.
2
Identify the requirement for secure transmission of log data.
Syslog over TLS (TCP port 6514) establishes a cryptographically secure transport channel.
Cleartext protocols like standard UDP 514 Syslog or SNMPv1 expose auditing details to network sniffing.

Key Concept

Centralized Log Security, Event Correlation, and Transport Encryption
Question 771Question

A network security administrator is deploying a Network Intrusion Detection System (NIDS) connected to a hardware network TAP at the main datacenter perimeter. Which of the following operational characteristics and limitations apply specifically to this out-of-band NIDS architecture? (Select TWO).

Select all that apply

Show answer & explanation

Answer: The deployment introduces zero processing latency to the active transit traffic flow.; The system cannot directly block or drop malicious packets before they reach their destination host.

Answer

The out-of-band NIDS deployment introduces zero processing latency to live transit traffic and cannot directly drop or block malicious packets inline before they reach their destination.
Out-of-band NIDS sensors receive duplicate frames via SPAN or network TAPs. Because the sensor operates outside the live packet path, it does not add latency to transit traffic, but it also lacks the ability to prevent or drop malicious packets inline before they arrive at their destination.

Step-by-Step Solution

1
Analyze the deployment architecture described in the scenario.
The scenario specifies a passive out-of-band NIDS receiving mirrored traffic from a hardware network TAP.
Placement topology dictates whether the system functions inline (in-band) or passively (out-of-band).
2
Evaluate the latency impact of passive monitoring.
Since packets are copied by the TAP and sent to the NIDS in parallel, original transit frames are not delayed.
Out-of-band sensors process copies of packets rather than sitting directly in the active data path.
3
Evaluate active prevention capabilities of passive monitoring.
Because the sensor sits outside the live path, it can generate alerts or send TCP resets, but it cannot drop inline packets in real time.
Inline drop actions require in-band NIPS placement directly between the source and destination.

Key Concept

Out-of-Band NIDS Architecture vs. Inline NIPS Placement
Question 772Question

A network security team needs to implement intrusion monitoring across a high-throughput enterprise core switch link carrying latency-sensitive voice and transactional traffic. The security policy mandates that the monitoring deployment must not introduce latency, perform inline packet modification, or risk creating a single point of network failure if the monitoring service fails. Which deployment architecture and system type best meets these requirements?

Show answer & explanation

Answer: A Network Intrusion Detection System (NIDS) deployed out-of-band using a switch SPAN/mirror port

Answer

A Network Intrusion Detection System (NIDS) deployed out-of-band using a switch SPAN/mirror port
The option specifying a Network Intrusion Detection System (NIDS) deployed out-of-band using a switch SPAN or mirror port is correct because out-of-band passive deployments inspect duplicate copies of network packets. This architecture guarantees that monitoring operations do not introduce serialization latency into live real-time streams and ensures that a failure of the NIDS sensor will not disrupt production network traffic.

Step-by-Step Solution

1
Analyze the operational constraints required by the enterprise network scenario
Identified three critical constraints: zero added latency, no active packet dropping/modification, and zero risk of network disruption upon monitoring device failure.
Understanding architectural constraints determines whether an in-band (inline) or out-of-band (passive) solution is appropriate.
2
Evaluate system placement options (in-band prevention vs out-of-band detection)
In-band (inline) IPS devices sit directly in the traffic flow path and can introduce latency or drop connection traffic if overloaded. Out-of-band (passive) IDS devices monitor mirrored copy traffic from a SPAN or TAP port.
Passive out-of-band deployment ensures live network throughput is completely unaffected by sensor hardware failures or processing bottlenecks.
3
Select the system type and deployment mechanism matching all requirement criteria
A NIDS deployed passively via a SPAN port satisfies network-wide traffic visibility while adhering to zero-latency and high-availability operational requirements.
NIDS provides signature-based and anomaly detection on network traffic copies without sitting directly in the active forwarding path.

Key Concept

Passive Out-of-Band NIDS vs Inline NIPS Placement
Estimated Time:1m 30s
Question 773Question

A senior network security engineer is updating the centralized management architecture for core enterprise switches and firewalls. Enterprise compliance mandates that all administrative communications must completely separate authentication processes from command-by-command authorization rules, while encrypting the entire packet payload during transit across the management network. Which authentication protocol and transport configuration must the engineer deploy on the network access servers to satisfy all compliance parameters?

Show answer & explanation

Answer: TACACS+ utilizing TCP port 49

Answer

TACACS+ utilizing TCP port 49 satisfies all corporate compliance parameters by encrypting the full packet body payload and separating authentication and authorization functions.
TACACS+ natively operates over TCP port 49 and is designed specifically for device access control. It completely separates Authentication, Authorization, and Accounting, allowing granular per-command administrative permissions. Furthermore, TACACS+ encrypts the full body of each packet, meeting the stringent compliance rules specified in the scenario.

Step-by-Step Solution

1
Analyze requirement for AAA functional decoupling
TACACS+ separates Authentication, Authorization, and Accounting into distinct functions, permitting per-command authorization checks, whereas RADIUS combines Authentication and Authorization into a single response.
The scenario explicitly specifies that command-by-command authorization rules must be decoupled from authentication.
2
Evaluate payload encryption capabilities
TACACS+ encrypts the entire body payload of every packet following the header, whereas RADIUS encrypts only the password attribute in the request body.
The compliance directive mandates full PDU payload protection rather than partial credential-only obscuration.
3
Identify correct transport layer protocol and port number
TACACS+ operates natively over TCP port 49 to provide connection-oriented reliability for device administration.
Selecting TCP port 49 aligns with the RFC specification for TACACS+.

Key Concept

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

A network administrator implements a First Hop Redundancy Protocol (FHRP) across two core routers to maintain continuous gateway accessibility for end-user workstations. Which IP address must be assigned as the default gateway on the workstations to achieve seamless failover?

Show answer & explanation

Answer: The virtual IP address assigned to the redundancy group

Answer

The virtual IP address assigned to the redundancy group
The correct option is the shared virtual IP address. First Hop Redundancy Protocols present a single virtual gateway IP and virtual MAC address to the local network segment. When end-user workstations use the virtual IP as their default gateway, active/standby router state changes occur transparently without breaking client connectivity.

Step-by-Step Solution

1
Identify the purpose of First Hop Redundancy Protocols (FHRPs) such as HSRP or VRRP.
FHRPs allow multiple physical routers to collaborate and present a single virtual router identity to local hosts.
This abstract layer allows client devices to send default gateway traffic to a consistent virtual address regardless of individual physical router status.
2
Determine the proper workstation TCP/IP network configuration for default gateways in an FHRP environment.
Workstations must point to the shared Virtual IP (VIP).
If the active physical router fails, the standby physical router assumes control of the Virtual IP, keeping default gateway traffic flowing without requiring changes on client endpoints.

Key Concept

FHRP Virtual Gateway IP Configuration
Question 775Question

A network administrator is upgrading an enterprise monitoring infrastructure to comply with strict auditing standards. The current deployment experiences dropped log packets across congested WAN links and fails security audits due to cleartext management traffic across untrusted boundaries. Which protocol and transport configuration best satisfies the requirements for reliable, cryptographically protected log aggregation and secure device polling?

Show answer & explanation

Answer: Configure Syslog using TCP port 6514 with TLS framing for event logs, and implement SNMPv3 with the authPriv security level for device polling.

Answer

Configure Syslog using TCP port 6514 with TLS framing for event logs, and implement SNMPv3 with the authPriv security level for device polling.
The correct response pair combines TCP port 6514 for Syslog over TLS with SNMPv3 running at the authPriv security level. Syslog over TLS uses TCP to guarantee log transmission across lossy or congested links while encrypting log contents. SNMPv3 authPriv enforces both cryptographic user authentication and payload privacy (encryption), fully satisfying the auditing and security objectives.

Step-by-Step Solution

1
Analyze transport reliability requirements for log aggregation
UDP Syslog (port 514) is connectionless and prone to packet drops during congestion; TCP provides reliable transport, while TCP port 6514 standardizes secure Syslog over TLS.
Meeting compliance requires guaranteed delivery and confidentiality across untrusted WAN links.
2
Evaluate SNMP security models for secure device auditing
SNMPv3 offers three security levels: noAuthNoPriv (no auth/privacy), authNoPriv (auth without encryption), and authPriv (both auth and encryption).
Only authPriv ensures that polled device data and configuration parameters are encrypted over the network.
3
Synthesize the protocol requirements
The target deployment must use Syslog over TCP port 6514 (TLS) alongside SNMPv3 configured with authPriv.
This combination guarantees both reliable, encrypted log transport and fully encrypted polling.

Key Concept

Secure Network Logging & Auditing Protocols (Syslog TLS & SNMPv3 Security Levels)
Estimated Time:2m 0s
Question 776Question

A network operations team is updating an organization's logging infrastructure across multiple branch office firewalls to meet strict compliance mandates. Currently, event log messages are transmitted across an untrusted WAN link using default unencrypted Syslog over UDP. The audit team requires that all remote log transmissions be encrypted to protect sensitive header and message contents, while also establishing a reliable, connection-oriented session. Which of the following transport configuration changes will meet these requirements?

Show answer & explanation

Answer: Migrate Syslog forwarding to use Transport Layer Security (TLS) over TCP port 6514.

Answer

Migrate Syslog forwarding to use Transport Layer Security (TLS) over TCP port 6514.
The correct option specifies migrating Syslog forwarding to use Transport Layer Security (TLS) over TCP port 6514. Secure Syslog (RFC 5425) uses TLS to encrypt log messages in transit across untrusted networks and relies on TCP to guarantee connection-oriented, ordered log delivery.

Step-by-Step Solution

1
Identify the encryption and transport reliability requirements specified in the scenario.
The mandate requires encrypted transmission across an untrusted WAN link and a reliable, connection-oriented transport protocol.
Default Syslog operates over UDP port 514, which lacks both delivery guarantees and transport encryption.
2
Evaluate secure Syslog standards and default port assignments.
Syslog over TLS utilizes TCP port 6514, satisfying both connection reliability via TCP and payload encryption via TLS.
RFC 5425 defines Syslog over TLS using TCP port 6514 as the standard mechanism for secure, reliable log forwarding.

Key Concept

Syslog Security and Secure Transport Protocols (Syslog over TLS / TCP 6514)
Question 777Question

A network security administrator is upgrading the centralized logging and management framework across core network switches to adhere to a strict zero-trust audit policy. The updated policy mandates that all forwarded event logs and SNMP polling queries must guarantee both cryptographic payload confidentiality (encryption) and data integrity/authentication during transit across administrative subnets. Which configuration combination should the network security administrator implement to meet all audit compliance requirements?

Show answer & explanation

Answer: Configure Syslog to use TLS encapsulation over TCP port 6514, and enable SNMPv3 with the authPriv security level.

Answer

Configure Syslog to use TLS encapsulation over TCP port 6514, and enable SNMPv3 with the authPriv security level.
To satisfy zero-trust requirements for confidentiality and authentication in network auditing, both event message transport and management query protocols must encrypt their payloads. Syslog over TLS utilizes TCP port 6514 to provide encrypted log delivery, while SNMPv3 configured at the authPriv level enforces cryptographic message authentication alongside payload encryption (privacy).

Step-by-Step Solution

1
Evaluate the protocol and transport requirements for centralized logging confidentiality.
Standard Syslog over UDP 514 and plain TCP 514 lack encryption. Secure Syslog defined in RFC 5424/5425 utilizes Transport Layer Security (TLS) over TCP port 6514 to encrypt log messages in transit.
Cryptographic protection of event log traffic requires an encrypted transport tunnel like TLS.
2
Evaluate the security level options for SNMP remote management.
SNMPv1 and SNMPv2c send community strings in plaintext. SNMPv3 offers three security levels: noAuthNoPriv (no authentication, no encryption), authNoPriv (authentication via HMAC-MD5/SHA, no encryption), and authPriv (authentication via HMAC and privacy/encryption via AES/DES).
Only SNMPv3 authPriv satisfies both authentication and encryption (confidentiality) requirements.
3
Synthesize the compliant logging and auditing controls.
Combining Syslog over TLS (TCP 6514) with SNMPv3 authPriv meets all criteria for encrypted log transport and authenticated, encrypted device management.
This combined posture enforces full end-to-end data integrity and payload confidentiality for administrative network traffic.

Key Concept

Secure Logging Transport (Syslog-TLS Port 6514) and SNMPv3 Security Levels (authPriv)
Estimated Time:2m 0s
Question 778Question

A network administrator receives a vendor security advisory requiring a critical operating system patch to be applied to perimeter firewalls. Before deploying this update to live production systems, which of the following operational practices represents the best approach to validate stability and prevent unplanned downtime?

Show answer & explanation

Answer: Deploy and evaluate the software update within an isolated staging environment that mimics the production configuration.

Answer

Deploy and evaluate the software update within an isolated staging environment that mimics the production configuration.
Staging and testing patches in an isolated environment that replicates production topology ensures that software updates, hotfixes, and vendor patches do not introduce unforeseen routing issues, security gaps, or system instability before touching production traffic.

Step-by-Step Solution

1
Analyze patch management best practices for enterprise network devices.
Identified staging and lab testing as mandatory pre-deployment verification steps.
Direct deployment to live production systems without prior validation introduces unacceptable operational risk.
2
Evaluate risk mitigation strategies for software maintenance.
Confirmed that verifying functionality in an environment replicating production ensures dependencies and software defects are discovered safely.
Production environments require high availability, necessitating pre-deployment verification in an isolated mirror environment.

Key Concept

Patch Management Staging and Pre-Deployment Validation
Question 779Question

An enterprise data center utilizes two edge routers, Edge-1 and Edge-2, configured with Hot Standby Router Protocol (HSRP) to provide default gateway redundancy for internal LAN clients. Edge-1 is configured with an HSRP priority of 120, while Edge-2 is configured with the default priority of 100. Both routers connect to downstream switches via their LAN interfaces and to separate ISP providers via their WAN interfaces. During a line cut on Edge-1's WAN circuit, internal LAN clients report a complete loss of internet connectivity. Network monitoring shows that Edge-1 remains the active HSRP router and continues accepting LAN traffic. Which of the following is the most likely cause of this failover failure?

Show answer & explanation

Answer: HSRP interface tracking was not configured on Edge-1's WAN interface to decrement its priority upon link failure.

Answer

HSRP interface tracking was not configured on Edge-1's WAN interface to decrement its priority upon link failure.
The correct answer highlights the necessity of FHRP interface or object tracking. By default, HSRP only monitors the local interface where standby groups are configured. If an upstream WAN interface fails while the local LAN interface stays active, HSRP priority remains unchanged unless interface tracking is configured to decrement the priority below the standby router's priority.

Step-by-Step Solution

1
Analyze the HSRP state and network symptoms.
Edge-1 has a higher priority (120) than Edge-2 (100) and remains the active HSRP router despite losing its WAN interface.
By default, HSRP routers only monitor the operational state of the interface on which HSRP is running (the LAN interface).
2
Evaluate why Edge-1 did not yield the active role to Edge-2.
Because the LAN interface on Edge-1 remained operational, Edge-1 continued transmitting HSRP hellos with priority 120.
Without tracking the upstream WAN interface status, HSRP has no mechanism to know that outbound internet traffic through Edge-1 will be black-holed.
3
Identify the required feature to resolve upstream failover issues.
Configuring HSRP interface/object tracking on Edge-1 decrements its priority (e.g., by 30 points to 90) when the WAN link drops.
When Edge-1's priority drops below Edge-2's priority (100), preemption allows Edge-2 to seamlessly assume the active role.

Key Concept

FHRP Interface/Object Tracking
Estimated Time:2m 0s
Question 780Question

Match each core component of the AAA security framework to its corresponding network security function.

Click a left item, then click its matching right item

Items

Authentication
Authorization
Accounting

Matches

Show answer & explanation

Answer

Authentication matches with identity verification; Authorization matches with permission enforcement; Accounting matches with activity tracking and auditing.
Authentication establishes and confirms entity identity, Authorization controls accessible operations and services, and Accounting collects operational metrics and session logs for security audits.

Step-by-Step Solution

1
Analyze the function of Authentication in network access management.
Authentication verifies identity credentials.
Authentication is the first pillar of AAA, proving the identity of the entity requesting access.
2
Analyze the function of Authorization in network access management.
Authorization defines privileges and access bounds.
Once identity is proven, authorization enforces rules on what the entity is allowed to do.
3
Analyze the function of Accounting in network access management.
Accounting records session history and resource usage.
Accounting creates an audit trail of user activity and resource consumption.

Key Concept

AAA Framework Core Pillars
PreviousPage 39 / 112Next
All practice questions — CompTIA Network+ | Examkin