Network Operations

362 questions

Question 221Question

An enterprise implements Virtual Router Redundancy Protocol (VRRP) across two core switches to provide high availability for client devices on a production VLAN. During a scheduled test, the primary switch is powered down, and network logs confirm that the standby switch successfully transitions to the master role. However, workstations on the VLAN immediately lose external network connectivity and fail to recover. Diagnostics show that VRRP advertisement packets and virtual MAC transitions operated correctly. Which of the following host misconfigurations is the most likely cause of this connectivity failure?

Show answer & explanation

Answer: Workstations were configured with the primary switch's physical interface IP address as their default gateway rather than the virtual IP address shared by the redundancy group.

Answer

Workstations were configured with the primary switch's physical interface IP address as their default gateway rather than the virtual IP address shared by the redundancy group.
For First Hop Redundancy Protocols (such as VRRP or HSRP) to provide seamless failover, client workstations must use the Virtual IP (VIP) assigned to the router redundancy group as their default gateway. When the active router fails, the standby router takes ownership of the Virtual IP and virtual MAC address. If workstations are statically or dynamically configured with the physical interface IP of the primary router instead of the VIP, their traffic continues targeting the failed physical interface, breaking outbound connectivity despite a successful protocol failover.

Step-by-Step Solution

1
Analyze First Hop Redundancy Protocol (FHRP) operational requirements.
FHRP protocols like VRRP and HSRP create a Virtual IP (VIP) and Virtual MAC address that are shared between redundant routers.
Client endpoints must send outbound traffic to the Virtual IP so that whichever router holds the active/master role can process the frames seamless to the client.
2
Evaluate the failure symptom described in the scenario.
The backup switch successfully assumed the Master role, meaning VRRP failover executed properly at the network layer.
If clients lose connectivity despite a successful VRRP failover, client traffic is directed to a specific physical hardware address rather than the virtual gateway.
3
Identify the client-side configuration error.
Clients configured with the physical interface IP of the primary router lose access when that specific device fails because their packets are sent to an inactive physical node rather than the virtual gateway.
Configuring hosts with the Virtual IP (VIP) ensures traffic is dynamically serviced by whichever switch currently holds the master role.

Key Concept

FHRP Virtual Gateway IP Configuration
Question 222Question

A network engineer is preparing a formal Request for Change (RFC) for an upcoming core router configuration update during a scheduled maintenance window. The Change Advisory Board (CAB) mandates that all high-impact RFCs include provisions to minimize operational downtime in case the update causes unforeseen service disruption. Which of the following components MUST be explicitly defined within the RFC to fulfill this mandatory requirement?

Show answer & explanation

Answer: A detailed rollback plan that includes specific back-out procedures and quantitative trigger thresholds.

Answer

A detailed rollback plan that includes specific back-out procedures and quantitative trigger thresholds.
A comprehensive rollback plan specifies the step-by-step procedures, timing constraints, and clear trigger conditions required to safely restore the network to its pre-change state if the modification introduces unexpected issues.

Step-by-Step Solution

1
Identify the core requirement of the Change Advisory Board (CAB) scenario.
The CAB requires a mechanism to mitigate risk and quickly restore service if the proposed change fails.
Standard change management protocol dictates that risk mitigation must be established prior to executing changes.
2
Evaluate the role of a rollback plan within an RFC.
A rollback plan specifies explicit steps, time limits, and trigger conditions to revert changes safety.
Having predefined rollback triggers prevents prolonged outages caused by troubleshooting failed changes live during a tight maintenance window.

Key Concept

Rollback Planning and Risk Mitigation in Change Management
Question 223Question

A network engineer is designing a high-availability network topology for a cluster of mission-critical application servers. The design requires active-active link aggregation, increased total bandwidth, and seamless link failover across two separate physical access switches without Spanning Tree Protocol (STP) placing any redundant interface into a blocking state. Which TWO of the following configurations or technologies must be implemented to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Configure Multi-Chassis Link Aggregation (MC-LAG) or Virtual Port Channel technology across the two access switches.; Enable IEEE 802.3ad Link Aggregation Control Protocol (LACP) in active mode on the server NIC team.

Answer

To achieve active-active link aggregation and redundant switch connectivity without STP blocking links, Multi-Chassis Link Aggregation (MC-LAG) must be configured on the switches alongside IEEE 802.3ad LACP on the server NIC team.
Implementing Multi-Chassis Link Aggregation (MC-LAG) across the access switch pair allows them to function as a single logical switch toward the servers. Combining this with IEEE 802.3ad LACP on the server NIC team enables active-active link aggregation, increased total throughput, and transparent link failover without Spanning Tree Protocol blocking redundant paths.

Step-by-Step Solution

1
Analyze the requirement for active-active link bundling spanning two physical switches.
Identified that standard LACP requires member links to terminate on a single logical device entity.
Unstacked standalone switches cannot coordinate control plane frames for a single standard LACP trunk.
2
Identify the switch technology that presents two physical switches as one logical switch.
Selected Multi-Chassis Link Aggregation (MC-LAG).
MC-LAG synchronizes control states between peer switches so downstream servers perceive them as a single LACP peer.
3
Identify the standard host protocol for dynamic link bundling.
Selected IEEE 802.3ad Link Aggregation Control Protocol (LACP) in active mode.
LACP manages frame distribution and link status monitoring dynamically across all active interfaces in the group.

Key Concept

Multi-Chassis Link Aggregation (MC-LAG) and Dynamic LACP Integration
Question 224Question

A network engineering team needs to update the primary TACACS+ server IP addresses and authentication keys across all wireless LAN controllers in an enterprise network. To adhere to organizational governance and minimize service disruption, the team must follow the standard change management lifecycle.

Place the following change management 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 chronological order begins with drafting and submitting the RFC, followed by obtaining CAB approval, validating the change in a lab environment, executing the deployment during the maintenance window, and concluding with post-implementation verification and documentation updates.
The standard change management lifecycle follows a strict sequential flow: Request initiation (RFC submission), Stakeholder review and approval (CAB approval), Technical validation (sandbox testing and rollback verification), Maintenance execution (production deployment), and Finalization (post-implementation review and baseline documentation update).

Step-by-Step Solution

1
Initiate the formal change process by drafting and submitting the RFC.
Comprehensive documentation of proposed scope, risks, and rollback steps is created.
All structured changes require formal tracking and initial documentation before review.
2
Submit the RFC to the CAB for review.
Formal authorization and scheduling alignment are secured from key stakeholders.
CAB approval ensures business continuity and prevents uncoordinated network changes.
3
Conduct pre-deployment testing in a lab or staging environment.
Potential syntax errors and rollback failures are identified prior to production exposure.
Testing validates the implementation plan and ensures the rollback procedure is effective.
4
Implement the change on production devices during the designated maintenance window.
The configuration updates are applied to the active network infrastructure.
Performing execution inside approved windows minimizes operational impact to end users.
5
Verify service functionality, perform PIR, and update baseline configuration records.
The change workflow is formally closed and network documentation reflects current state.
Post-implementation review and baseline updates ensure configuration drift is avoided and institutional records remain accurate.

Key Concept

Standard ITIL/CompTIA Change Management Lifecycle Stages
Question 225Question

During a routine maintenance window, a network administrator attempts to apply a firmware update to a core distribution switch at an unmanned remote facility. The update fails, corrupting the flash memory and placing the switch into a continuous boot loop, which brings down all VLAN interfaces and primary IP routing. The administrator needs to gain low-level CLI access to the switch's bootloader to restore the operating system image and must also be able to perform a hard power-cycle if the device hangs. Which out-of-band management configuration best fulfills these requirements?

Show answer & explanation

Answer: Connect the switch's RS-232 serial console port to an out-of-band terminal server paired with an independent cellular modem, and plug the switch's power cord into a remotely managed switched PDU.

Answer

Connecting the switch's serial console port to an out-of-band terminal server with a cellular modem and utilizing a remotely managed switched PDU is the optimal solution.
When a network switch suffers flash corruption and enters a continuous boot loop, all Layer 2 and Layer 3 in-band network interfaces become unreachable. Establishing out-of-band (OOB) management via a terminal server connected to the switch's serial console port provides direct CLI access to the ROMMON bootloader over an independent cellular path. Additionally, plugging the switch into a remotely managed switched PDU enables administrators to hard power-cycle the switch remotely without requiring on-site technical personnel.

Step-by-Step Solution

1
Analyze the failure scenario and impact on management channels.
Corrupted flash memory and continuous rebooting render all primary IP routing, VLAN interfaces, and in-band management protocols (SSH, Telnet, SNMP) unusable.
In-band access requires a running operating system and functional network protocol stack.
2
Identify the required access layer for ROMMON/bootloader recovery.
Direct serial console access (RS-232/RJ-45 console) is necessary to interact with low-level bootloader environments.
Bootloader environments bypass operating system networking stack requirements and output directly over serial interfaces.
3
Determine the alternate transport and power control mechanisms.
A terminal server connected to a cellular modem provides out-of-band path connectivity, while a switched Power Distribution Unit (PDU) enables remote power-cycling.
Cellular connectivity circumvents the down primary WAN/LAN links, and a switched PDU provides power control independent of the device's responsive state.

Key Concept

Out-of-Band (OOB) Management and Remote Infrastructure Access
Question 226Question

A network administrator is preparing to update SNMP community strings and syslog server configurations across all data center switches to align with an updated security baseline. The administrator has already drafted the configuration syntax and conducted a risk assessment identifying potential monitoring outages. Which of the following actions should the administrator perform next in accordance with formal change management procedures?

Show answer & explanation

Answer: Submit a formal Request for Change (RFC) to the Change Advisory Board (CAB) for authorization.

Answer

The administrator should submit a formal Request for Change (RFC) to the Change Advisory Board (CAB) for authorization.
In standard IT change management, once a configuration change is planned and its operational risks are assessed, the next mandatory step is to submit a Request for Change (RFC) for review and approval by the Change Advisory Board (CAB). Implementation and maintenance window scheduling can only occur after CAB approval.

Step-by-Step Solution

1
Analyze the current stage of the change management process.
The proposed technical changes have been drafted and initial risk assessment has been completed.
Establishing the current phase identifies the required next step in the standard change lifecycle.
2
Identify the required governance gate prior to implementation.
Formal authorization via a Change Advisory Board (CAB) review of the Request for Change (RFC) is necessary.
Standard operational procedures mandate that non-emergency production modifications undergo review and approval before scheduling execution windows.

Key Concept

Change Management Lifecycle and Authorization Procedures
Question 227Question

A network engineer is drafting a formal Request for Change (RFC) to update the configuration baseline and firmware of critical core switches in a financial datacenter. Which of the following elements must be included in the RFC documentation before submitting it for Change Advisory Board (CAB) review? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A detailed rollback plan specifying clear metric triggers and procedures for reverting to the previous baseline if implementation issues occur; A defined maintenance window detailing the exact scheduled timeframe, affected network services, and expected business impact

Answer

The essential RFC components are a detailed rollback plan with explicit failure triggers and a defined maintenance window specifying execution timeframes and business impact.
A formal Request for Change must include both an explicit rollback plan (with actionable triggers for reverting changes) and a scheduled maintenance window (defining the operational impact and exact time bounds). These elements allow the Change Advisory Board to assess operational risk accurately and ensure business continuity.

Step-by-Step Solution

1
Analyze standard components of a Request for Change (RFC) in formal network operations.
Identified that RFCs must contain risk assessments, execution steps, rollback plans, and maintenance schedules.
CAB approval depends on comprehensive documentation that evaluates risk and limits downtime exposure.
2
Evaluate the requirement for a rollback plan.
Determined that documenting specific triggers and reversion steps ensures rapid recovery in the event of an unexpected outage during deployment.
A change cannot proceed safely without a reliable method to return to the functional baseline configuration.
3
Evaluate the requirement for maintenance window scheduling.
Determined that defining the precise timeframe and scope of impact allows the organization to coordinate around planned maintenance.
Proper scheduling prevents unannounced outages for critical business functions.

Key Concept

Request for Change (RFC) Essential Elements
Question 228Question

A network administrator is designing an enterprise monitoring and telemetry strategy. Match each monitoring technology or protocol to its primary functional characteristic.

Click a left item, then click its matching right item

Items

SNMPv3 (authPriv)
NetFlow / IPFIX
Syslog
sFlow

Matches

Show answer & explanation

Answer

SNMPv3 (authPriv) matches with authenticated and encrypted MIB polling; NetFlow/IPFIX matches with flow table aggregation for IP conversation statistics; Syslog matches with unprompted event log messaging categorized by facility and severity; and sFlow matches with hardware packet sampling for scalable switch monitoring.
Each monitoring technology serves a distinct operational purpose: SNMPv3 with authPriv secures device MIB polling; NetFlow/IPFIX aggregates traffic into flow records; Syslog delivers centralized event messages organized by facility and severity; and sFlow provides hardware-level packet sampling for high-density switches.

Step-by-Step Solution

1
Analyze management querying protocols and security modes.
Identify SNMPv3 authPriv as the mode offering both authentication and payload privacy (encryption) when polling device MIB counters.
Security compliance standards require encrypted management queries to safeguard device telemetry.
2
Compare flow monitoring against packet sampling mechanisms.
Differentiate stateful flow tracking (NetFlow/IPFIX) which aggregates IP 5-tuple records from statistical packet sampling (sFlow) implemented in switch ASICs.
NetFlow builds connection records in cache, whereas sFlow samples raw packets to scale across wire-speed interfaces.
3
Identify event notification messaging protocols.
Recognize Syslog as an unprompted message transport mechanism using facility and severity codes to log status changes.
Syslog operates asynchronously when events occur rather than via periodic polling.

Key Concept

Network Telemetry and Performance Monitoring Protocols
Question 229Question

A network operations team is preparing to implement a major infrastructure modification involving the deployment of new interior routing protocol parameters across core enterprise routers. To ensure compliance with IT governance standards, what is the correct chronological sequence of steps the team must follow throughout the standard change management lifecycle?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for standard IT change management is: 1) Draft the RFC including risk analysis and rollback plans, 2) Submit the RFC for CAB review and approval, 3) Perform pre-implementation lab validation and schedule the maintenance window, 4) Execute the change during the maintenance window and perform post-change verification, and 5) Update baseline documentation and conduct a post-implementation review.
Standard ITIL and enterprise change management practices require defining scope and rollback procedures in an RFC prior to obtaining formal CAB authorization. Once approved, changes are validated in a sandbox and scheduled during a low-impact maintenance window. Following execution and verification in production, configuration baselines must be updated and a post-implementation review conducted to finalize the change.

Step-by-Step Solution

1
Initiate the change request by drafting the formal RFC.
Defines change scope, potential impact, implementation steps, and mandatory rollback procedures.
Clear documentation of scope and rollback steps is necessary before any review or testing can occur.
2
Submit the RFC to the Change Advisory Board (CAB).
Obtain formal authorization and assessment from business and technical stakeholders.
CAB approval ensures business continuity and prevents uncoordinated or conflicting production changes.
3
Conduct sandbox validation and schedule the maintenance window.
Verifies configuration syntax in lab conditions and minimizes user impact by selecting low-traffic operational windows.
Pre-deployment testing ensures implementation readiness prior to modifying live infrastructure.
4
Deploy configuration changes and execute verification testing.
Applies changes on production equipment during the approved window and confirms service functionality.
Immediate post-change testing confirms whether the change succeeded or if immediate rollback is triggered.
5
Update configuration baselines and complete the Post-Implementation Review (PIR).
Maintains accurate inventory/configuration records and documents lessons learned to close the change ticket.
Documentation and PIR ensure configuration management database (CMDB) accuracy and operational traceability.

Key Concept

Standard Change Management Lifecycle Phases
Estimated Time:1m 30s
Question 230Question

During a scheduled maintenance window, a senior administrator applies a new security configuration baseline to a core enterprise gateway. Immediately after applying the change, automated monitoring indicates that key database servers have lost network reachability due to an unintended blocking rule. Which of the following is the immediate next step the administrator should take according to standard change management procedures?

Show answer & explanation

Answer: Execute the documented rollback plan to return the core gateway to its pre-change functional baseline configuration.

Answer

The immediate next step is to execute the documented rollback plan to return the core gateway to its pre-change functional baseline configuration.
Executing the documented rollback plan is the required response when a change fails post-implementation testing. Reverting to the pre-change configuration baseline restores production service immediately without introducing unvetted configuration drift.

Step-by-Step Solution

1
Assess post-implementation validation results
Identified unexpected loss of database server reachability caused by the newly applied baseline configuration.
Post-implementation testing confirms that the change failed validation criteria.
2
Determine appropriate lifecycle procedure
Recognize that service outage triggers the predefined rollback conditions specified in the Request for Change (RFC).
Standard change management procedures require reverting failed changes immediately to minimize operational downtime.
3
Initiate rollback execution
Revert device configuration to the verified baseline taken prior to the maintenance window.
Restores full network connectivity and service baseline functionality before conducting root-cause analysis in a non-production environment.

Key Concept

Rollback Execution Trigger and Change Management Lifecycle
Estimated Time:1m 30s
Question 231Question

Following a compliance audit, a network engineer must establish centralized performance polling for hardware metrics including CPU utilization, memory usage, and interface throughput across core enterprise routers. The organization's security policy strictly mandates that all monitoring telemetry communications must enforce cryptographic user authentication and encrypt all payload data in transit to prevent eavesdropping. Which protocol and security level combination should the engineer implement to satisfy these requirements?

Show answer & explanation

Answer: SNMPv3 configured with the authPriv security level

Answer

SNMPv3 configured with the authPriv security level
SNMPv3 with authPriv (Authentication and Privacy) provides both cryptographic authentication and full payload encryption. This ensures that SNMP polling requests for core metrics are authenticated and that telemetry data in transit cannot be read by unauthorized packet sniffers.

Step-by-Step Solution

1
Identify the performance monitoring mechanism required.
System metric polling (CPU, memory, bandwidth) requires a structured management protocol like SNMP rather than an event logging protocol like Syslog.
SNMP provides structured OID polling capabilities suited for device health telemetry.
2
Evaluate the security requirements specified in the scenario.
The requirements demand both cryptographic user authentication and payload encryption of traffic in transit.
Security mandates require protection against unauthorized polling access and eavesdropping.
3
Select the SNMP version and security level that satisfies both requirements.
SNMPv3 with authPriv (Authentication and Privacy) provides HMAC authentication and AES/DES payload encryption.
authNoPriv lacks encryption, noAuthNoPriv lacks both, and SNMPv2c sends plain-text community strings without security.

Key Concept

SNMPv3 Security Levels and Telemetry Security
Estimated Time:1m 15s
Question 232Question

A network administrator is setting up a performance monitoring and telemetry strategy across an enterprise network that supports real-time voice communications and core infrastructure devices. The design requires secure polling of switch hardware metrics alongside precise measurement of packet delay variability for voice streams. Which of the following configuration options and metric analysis practices should the administrator implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Implement SNMPv3 configured with the authPriv security level to ensure both cryptographic authentication and payload encryption during switch metric polling.; Monitor jitter metrics using IPFIX or NetFlow flow records transported via UDP to assess packet arrival time variation across real-time voice streams.

Answer

The correct selections are implementing SNMPv3 with the authPriv security level for encrypted hardware polling, and monitoring jitter metrics using IPFIX or NetFlow flow records over UDP to evaluate delay variation in voice streams.
Configuring SNMPv3 with authPriv satisfies enterprise security standards by authenticating the session and encrypting metric payloads. Additionally, tracking jitter metrics via IPFIX/NetFlow transported over UDP enables network engineers to diagnose delay variation affecting latency-sensitive traffic such as VoIP.

Step-by-Step Solution

1
Identify the security requirements for infrastructure telemetry.
SNMPv3 authPriv is required because it adds cryptographic authentication and privacy (data encryption), whereas legacy versions (SNMPv1/v2c) transmit data in plain text.
Enterprise monitoring baselines demand protection against eavesdropping and unauthorized command injection.
2
Select the appropriate performance metric and transport method for real-time voice quality analysis.
Jitter measures the variability in packet arrival intervals, directly affecting voice quality. Flow-based telemetry (IPFIX/NetFlow) exported over UDP provides timely flow metrics without protocol buffering overhead.
Voice quality degradation is primarily driven by delay variation (jitter) and packet loss rather than simple bandwidth saturation.

Key Concept

SNMPv3 Security Levels and Flow-based Jitter Telemetry
Question 233Question

An enterprise network administrator needs to set up performance monitoring to periodically poll CPU usage and interface bandwidth metrics across remote routers. Institutional security compliance mandates that all network telemetry must enforce both user authentication and data encryption in transit. Which monitoring protocol and security level should the administrator configure?

Show answer & explanation

Answer: SNMPv3 configured with the authPriv security level

Answer

SNMPv3 configured with the authPriv security level
Simple Network Management Protocol version 3 (SNMPv3) with the authPriv (Authentication and Privacy) security level provides cryptographic user authentication using hashes like SHA and data payload encryption using algorithms like AES. This meets both performance monitoring and strict encryption compliance standards.

Step-by-Step Solution

1
Identify the primary performance monitoring requirement
The requirement calls for periodic polling of device performance metrics (CPU and interface bandwidth) across network hardware.
Simple Network Management Protocol (SNMP) is the standard protocol for polling device performance parameters and metrics.
2
Evaluate protocol security requirements
The compliance policy explicitly specifies both user authentication and data encryption in transit.
SNMPv1 and SNMPv2c send community strings in plaintext without encryption. Only SNMPv3 includes robust cryptographic security models.
3
Select the correct SNMPv3 security level
The authPriv security level provides authentication (auth) and privacy/encryption (priv).
authNoPriv provides authentication without encryption, whereas noAuthNoPriv provides neither cryptographic authentication nor encryption.

Key Concept

SNMP Security Levels and Telemetry Monitoring
Question 234Question

An enterprise network team prepares to update the operating system across central distribution switches to patch a critical security flaw. The lead engineer submits a formal Request for Change (RFC) to the Change Advisory Board (CAB). After evaluating the submission, the CAB rejects the RFC. Which of the following omissions in the RFC is the most likely reason for the board's rejection?

Show answer & explanation

Answer: The RFC did not contain a validated rollback procedure and specific performance metrics for triggering a change reversion.

Answer

The RFC did not contain a validated rollback procedure and specific performance metrics for triggering a change reversion.
The correct answer highlights the necessity of a fully documented rollback plan and clear abort triggers within an RFC. A primary responsibility of the Change Advisory Board is risk management; any RFC lacking a clear, tested backout strategy for reverting to a functional baseline upon failure will be rejected.

Step-by-Step Solution

1
Analyze the core requirements of a Change Advisory Board (CAB) review for a Request for Change (RFC).
Identify that CAB approval requires comprehensive risk mitigation, including impact analysis, maintenance window scheduling, testing validation, and backout strategies.
CAB governance focuses on ensuring system stability and minimizing unmitigated operational risk.
2
Evaluate the missing element that presents the greatest risk during a core distribution switch upgrade.
The absence of a defined rollback plan leaves the network without a recovery strategy if the software update causes unforeseen instability or outage.
Without clear backout steps and trigger metrics, recovery from a failed change would be unstructured and prolonged.

Key Concept

Request for Change (RFC) Requirements and Rollback Planning
Question 235Question

Following an unannounced configuration drift incident, a network engineer submits a formal Request for Change (RFC) to deploy a standardized configuration baseline across all datacenter access switches. The RFC details the proposed technical modifications, maintenance window timing, and post-deployment verification procedures. However, the Change Advisory Board (CAB) defers authorization because the proposal fails to specify the exact performance thresholds (such as interface error spikes or packet loss rates) that would mandate immediately reversing the deployment. Which critical component of the RFC requires revision before approval can be granted?

Show answer & explanation

Answer: The rollback plan and its activation triggers

Answer

The rollback plan and its activation triggers
A comprehensive Request for Change (RFC) must include a explicit rollback (backout) plan that specifies both the technical steps to revert to the previous baseline and the measurable abort criteria (such as packet loss or interface error thresholds). Without clear rollback triggers, engineers cannot determine when a deployment has failed and must be aborted to protect production services.

Step-by-Step Solution

1
Identify the missing requirement in the CAB evaluation scenario.
The CAB noted the absence of defined thresholds for aborting and reversing the deployment if network issues occur during implementation.
CAB approval requires risk mitigation controls that specify when and how to revert modifications to protect operational continuity.
2
Map the missing requirement to standard RFC documentation components.
Definite threshold criteria for reversing a change belong directly within the rollback (or backout) plan section of an RFC.
A robust rollback plan must detail both the technical steps to restore the prior configuration baseline and the explicit trigger conditions that mandate rolling back.

Key Concept

Request for Change (RFC) Essential Elements and Rollback Triggers
Estimated Time:1m 30s
Question 236Question

A network operations team is preparing to modify BGP routing parameters across WAN edge routers to connect a secondary internet service provider. Before executing this scheduled modification, the lead network engineer must submit a formal Request for Change (RFC) to the Change Advisory Board (CAB). Which TWO of the following elements must be explicitly detailed within the RFC to ensure proper change management governance?

Select all that apply

Show answer & explanation

Answer: A step-by-step rollback procedure with defined trigger conditions for reverting the changes if unexpected performance degradation occurs; A comprehensive risk and impact analysis detailing potential downtime and affected business services

Answer

The correct elements that must be included in the Request for Change (RFC) are a step-by-step rollback procedure with defined trigger conditions, and a comprehensive risk and impact analysis detailing potential service disruptions.
A formal Request for Change (RFC) submitted to a Change Advisory Board (CAB) must contain a detailed risk and impact analysis to gauge potential service disruption, alongside a clear rollback plan with concrete triggers to safely undo changes if implementation fails during the maintenance window.

Step-by-Step Solution

1
Identify the core requirements of an enterprise Request for Change (RFC) document prior to CAB review.
Recognize that RFC documentation must justify the change, evaluate risk, specify the implementation steps, and detail emergency recovery procedures.
CAB approval relies on knowing the business impact, scheduling scope, and risk mitigation strategies.
2
Evaluate the necessity of a rollback plan with specific trigger criteria.
Confirm that a defined rollback plan allows engineers to abort and revert the change safely if issues arise during execution.
Without predefined trigger conditions, teams risk extending downtime beyond approved maintenance windows trying to troubleshoot ad-hoc errors.
3
Evaluate the risk assessment component.
Confirm that risk and impact analysis is required to determine maintenance window scheduling and business unit notifications.
Higher-risk changes targeting core WAN edge infrastructure require greater scrutiny and broader stakeholder awareness.

Key Concept

Request for Change (RFC) Components and Risk Management
Question 237Question

A network administrator is evaluating enterprise network telemetry tools and performance metrics. Match each monitoring scenario or metric requirement on the left with the corresponding metric or telemetry mechanism on the right.

Click a left item, then click its matching right item

Items

Measuring time variations between packet arrivals that cause choppiness in real-time VoIP calls
Periodically polling device CPU metrics and interface counters with encrypted payloads and authentication
Aggregating IP traffic flow statistics, protocol breakdown, and conversation byte counts across router interfaces
Measuring the total elapsed round-trip time required for a packet to travel from source to destination and back

Matches

Show answer & explanation

Answer

The correct pairings match packet delay variation to Jitter, authenticated and encrypted metric polling to SNMPv3 authPriv, traffic flow breakdown statistics to NetFlow / IPFIX, and total round-trip travel time to Latency.
Each monitoring scenario directly maps to its corresponding baseline metric or protocol: delay fluctuation in real-time calls is jitter; encrypted/authenticated device polling uses SNMPv3 authPriv; aggregating IP conversation and flow data uses NetFlow/IPFIX; and total transit delay is latency.

Step-by-Step Solution

1
Identify the performance issue related to packet delay variation in real-time voice calls.
Variation in arrival time between consecutive packets is defined as jitter.
VoIP streams require consistent packet delivery timing; variations result in audio buffer underruns/overruns.
2
Determine the management protocol required for secure, encrypted polling of system metrics.
SNMPv3 with authPriv provides both authentication and privacy (encryption).
Lower SNMP security levels like noAuthNoPriv or authNoPriv lack encryption for polled management data.
3
Match traffic flow analysis and protocol breakdown requirements to telemetry protocols.
NetFlow and IPFIX export flow records containing source/destination IPs, ports, and byte counts.
SNMP polls device counters, whereas flow technologies aggregate granular conversation metadata.
4
Associate total transit time measurement with the correct baseline performance metric.
Total delay for packet transmission and receipt is latency.
Latency measures overall transit time across a link or network path.

Key Concept

Network Performance Metrics and Telemetry Mechanisms
Question 238Question

During a routine security review, a network team must update device telemetry settings on WAN edge routers to enable continuous hardware performance polling. The organization's compliance mandate requires both cryptographic user authentication and payload encryption for all management traffic. Which protocol configuration should the team implement on the devices?

Show answer & explanation

Answer: SNMPv3 using the authPriv security level

Answer

SNMPv3 using the authPriv security level
The authPriv security level in SNMPv3 enforces both user authentication (via HMAC-SHA or HMAC-MD5) and payload encryption (via AES or DES). This satisfies the requirement for secured performance metric collection.

Step-by-Step Solution

1
Identify compliance requirements
Requirements specify both authentication and encryption for monitoring traffic.
Security mandates require mutual verification of origin and payload confidentiality.
2
Evaluate SNMP security levels
authPriv provides cryptographic authentication (auth) and payload privacy/encryption (priv).
SNMPv3 supports three levels: noAuthNoPriv (none), authNoPriv (authentication only), and authPriv (authentication and encryption).

Key Concept

SNMPv3 Security Levels and Cryptographic Protection
Question 239Question

A network engineering team needs to upgrade the operating system across core firewall pairs to patch a critical zero-day vulnerability. Place the standard change management stages in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct chronological order for the change management lifecycle is: (1) Draft and submit a formal RFC, (2) Present the RFC to the CAB for review and approval, (3) Perform sandbox testing and broadcast the maintenance window, (4) Deploy updates during the maintenance window and conduct verification testing, and (5) Perform a post-implementation review, update baseline documentation, and close the ticket.
The standard network change management process follows a clear administrative and operational sequence: initial request documentation (RFC creation), administrative governance (CAB authorization), staging and scheduling (sandbox testing and maintenance window notification), active implementation (deployment and post-change testing), and final administrative closure (post-implementation review and baseline updating).

Step-by-Step Solution

1
Identify the initial documentation stage.
The network team initiates the change process by creating an RFC with risk and rollback documentation.
Formal change control requires a documented RFC before stakeholder evaluation can begin.
2
Identify the authorization stage.
The RFC is submitted to the CAB for organizational review and approval.
CAB approval ensures that business and operational risks are acceptable before scheduling downtime.
3
Identify the staging and scheduling stage.
The change is pre-tested in a lab environment and stakeholders are informed of the maintenance window.
Technical validation and scheduling take place after authorization but prior to active deployment.
4
Identify the execution stage.
The change is implemented during the approved window and core functionality is verified.
Deployments must adhere strictly to scheduled windows to prevent unexpected outages.
5
Identify the post-change closure stage.
The post-implementation review is completed, baselines are updated, and the change ticket is closed.
Documenting final configuration states ensures audit compliance and maintains updated network baseline records.

Key Concept

Standard Network Change Management Lifecycle
Question 240Question

A network administrator needs to establish a comprehensive network performance monitoring strategy across remote branch routers. The solution must securely collect hardware state metrics (such as CPU utilization and interface counters) while also capturing granular flow-level statistics (such as packet loss and jitter) for latency-sensitive applications. Which TWO performance telemetry mechanisms should the administrator implement to fulfill these requirements?

Select all that apply

Show answer & explanation

Answer: Deploy SNMPv3 configured with the authPriv security level to poll hardware state metrics and interface telemetry securely.; Export IPFIX (IP Flow Information Export) records to analyze per-flow performance parameters such as packet loss and delay variation.

Answer

The administrator should implement SNMPv3 with authPriv for secure device state monitoring and IPFIX for granular flow-level performance analysis.
The combination of SNMPv3 with authPriv and IPFIX satisfies both requirements. SNMPv3 authPriv guarantees secure, encrypted polling of system hardware counters and interface statistics. IPFIX allows edge devices to export detailed flow records that track timing, packet loss, and jitter for real-time application traffic analysis.

Step-by-Step Solution

1
Identify the requirement for secure hardware metric polling.
SNMPv3 with authPriv satisfies authentication and encryption requirements for hardware state telemetry.
SNMPv3 authPriv ensures data integrity and confidentiality during device polling.
2
Identify the requirement for per-flow performance metric analysis (packet loss, delay variation).
IPFIX (or NetFlow) provides flow export mechanisms to monitor traffic dynamics and quality metrics.
Flow telemetry protocols collect traffic statistical records to evaluate real-time application behavior.

Key Concept

Network telemetry protocols and security calibration for performance monitoring
PreviousPage 12 / 19Next