Network Operations

362 questions

Question 121Question

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

Click a left item, then click its matching right item

Items

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

Matches

Show answer & explanation

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

Patch Staging and Baseline Backups
Question 124Question

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

Click a left item, then click its matching right item

Items

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

Matches

Show answer & explanation

Answer

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

Step-by-Step Solution

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

Key Concept

High Availability and Gateway/Link Redundancy Protocols
Question 125Question

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Select all that apply

Show answer & explanation

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

Answer

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

Step-by-Step Solution

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

Key Concept

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

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

Show answer & explanation

Answer: SNMPv3 configured with authPriv

Answer

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

Step-by-Step Solution

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

Key Concept

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

A network administrator is investigating intermittent VoIP audio degradation across an enterprise WAN link connecting two branch offices. Telephony logs indicate elevated packet loss and jitter during peak operational hours. Corporate security policy dictates that all infrastructure monitoring must utilize encrypted payload data and cryptographic authentication to prevent packet interception on intermediate links. Additionally, the administrator must gather interface bandwidth utilization baselines alongside granular protocol flow analysis to isolate the source of network congestion. Which of the following protocol and security level combinations correctly fulfills both operational and security requirements?

Show answer & explanation

Answer: Configure SNMPv3 using the authPriv security level for interface metric polling, and deploy IPFIX to export traffic flow statistics for jitter analysis.

Answer

Configure SNMPv3 using the authPriv security level for interface metric polling, and deploy IPFIX to export traffic flow statistics for jitter analysis.
The correct option fulfills both requirements: SNMPv3 at the authPriv security level provides cryptographic authentication as well as payload encryption (privacy) using AES or DES, meeting the strict enterprise security mandate. Additionally, IPFIX (IP Flow Information Export) is an industry-standard protocol for analyzing flow data such as VoIP jitter, latency, and packet loss across WAN links.

Step-by-Step Solution

1
Analyze security policy requirements for SNMP device polling.
Identified that cryptographic authentication and payload encryption are mandatory for all management polling across untrusted WAN links.
Security mandates require privacy (encryption) in addition to authentication.
2
Evaluate SNMP version and security mode capabilities.
Determined SNMPv3 authPriv is the only mode providing both cryptographic authentication (SHA/MD5) and packet payload encryption (AES/DES).
SNMPv1 and SNMPv2c communicate in cleartext. SNMPv3 authNoPriv encrypts password hashes but leaves metrics payloads unencrypted.
3
Select the appropriate traffic monitoring mechanism for VoIP jitter and packet loss analysis.
Selected IPFIX (or NetFlow) for exporting connection-level flow records.
IPFIX/NetFlow captures flow-level telemetry necessary to identify application-specific performance issues such as VoIP jitter and bandwidth consumption.

Key Concept

SNMPv3 Security Levels and Network Flow Telemetry Integration
Question 131Question

A network administrator is preparing to apply a major firmware update to enterprise distribution switches following a vendor security advisory. Which TWO of the following actions should the administrator perform during the pre-deployment and staging phase to verify software integrity and minimize operational risk?

Select all that apply

Show answer & explanation

Answer: Verify the cryptographic hash of the downloaded firmware file against the vendor's published digest.; Test the firmware update in an isolated lab environment that mirrors the production device configuration.

Answer

The administrator should verify the cryptographic hash of the downloaded firmware file against the published digest and test the firmware update in an isolated lab environment mirroring production.
Verifying the cryptographic hash ensures file integrity and authenticity before deployment, while testing the patch in an isolated lab sandbox ensures that unexpected bugs or configuration incompatibilities are identified prior to affecting live production network services.

Step-by-Step Solution

1
Inspect the integrity of the downloaded image file.
Confirming the SHA-256 digest ensures the firmware image is uncorrupted and authentic.
Corrupted or malicious firmware binaries can render network switches completely unbootable.
2
Stage and validate the patch in a non-production environment.
Testing identifies unanticipated software bugs, protocol interactions, or failure modes safe from production impact.
Pre-deployment lab validation ensures stability and validates rollback scripts before scheduled maintenance windows.

Key Concept

Patch Verification and Staging Practices
Estimated Time:1m 30s
Question 132Question

An enterprise network architect is designing a comprehensive monitoring strategy for a multi-site WAN deployment. The solution must provide secure, continuous device health monitoring, granular flow visibility for bandwidth utilization analysis, and ensure compliance with strict zero-trust cryptographic requirements. Which of the following technical configurations and protocols should the architect deploy to satisfy these operational requirements? (Select TWO).

Select all that apply

Show answer & explanation

Answer: Deploy SNMPv3 configured with the authPriv security level using SHA-256 for authentication and AES-256 for payload encryption.; Export IPFIX or NetFlow v9 records from WAN edge routers to a centralized collector to evaluate traffic volumes, top talkers, and protocol distribution.

Answer

The architect should deploy SNMPv3 configured with authPriv (SHA/AES) for secure management polling and export IPFIX/NetFlow records for granular flow visibility.
Combining SNMPv3 with authPriv security ensures that device metrics and system health indicators are queried with cryptographic authentication (SHA-256) and payload privacy (AES-256). Supplementing SNMP polling with IPFIX/NetFlow protocol exports enables full-stack traffic flow analysis, identifying granular bandwidth consumption without subjecting network management data to cleartext interception.

Step-by-Step Solution

1
Analyze security and monitoring requirements
Identified the need for encrypted device management queries (zero-trust compliance) and flow-level bandwidth statistics.
SNMPv3 authPriv meets the cryptographic standard by providing authentication and payload encryption, unlike SNMPv1 or SNMPv2c.
2
Evaluate flow monitoring mechanisms for traffic statistics
Selected IPFIX/NetFlow export to track top talkers and link utilization.
Flow protocols analyze packet headers to report traffic volume by IP address, port, and protocol.
3
Identify misconfigurations and incorrect protocol roles in remaining choices
Eliminated SNMPv2c due to plain-text transmission and TCP transport misclassification; eliminated Syslog due to port/protocol role mismatch.
SNMP uses UDP port 161 for polling; Syslog uses UDP port 514 for message logging and cannot actively poll interface counters.

Key Concept

Enterprise Network Performance Monitoring Frameworks
Question 133Question

An IT department deploys Virtual Router Redundancy Protocol (VRRP) across two edge routers, Router-1 (Primary, physical IP 10.0.10.2/2410.0.10.2/24) and Router-2 (Backup, physical IP 10.0.10.3/2410.0.10.3/24), to provide default gateway redundancy for a LAN. The virtual router is assigned the Virtual IP (VIP) address 10.0.10.1/2410.0.10.1/24. During a planned failover test, Router-1 is powered down. Although Router-2 correctly assumes the active VRRP Master role, all client workstations on the LAN immediately lose access to external networks. Which of the following host misconfigurations is the most likely cause of this service disruption?

Show answer & explanation

Answer: The client workstations were statically configured with the physical IP address of Router-1 as their default gateway instead of the VRRP virtual IP address.

Answer

The client workstations were statically configured with the physical IP address of Router-1 as their default gateway instead of the VRRP virtual IP address.
For First-Hop Redundancy Protocols (such as VRRP, HSRP, or CARP) to provide seamless gateway failover, all host devices on the local network segment must use the shared Virtual IP (VIP) address (10.0.10.110.0.10.1) as their configured default gateway. If workstations are statically assigned the physical IP address of Router-1 (10.0.10.210.0.10.2), their gateway traffic is sent directly to Router-1's physical MAC address. When Router-1 powers off, Router-2 assumes the VIP, but the workstations continue attempting to send traffic to the offline physical IP address of Router-1, causing a total blackout for external connectivity.

Step-by-Step Solution

1
Analyze First-Hop Redundancy Protocol (FHRP) architecture requirements.
FHRP protocols like VRRP create a shared Virtual IP (VIP) and Virtual MAC address hosted by whichever router is currently acting as the Master.
Host machines must point their default gateway setting to the shared Virtual IP so traffic is transparently routed through whichever physical device holds the Master state.
2
Evaluate the symptom observed during the failover event.
Router-2 successfully became Master, but client traffic stopped flowing to external networks.
If clients were configured with the physical IP of Router-1 (10.0.10.210.0.10.2) as their default gateway, their traffic continues targeting Router-1's physical address directly, failing completely when Router-1 goes offline despite VRRP functioning properly on Router-2.

Key Concept

FHRP Virtual IP Assignment for High Availability
Estimated Time:1m 30s
Question 134Question

A network security administrator is configuring a centralized logging and monitoring architecture across enterprise core switches. The corporate compliance policy mandates that event logs are delivered reliably with connection-oriented transport and encrypted in transit, and that SNMP polling must provide both cryptographic user authentication and payload encryption. Which of the following protocol and port configurations must the administrator implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure Syslog to forward messages over TCP port 6514 using TLS encryption.; Configure SNMPv3 using the authPriv security level for device polling.

Answer

The administrator must configure Syslog over TCP port 6514 with TLS encryption for reliable, encrypted log transport, and configure SNMPv3 with authPriv for authenticated and encrypted telemetry polling.
Configuring Syslog over TCP port 6514 with TLS satisfies the requirement for reliable, encrypted log transport because TCP provides connection-oriented delivery and TLS encrypts data in transit. Configuring SNMPv3 with the authPriv security level satisfies the requirement for authenticated and encrypted telemetry because authPriv enforces cryptographic user authentication as well as payload encryption.

Step-by-Step Solution

1
Analyze the log forwarding compliance requirement.
Reliable connection-oriented transport with encryption requires TCP port 6514 (Syslog over TLS), whereas standard UDP port 514 lacks reliability and encryption.
TCP guarantees packet delivery via acknowledgments, and TLS encrypts the Syslog payload.
2
Analyze the SNMP monitoring security requirement.
SNMPv3 authPriv is the only SNMP configuration that provides both cryptographic user authentication and privacy (data encryption).
SNMPv1 and SNMPv2c rely on cleartext community strings, and SNMPv3 authNoPriv only provides authentication without encrypting the payload.

Key Concept

Centralized Network Audit Logging and Secure Telemetry Protocols
Question 135Question

A network administrator is designing a high-availability infrastructure for a mission-critical application server cluster. The design must provide Layer 2 link bandwidth aggregation with failure protection between switches, as well as Layer 3 active-standby gateway redundancy for host workstations on the local subnet. Which TWO of the following protocols or configurations should be deployed to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Implement Virtual Router Redundancy Protocol (VRRP) on the Layer 3 switches to present a shared Virtual IP (VIP) address as the default gateway.; Configure Link Aggregation Control Protocol (LACP / IEEE 802.3ad) on switch uplink ports to combine multiple physical links into a single logical trunk.

Answer

The correct choices are deploying Virtual Router Redundancy Protocol (VRRP) to provide a Virtual IP default gateway and configuring Link Aggregation Control Protocol (LACP) to combine physical links into a redundant logical trunk.
To satisfy both Layer 2 and Layer 3 high availability requirements, an administrator must combine link aggregation and default gateway redundancy. Deploying Virtual Router Redundancy Protocol (VRRP) allows multiple Layer 3 switches to share a single Virtual IP (VIP), ensuring host default gateway traffic seamlessly switches to a standby router upon hardware failure. Configuring Link Aggregation Control Protocol (LACP / IEEE 802.3ad) aggregates multiple physical interfaces between network switches into a single logical channel, providing both elevated throughput and automatic Layer 2 path redundancy if an individual cable or port fails.

Step-by-Step Solution

1
Identify the Layer 3 default gateway redundancy requirement.
Recognize that First Hop Redundancy Protocols (FHRPs) such as VRRP or HSRP present a unified Virtual IP (VIP) to end hosts, allowing dynamic active-standby gateway failover.
Endpoints configured with a shared VIP maintain gateway access even if one physical router interface fails.
2
Identify the Layer 2 link aggregation and bandwidth redundancy requirement.
Select LACP (IEEE 802.3ad) as the protocol designed to bundle multiple physical Ethernet links between switches into a single logical Ethernet channel.
LACP dynamically negotiates link aggregation, allowing traffic load balancing across links and automatic link recovery if a physical port drops.

Key Concept

High Availability and Redundancy Concepts
Question 136Question

A network administrator is preparing to modify the interface configurations on a primary distribution switch during a scheduled maintenance window. Which of the following steps should be completed BEFORE applying any configuration updates to ensure the switch can be rapidly restored if the change causes an unexpected outage?

Show answer & explanation

Answer: Create a complete backup of the current running configuration and verify a documented rollback plan.

Answer

Create a complete backup of the current running configuration and verify a documented rollback plan.
In standard network change management, saving a copy of the current functional configuration and establishing a tested rollback plan prior to making changes ensures that the system can be restored immediately to a working baseline if issues arise during implementation.

Step-by-Step Solution

1
Identify the primary objective of pre-change preparation in network change management.
Recognize that maintaining business continuity requires a recovery strategy before executing system modifications.
If an applied change causes network instability or service degradation, administrators need a verified path to return to the functional state.
2
Evaluate standard pre-implementation procedures.
Saving/backing up the active running configuration and reviewing the rollback plan guarantees that pre-change state files are secured.
Having an explicit rollback plan ensures zero guesswork during high-pressure outage recovery scenarios.

Key Concept

Pre-Implementation Rollback Planning & Baseline Backups
Estimated Time:45s
Question 137Question

A network administrator configures a First Hop Redundancy Protocol (FHRP) across two routers to ensure continuous network availability for clients on a local subnet. To enable seamless automated failover if the primary router fails, which address must be specified as the default gateway on the client workstations?

Show answer & explanation

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

Answer

The shared virtual IP (VIP) address assigned to the redundancy group
The correct answer specifies using the shared virtual IP address assigned to the redundancy group. First Hop Redundancy Protocols (FHRPs) present a single virtual IP and virtual MAC address to local clients. When clients point their default gateway to this virtual IP, traffic is dynamically forwarded by whichever physical router currently holds the active role.

Step-by-Step Solution

1
Identify the primary purpose of First Hop Redundancy Protocols (FHRP) such as HSRP or VRRP.
FHRP provides high availability by allowing multiple physical routers to share a single virtual default gateway address.
Client endpoints need a static default gateway setting that remains constant regardless of individual router hardware failures.
2
Determine the proper host network configuration for high availability.
Assign the Virtual IP (VIP) generated by the router redundancy group as the default gateway on all client workstations.
Traffic directed to the VIP is handled by the active router, and if that router fails, the standby router assumes control of the VIP seamlessly.

Key Concept

FHRP Virtual IP Gateway Configuration
Question 138Question

An enterprise network operations team must urgently remediate a newly published zero-day vulnerability affecting the routing protocol daemon across core Layer 3 switches. Which of the following procedures should the engineering team execute during the emergency maintenance window to preserve high availability and maintain change management compliance? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Stagger the patch installation across redundant switch pairs, updating the secondary node first while verifying control-plane stability before patching the primary node.; Export a full running-configuration file and verify an existing rollback system image copy in flash storage immediately prior to applying the software patch.

Answer

The engineering team must stagger the patch installation across redundant switch pairs—updating the secondary node first—and export running configurations alongside validating fallback system image copies in flash storage prior to patch execution.
Staggering software updates across redundant high-availability switch pairs preserves uninterrupted traffic flow while allowing the secondary device to be tested post-patch. Additionally, saving the current running configuration and confirming a valid rollback image in local storage ensures that the core switch can be restored quickly if the patch causes instability.

Step-by-Step Solution

1
Perform Pre-Patch Preparation and Backups
System configurations and baseline images are saved and verified for fast recovery.
Before executing software updates on critical infrastructure, administrators must secure current running configurations and confirm flash memory contains a functional rollback image.
2
Execute Staggered Redundant Deployment
High availability is maintained as active traffic is handled by the unpatched primary node while the secondary node updates.
Upgrading high-availability pairs sequentially prevents network-wide outages caused by unexpected patch failure or crash loops.
3
Perform Post-Patch Verification and Change Documentation
The update is validated, and change management records are updated post-maintenance.
Verifying control-plane stability and routing protocol convergence ensures full operational capability before completing change tickets.

Key Concept

High-Availability Staggered Patching and Rollback Verification
Question 139Question

An enterprise network engineering team is preparing a formal Request for Change (RFC) to modify core switch configurations and re-architect VLAN trunking across multiple datacenters. To adhere strictly to enterprise configuration and change management standards, which of the following components MUST be included within the submitted RFC prior to presenting it to the Change Advisory Board (CAB) for evaluation? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A detailed rollback plan specifying precise abort triggers and step-by-step restoration procedures; A comprehensive risk and impact assessment outlining potential service disruptions and mitigation controls

Answer

The Request for Change (RFC) must include a detailed rollback plan with explicit abort triggers and a comprehensive risk and impact assessment detailing service exposure.
A formal Request for Change (RFC) requires both a comprehensive risk and impact assessment to evaluate business risk and a detailed rollback procedure specifying exact conditions under which the change must be aborted and reverted.

Step-by-Step Solution

1
Analyze RFC documentation requirements
Identify mandatory sections required prior to CAB submission, including impact scope, business justification, maintenance window parameters, and contingency planning.
An RFC must provide complete visibility into the risk exposure and operational safety nets of a proposed network change.
2
Evaluate risk and impact assessment necessity
Confirm that an impact analysis evaluates how the change affects dependent applications, network links, and business operations during and after maintenance.
CAB members rely on risk assessments to approve scheduling windows and assess organizational risk.
3
Evaluate rollback plan necessity
Confirm that a rollback plan defines precise quantitative criteria (e.g., latency spikes, packet loss thresholds) for aborting the deployment and restoring original state.
Without a validated rollback plan, unforeseen errors in production could lead to prolonged unrecoverable outages.

Key Concept

Request for Change (RFC) Mandatory Components
Question 140Question

A network administrator is scheduling a critical vendor-issued software update for an organization's central network monitoring server. Before deploying the software update into the live environment, the administrator needs to ensure that the patch will not disrupt existing monitoring services or introduce system instability. Which of the following represents the most appropriate initial step in the patch management lifecycle to safely mitigate this risk?

Show answer & explanation

Answer: Deploying and validating the software update in an isolated staging environment that mirrors production

Answer

Deploying and validating the software update in an isolated staging environment that mirrors production is the correct initial step in the patch management process.
Testing patches in an isolated staging environment that accurately replicates the production environment is a mandatory standard in software maintenance. This practice permits administrators to verify compatibility, observe system performance, and identify software conflicts before any changes touch live services.

Step-by-Step Solution

1
Identify the core risk of patch deployment
Unvalidated patches can cause software incompatibility, service failures, or system crashes on production hosts.
Understanding operational risk requires pre-deployment verification.
2
Evaluate patch management lifecycle phases
The standard sequence follows discovery, lab testing/staging, approval, scheduled deployment, and post-installation auditing.
Staging allows engineers to safely observe software behavior without affecting production traffic or management tools.
3
Select the safest risk-mitigation action
Testing the update within a staging environment that mirrors production configurations catches dependencies and flaws early.
Staging validation confirms stability prior to authorizing production deployment windows.

Key Concept

Pre-deployment staging and lab testing in the patch management lifecycle
PreviousPage 7 / 19Next