Network Operations

362 soru

Soru 101Soru

An organization is deploying a pair of enterprise edge switches configured with multi-chassis link aggregation (mLAG) connected to two core routers configured with Virtual Router Redundancy Protocol (VRRP). Server host interfaces are configured in an LACP IEEE 802.3ad dynamic bond. During failure simulation testing, host traffic experiences intermittent packet loss and unidirectional asymmetry upon primary router failure. Which TWO of the following administrative actions or verification steps will resolve these specific high availability operational defects?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Verify that the VRRP virtual MAC address is correctly populated in the source address field of gratuitous ARP packets sent upon master state transitions.; Ensure that the LACP system identifier and operational mode on both mLAG switches are synchronized to present a single logical switch system to the host bond.

Cevap

The issues are resolved by verifying that VRRP transmits gratuitous ARP frames containing the virtual MAC address upon master state transitions, and ensuring the mLAG switch pair shares a synchronized LACP system identifier to maintain host link aggregation stability.
High availability designs utilizing both FHRP (VRRP) and multi-chassis link aggregation (mLAG) depend on seamless Layer 2 transition and unified control protocol appearance. Verifying that gratuitous ARP (GARP) broadcasts the VRRP virtual MAC allows adjacent switches to immediately update their MAC address tables upon gateway failover. Synchronizing the LACP system ID across mLAG peers allows host dual-homed NIC teams operating in IEEE 802.3ad mode to treat both physical switch connections as a single logical bundle without dropping member ports.

Adım Adım Çözüm

1
Analyze the layer 2 network topology and failover mechanisms
Identify that host NIC teaming uses LACP across two switches (requiring mLAG), while default gateway redundancy relies on VRRP.
Traffic asymmetry and intermittent loss after a failover typically indicate MAC table staleness (missing or unacknowledged GARP) or link aggregation protocol mismatches across multi-chassis nodes.
2
Evaluate default gateway ARP updates during failover
Confirm that VRRP state changes require gratuitous ARP (GARP) frames with the virtual MAC address to refresh switch forwarding tables.
Without GARP updating the switches' CAM tables, traffic destined for the Virtual IP will continue to be sent toward the failed master's interface port.
3
Evaluate link aggregation parameters across multi-chassis nodes
Confirm that the mLAG switch pair must synchronize its LACP system ID.
If the LACP system ID differs between the two switches in an mLAG pair, the host NIC team will split the aggregate group or disable links due to perceived switch mismatch.

Anahtar Kavram

High Availability Integration of FHRP (VRRP) and Multi-Chassis Link Aggregation (mLAG/LACP)
Soru 102Soru

An IT administrator wants to ensure that a newly released software update for core network switches will not disrupt corporate operations or introduce instability before deploying it network-wide. Which of the following is the best initial step to validate the software update safely?

Cevabı ve açıklamayı göster

Cevap: Deploy the update to a non-production staging environment to test stability and compatibility.

Cevap

Testing the software update in a non-production staging environment before wide deployment.
Evaluating a software patch in a non-production staging environment allows administrators to observe device behavior, verify feature compatibility, and identify defects safely before introducing the update into live operations.

Adım Adım Çözüm

1
Identify the goal of safe patch validation.
Determine that software patches must be evaluated for bugs and compatibility before production deployment.
Applying unverified patches directly to production risks network outage and business interruption.
2
Select the appropriate environment for validation.
Use a dedicated non-production lab or staging environment that mirrors production conditions.
A staging environment allows full testing of device features and performance safely isolated from operational networks.

Anahtar Kavram

Patch Testing and Lab Staging
Tahmini Süre:45s
Soru 103Soru

During a security audit, a network administrator notices that event logs sent from a remote switch to a central log server contain significant gaps during periods of high network utilization. Investigation reveals that log packets sent via standard Syslog are being silently dropped by intermediate routers under heavy congestion. Which transport protocol and port configuration should be configured on the switch to ensure reliable, delivery-guaranteed log transmission?

Cevabı ve açıklamayı göster

Cevap: Configure Syslog to use TCP on port 514

Cevap

Configure Syslog to use TCP on port 514 to guarantee log message delivery across congested network paths.
The correct approach is configuring Syslog to use TCP on port 514. UDP-based Syslog relies on best-effort transport, which leads to lost audit events when network congestion causes packet drops. Using TCP introduces connection tracking, acknowledgments, and retransmissions to guarantee that every generated audit message reaches the central logging repository.

Adım Adım Çözüm

1
Identify the cause of missing audit logs
Standard Syslog operates by default over UDP port 514, which is a connectionless protocol without delivery guarantees or retransmission mechanisms during network congestion.
UDP packets are discarded by network devices during buffer exhaustion without notifying the sender.
2
Determine the transport protocol requirement for guaranteed log delivery
Switching log transport to TCP establishes reliable, acknowledged sessions with automatic retransmission of lost packets.
TCP sliding window mechanisms and positive acknowledgments prevent log entry loss when links experience drop conditions.
3
Select the proper standard port configuration
Standard unencrypted Syslog over TCP uses port 514.
Port 514 is the standard registered port for Syslog traffic over both UDP and TCP.

Anahtar Kavram

Syslog Transport Protocols and Reliability
Soru 104Soru

A regional bank experienced a storage area network (SAN) volume failure on Thursday at 13:30. The network operations team maintains the following backup schedule for the critical database volume:

- Full backup: Executed every Sunday at 01:00
- Differential backup: Executed daily Monday through Wednesday at 23:00
- Incremental backup: Executed every 4 hours daily (03:00, 07:00, 11:00, 15:00, 19:00, 23:00)

To achieve the minimum Recovery Time Objective (RTO) while recovering all data up to the latest available recovery point prior to the outage, which restoration sequence must the backup engineer execute?

Cevabı ve açıklamayı göster

Cevap: Restore Sunday's Full backup, restore Wednesday's Differential backup, and sequentially apply Thursday's 03:00, 07:00, and 11:00 Incremental backups.

Cevap

The optimal sequence is to restore Sunday's Full backup, apply Wednesday's Differential backup, and then sequentially apply Thursday's 03:00, 07:00, and 11:00 Incremental backups.
The correct strategy combines the full baseline backup with the single latest cumulative differential backup, followed by every incremental backup taken after that differential up to the target restore time. Sunday's full backup restores the foundation, Wednesday's differential incorporates all changes up to Wednesday night in a single operation, and the three Thursday incrementals recover all subsequent changes prior to the failure, minimizing the total number of restoration operations to optimize RTO.

Adım Adım Çözüm

1
Identify the latest full baseline image.
Sunday's 01:00 Full backup establishes the baseline dataset.
Differential and incremental backups rely on the underlying full backup block state.
2
Select the latest cumulative differential backup taken prior to the outage.
Wednesday's 23:00 Differential backup contains all data changes from Sunday 01:00 to Wednesday 23:00.
Using the latest differential supersedes all previous differentials (Monday and Tuesday), minimizing total restore steps.
3
Identify and sequentially apply all incremental backups created after the selected differential backup.
Apply Thursday 03:00, Thursday 07:00, and Thursday 11:00 Incremental backups in chronological order.
Incremental backups contain changes only since the immediate prior backup (or differential), bringing the volume to 11:00 Thursday (the last clean state before the 13:30 outage).

Anahtar Kavram

Disaster recovery backup restoration sequencing combining full, differential, and incremental backup sets to optimize RTO.
Soru 105Soru

A network administrator receives a critical security advisory regarding a remote code execution vulnerability in the operating system running on the organization's enterprise switches. Which of the following procedures should the administrator perform first to ensure a safe patch deployment?

Cevabı ve açıklamayı göster

Cevap: Test the vendor-supplied patch in an isolated staging environment and perform a baseline configuration backup prior to production deployment.

Cevap

Testing the vendor-supplied patch in an isolated staging environment and performing a baseline configuration backup prior to production deployment is the correct initial procedure.
Before deploying software updates to production network hardware, administrators must perform staging tests in a non-production environment and perform a complete configuration and system image backup. This approach verifies patch compatibility, reduces unexpected downtime, and guarantees a rapid rollback path.

Adım Adım Çözüm

1
Analyze the vendor security advisory and evaluate patch requirements.
Identified the necessity of remediating the vulnerability while adhering to standard change management practices.
Security vulnerabilities must be addressed systematically to protect infrastructure without causing accidental network downtime.
2
Validate the software patch in a sandbox or staging environment.
Verified that the software operates stably with existing protocols and device configurations.
Staging validation ensures that software regression issues or unexpected bugs are discovered prior to impacting live network traffic.
3
Perform a complete configuration backup and document rollback procedures.
Established a clear restoration baseline in the event of an update failure.
Having a verified running configuration and flash image backup allows rapid restoration during maintenance windows if issues arise.

Anahtar Kavram

Patch Management Lifecycle and Pre-Deployment Staging
Soru 106Soru

During a security compliance audit, a network administrator discovers that edge routers are transmitting critical audit logs across an untrusted WAN connection using default Syslog configurations over UDP port 514. Updated corporate policy mandates that all network event logging must guarantee connection-oriented reliable delivery and encrypt log payloads in transit to prevent eavesdropping. Which configuration modification should the administrator implement to fulfill both requirements?

Cevabı ve açıklamayı göster

Cevap: Reconfigure Syslog forwarding to use TLS over TCP port 6514.

Cevap

Reconfigure Syslog forwarding to use TLS over TCP port 6514.
Reconfiguring Syslog forwarding to use TLS over TCP port 6514 satisfies both security mandates. TCP ensures connection-oriented, reliable packet delivery with retransmissions across the WAN, while TLS provides cryptographic privacy and payload integrity for logs in transit.

Adım Adım Çözüm

1
Analyze the audit compliance requirements.
Identified two mandatory technical requirements: connection-oriented reliable delivery and encrypted payload transmission for log forwarding across the WAN.
Default Syslog uses UDP port 514, which is connectionless (unreliable) and unencrypted (cleartext).
2
Evaluate transport layer protocols for log forwarding.
TCP guarantees connection-oriented reliable delivery through sequence numbers and acknowledgments, whereas UDP offers no delivery guarantees.
Connection reliability requires replacing UDP with TCP.
3
Evaluate security and standard port specifications for secure Syslog.
RFC 5425 establishes Syslog over TLS using TCP port 6514 to provide cryptographic privacy (encryption) and data integrity.
Standard TCP port 514 does not provide TLS encryption by default, whereas TCP port 6514 is designated specifically for Syslog encapsulated within TLS.

Anahtar Kavram

Syslog over TLS (TCP Port 6514) Transport Security and Reliability
Tahmini Süre:2m 0s
Soru 107Soru

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

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Hot Standby Router Protocol (HSRP)
Link Aggregation Control Protocol (LACP)
Virtual Router Redundancy Protocol (VRRP)
Active-Passive Clustering

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

The correct match pairs Hot Standby Router Protocol (HSRP) with the Cisco-proprietary first-hop redundancy protocol definition; Link Aggregation Control Protocol (LACP) with the IEEE 802.3ad open-standard multi-link bundling protocol; Virtual Router Redundancy Protocol (VRRP) with the open-standard default gateway redundancy protocol; and Active-Passive Clustering with the architecture where a secondary unit remains idle until primary failure.
Each concept directly matches its fundamental operational definition. HSRP is Cisco-proprietary for first-hop gateway failover, VRRP is an open-standard gateway redundancy protocol, LACP provides IEEE 802.3ad link bundling at Layer 2, and Active-Passive clustering reserves a secondary system for automated failover during active node failure.

Adım Adım Çözüm

1
Differentiate First-Hop Redundancy Protocols (FHRP) by vendor standards.
Identify HSRP as Cisco-proprietary and VRRP as the open-standard alternative for gateway fault tolerance.
Both HSRP and VRRP create virtual gateways, but their standard designations differ.
2
Identify link-level aggregation protocols.
Associate LACP with IEEE 802.3ad port channeling for bandwidth aggregation and link redundancy.
LACP aggregates switch interfaces at Layer 2 rather than routing at Layer 3.
3
Identify system failover deployment models.
Associate Active-Passive Clustering with primary node processing and standby secondary node takeover.
Active-Passive design ensures dedicated hardware failover without load sharing during normal operations.

Anahtar Kavram

High Availability and Redundancy Protocols
Soru 108Soru

During a compliance audit of an organization's network monitoring infrastructure, an auditor notes that event log messages and SNMP telemetry are vulnerable to packet loss, eavesdropping, and tampering across WAN links. To remediate these findings, the security engineer must ensure that centralized log forwarding to the SIEM appliance guarantees delivery acknowledgment, encrypts message traffic over standard secure ports, and that SNMP polling enforces cryptographic user authentication along with payload privacy. Which of the following configuration sets correctly fulfills all specified requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Syslog log forwarding over TCP port 6514 using TLS encryption, and implement SNMPv3 with the authPriv security level.

Cevap

The correct implementation requires Syslog log forwarding over TCP port 6514 using TLS encryption, paired with SNMPv3 utilizing the authPriv security level.
The requirement for reliable and encrypted log forwarding necessitates using TCP port 6514 with TLS (RFC 5425). Standard UDP 514 lacks connection state and encryption. For SNMP monitoring, satisfying both authentication and privacy requirements requires SNMPv3 configured with the authPriv security level (which uses authentication algorithms along with payload privacy encryption).

Adım Adım Çözüm

1
Identify the required transport protocol and port for secure, reliable log forwarding.
Syslog using TCP port 6514 with TLS provides guaranteed delivery and encryption.
Standard Syslog uses UDP port 514 (unreliable and unencrypted). TLS-encrypted Syslog is standardized under RFC 5425 using TCP port 6514.
2
Determine the appropriate SNMP version and security model to satisfy authentication and payload privacy requirements.
SNMPv3 with the authPriv security level is required.
SNMPv1 and SNMPv2c send credentials in cleartext. SNMPv3 authNoPriv authenticates but does not encrypt; authPriv encrypts both header/authentication credentials and payload data using symmetric ciphers.
3
Synthesize the findings to select the matching configuration choice.
Combining Syslog over TCP 6514 (TLS) and SNMPv3 authPriv fulfills all audit requirements.
This combination satisfies both reliable/encrypted log transport and authenticated/encrypted SNMP management polling.

Anahtar Kavram

Syslog over TLS (TCP Port 6514) and SNMPv3 Security Levels (authPriv)
Tahmini Süre:1m 30s
Soru 109Soru

A network architecture team is updating its operational repository to streamline disaster recovery, infrastructure auditing, and physical capacity management workflows across a hybrid enterprise data center. Match each specialized network documentation artifact to its primary operational or troubleshooting application.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Fiber Optic Cable Run Matrix with Optical Time-Domain Reflectometer (OTDR) Baseline Traces
Logical Topology Map with FHRP Virtual IP (VIP) State and Dynamic Routing Annotations
Physical Rack Elevation Diagram with Circuit Power Phase Balancing and Thermal U-Positioning
Configuration Baseline Diff paired with Change Management Audit Logs

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Each documentation artifact corresponds directly to its specific domain: OTDR traces analyze physical fiber attenuation; logical topology maps diagnose protocol and VIP routing paths; physical rack elevations evaluate power load balance and thermal management; and configuration baseline diffs identify unauthorized change drift.
Each artifact targets a distinct layer of network operations: OTDR traces isolate physical fiber integrity issues; logical topology maps detail IP routing paths and gateway redundancy states; physical rack elevation diagrams track spatial, electrical phase, and thermal limits; and configuration baseline diffs identify unauthorized CLI changes.

Adım Adım Çözüm

1
Analyze the physical layer diagnostic artifact.
Correlate OTDR baseline traces and cable run matrices with optical loss analysis, fiber distance measurements, and splice fault localization.
OTDR tools measure signal reflection over distance to diagnose physical layer medium anomalies.
2
Analyze protocol-level and logical routing documentation.
Associate logical topology maps containing FHRP and routing information with layer 3 traffic flow, asymmetric paths, and failover diagnostics.
Logical diagrams detail software abstractions, IP routing boundaries, virtual gateway redundancies, and packet flow logic.
3
Analyze spatial, power, and environmental rack planning documentation.
Match physical rack elevation diagrams incorporating thermal and phase data with physical unit placement and power distribution unit planning.
Rack elevations prevent thermal hotspots and electrical circuit overloads during hardware installation.
4
Analyze operational change tracking and configuration audit artifacts.
Link configuration diffs and change management logs with operational audit, compliance verification, and tracking unauthorized modifications.
Baseline diffs highlight line-by-line configuration variances against approved operational snapshots.

Anahtar Kavram

Distinguishing distinct network documentation artifacts and mapping them to appropriate layer-specific troubleshooting and operational workflows.
Tahmini Süre:2m 0s
Soru 110Soru

A network administrator is establishing a standard patch management procedure for enterprise routers. Place the following steps of the software patch management lifecycle in the correct order from first to last.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct order of the patch management lifecycle steps is: 1) Identify and evaluate vendor patch releases, 2) Test the software patch in an isolated lab environment, 3) Submit a formal request to the Change Advisory Board (CAB) for approval, 4) Deploy the patch to production network devices during an authorized maintenance window, and 5) Perform post-deployment auditing and functionality verification.
The standard patch management lifecycle follows a structured sequence: discovering vendor patches, testing updates in a non-production lab, securing approval through change management processes, deploying during an authorized maintenance window, and completing post-deployment audits to confirm stability.

Adım Adım Çözüm

1
Identify patch requirements
Discovers vendor security releases and evaluates applicability.
The patch lifecycle must begin with identifying updates before any operational changes are planned.
2
Validate the patch in a lab environment
Confirms software stability without impacting production networks.
Lab testing identifies unexpected bugs or configuration incompatibilities prior to broad deployment.
3
Obtain organizational change authorization
Secures approval from the Change Advisory Board and schedules the work.
Change management ensures stakeholders are aware of risks, scheduling, and rollback strategies.
4
Execute production deployment
Installs the patch on active network routers.
Applying patches within an authorized maintenance window minimizes operational disruption to end users.
5
Perform post-patch validation and audit
Confirms successful patch installation and system stability.
Post-deployment verification ensures vulnerabilities are mitigated and services remain fully functional.

Anahtar Kavram

Standard Patch Management Lifecycle
Tahmini Süre:1m 0s
Soru 111Soru

Match each network logging and auditing component on the left with its corresponding primary function on the right.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Syslog
NetFlow
SNMPv3
SIEM

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Syslog matches standard system event log forwarding; NetFlow matches IP traffic flow statistics collection; SNMPv3 matches secure device status monitoring with authentication and encryption; SIEM matches centralized log aggregation and security event correlation.
Each logging and monitoring technology addresses a distinct auditing requirement: Syslog forwards system event notifications; NetFlow gathers traffic flow metadata; SNMPv3 provides secure device polling and alerting; and SIEM centralizes log aggregation, correlation, and compliance auditing.

Adım Adım Çözüm

1
Identify the function of Syslog.
Syslog handles sending text-based log messages generated by system events to a central log collector.
Syslog is the standard protocol for event messaging on network equipment.
2
Identify the function of NetFlow.
NetFlow records traffic volume, IP source/destination pairs, and port metrics.
NetFlow focuses on traffic flow metadata rather than system status event logs.
3
Identify the features of SNMPv3.
SNMPv3 provides device monitoring with built-in encryption and authentication capabilities.
Version 3 addresses security weaknesses found in SNMPv1 and SNMPv2c.
4
Identify the role of a SIEM platform.
SIEM aggregates and correlates event data from across the enterprise for auditing and detection.
SIEM systems combine log management with automated correlation.

Anahtar Kavram

Network Logging and Auditing Technologies
Soru 112Soru

A network engineer configures two Layer 3 switches, Switch-1 and Switch-2, with Virtual Router Redundancy Protocol (VRRP) to provide default gateway redundancy for a server VLAN (172.16.20.0/24172.16.20.0/24). Switch-1 is configured with a VRRP priority of 110 and a physical SVI address of 172.16.20.2172.16.20.2. Switch-2 has a priority of 100 and a physical SVI address of 172.16.20.3172.16.20.3. The VRRP Virtual IP (VIP) is assigned as 172.16.20.1172.16.20.1. After a network maintenance reboot, end-user servers lose connectivity to external subnets whenever Switch-1 undergoes maintenance, despite Switch-2 being fully operational. Troubleshooting reveals that all servers were manually statically configured with 172.16.20.2172.16.20.2 as their default gateway. Which of the following best explains why gateway redundancy failed and identifies the correct solution?

Cevabı ve açıklamayı göster

Cevap: The servers were configured with the physical IP address of Switch-1 rather than the VRRP Virtual IP address; updating host default gateway configurations to 172.16.20.1172.16.20.1 will resolve the issue.

Cevap

The host servers were misconfigured to point directly to Switch-1's physical IP address (172.16.20.2172.16.20.2) instead of the VRRP Virtual IP address (172.16.20.1172.16.20.1). Configuring all hosts to use the VRRP VIP as their default gateway allows Switch-2 to transparently assume handling gateway traffic via the shared Virtual MAC address if Switch-1 fails.
First Hop Redundancy Protocols (FHRP) such as VRRP rely on workstations and servers using a shared Virtual IP (VIP) address as their default gateway. When hosts are incorrectly configured with the physical IP address of a specific router interface, traffic is routed directly to that single device without leveraging the virtual gateway mechanism. If that specific router fails or goes offline for maintenance, host packets sent to its physical IP are dropped, breaking redundancy. Setting host default gateways to the VRRP VIP ensures traffic floats to the active Master router.

Adım Adım Çözüm

1
Analyze host IP configuration and First Hop Redundancy Protocol (FHRP) architecture.
Identify that host default gateways are set to 172.16.20.2172.16.20.2, which is the physical SVI IP of Switch-1, rather than the VRRP VIP of 172.16.20.1172.16.20.1.
FHRP protocols like VRRP provide redundancy by generating a shared Virtual IP (VIP) and Virtual MAC address that float between active/backup nodes.
2
Determine the impact of pointing default gateways to physical interface IPs.
When Switch-1 goes offline, traffic destined to its physical IP (172.16.20.2172.16.20.2) drops because Switch-2 only responds to ARP requests for the Virtual IP (172.16.20.1172.16.20.1) when assuming the Master role.
Host packets targeted at a dead physical MAC/IP cannot be intercepted by VRRP Backup routers without host configuration using the VIP.
3
Select the correct remediation.
Reconfigure server default gateway settings to target the VRRP VIP (172.16.20.1172.16.20.1).
This restores high availability, allowing Switch-2 to seamlessly take over default gateway duties upon Switch-1 failure.

Anahtar Kavram

FHRP Virtual Gateway IP Configuration
Soru 113Soru

Match each Syslog severity level to its corresponding event description based on standard network auditing and logging specifications.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Syslog Severity 2 (Critical)
Syslog Severity 4 (Warning)
Syslog Severity 5 (Notice)
Syslog Severity 7 (Debug)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Syslog Severity 2 (Critical) matches critical conditions requiring prompt intervention; Syslog Severity 4 (Warning) matches warning conditions indicating potential degradation; Syslog Severity 5 (Notice) matches normal but significant operational events; and Syslog Severity 7 (Debug) matches detailed diagnostic messages for real-time troubleshooting.
Each Syslog severity rating corresponds to a standard priority level: Severity 2 (Critical) maps to urgent conditions like hardware component failures; Severity 4 (Warning) maps to conditions indicating performance degradation; Severity 5 (Notice) records normal but significant system events; and Severity 7 (Debug) yields granular diagnostic output for protocol analysis.

Adım Adım Çözüm

1
Recall the standard Syslog numerical severity scale (0 through 7) defined in RFC 5424.
Severity ratings range from 0 (Emergency - system unusable) down to 7 (Debug - verbose troubleshooting).
Proper log severity auditing requires understanding the hierarchical priority of system event classifications.
2
Differentiate critical and warning thresholds (Severity 2 vs Severity 4).
Severity 2 addresses critical component failures needing immediate intervention, whereas Severity 4 alerts on non-fatal warnings or degraded performance.
Critical logs signify active high-impact failures, while warning logs provide proactive indications of potential impairment.
3
Differentiate operational notifications and debug output (Severity 5 vs Severity 7).
Severity 5 captures routine, significant administrative state events, whereas Severity 7 outputs high-volume diagnostic detail for active troubleshooting.
Notice logs document healthy baseline operations, while debug logs generate high-overhead telemetry for deep protocol analysis.

Anahtar Kavram

Syslog Severity Levels (RFC 5424)
Soru 114Soru

A network engineering team must mitigate a critical zero-day privilege escalation vulnerability affecting core infrastructure routers. Which of the following represents the correct sequence of administrative and technical steps required to safely implement this software update according to standardized network maintenance procedures?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with vendor advisory analysis and hash verification, followed by staging/lab testing, securing formal CAB approval with a rollback strategy, taking pre-upgrade configuration baselines, and finally executing the deployment during an authorized maintenance window followed by verification.
The correct process follows standardized network operations governance: initial risk and patch verification precedes staging lab validation, which provides empirical data required for Change Advisory Board (CAB) authorization. Immediately prior to applying the update during the approved maintenance window, administrators take a full baseline backup of target devices to ensure immediate rollback capabilities if the upgrade encounters unexpected faults.

Adım Adım Çözüm

1
Analyze vendor advisories and confirm patch integrity.
Establishes necessity, scope, and verifies patch file authenticity via cryptographic hashes.
Prevents deploying corrupted binaries or unnecessary updates.
2
Perform staging lab validation.
Identifies software bugs, performance anomalies, or CLI syntax variations.
Lab verification ensures production stability without risking live network traffic.
3
Request Change Advisory Board (CAB) review and approval.
Schedules maintenance windows and approves backout/rollback procedures.
Enforces operational governance and prevents unauthorized enterprise disruptions.
4
Take pre-deployment configuration and system backups.
Creates a recovery point corresponding to the exact current production state.
Allows rapid restoration if firmware flashing fails or causes unexpected downtime.
5
Execute patch installation in production and perform verification.
Applies security fixes and verifies routing protocols and service availability.
Completes the maintenance cycle within designated out-of-service hours.

Anahtar Kavram

Network Patch Management Lifecycle and Change Management Governance
Soru 115Soru

Match each high availability and redundancy mechanism to its corresponding operational characteristics within an enterprise network design.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Link Aggregation Control Protocol (LACP)
Virtual Router Redundancy Protocol (VRRP)
Equal-Cost Multi-Path (ECMP)
Stateful Firewall Pair Synchronization

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Link Aggregation Control Protocol (LACP) matches bundling physical Ethernet interfaces into a single logical channel. Virtual Router Redundancy Protocol (VRRP) matches presenting a single Virtual IP address for default gateway redundancy. Equal-Cost Multi-Path (ECMP) matches distributing Layer 3 traffic across multiple parallel paths of identical cost. Stateful Firewall Pair Synchronization matches replicating connection tracking tables across appliances.
High availability designs utilize specialized protocols at different layers: LACP bundles physical links for bandwidth and link failover, VRRP manages Virtual IPs for default gateway redundancy, ECMP balances routing traffic over equal-cost paths, and stateful synchronization maintains active session tables across security appliances during a failover event.

Adım Adım Çözüm

1
Analyze Layer 2 link aggregation mechanisms.
Identify LACP as the standard protocol for combining physical interfaces into a logical link (EtherChannel/Trunk) to provide physical link redundancy.
LACP specifically targets switch-to-switch or server-to-switch link failures at Layer 2.
2
Identify default gateway redundancy mechanisms.
Associate VRRP with Virtual IP (VIP) sharing across redundant gateway routers.
VRRP provides transparent first-hop failover for end-user devices configured with a single gateway address.
3
Evaluate Layer 3 routing redundancy and load balancing.
Match ECMP with routing traffic across parallel equal-cost paths.
ECMP operates at the routing layer to leverage multiple simultaneous paths.
4
Evaluate high availability for stateful security appliances.
Connect Stateful Firewall Pair Synchronization with mirroring active session state tables.
Stateful failover requires synchronized session tables so existing user connections remain active upon failover.

Anahtar Kavram

High Availability and Redundancy Mechanisms Across Network Layers
Soru 116Soru

A senior network engineer is leading a major infrastructure upgrade to implement multi-chassis link aggregation and new VLAN topologies across an enterprise datacenter. To satisfy compliance and ensure minimal service disruption, the organization enforces a strict ITIL-aligned change control policy. Place the following phases of the change management lifecycle in the correct sequential order from first to last.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The proper sequence for the enterprise change management lifecycle is: (1) Draft the Request for Change (RFC) with rollback plans, (2) Perform sandbox lab testing and validation, (3) Present the RFC and test findings to the Change Advisory Board (CAB) for authorization, (4) Schedule the maintenance window and notify stakeholders, (5) Execute the change within the maintenance window and run post-change validation, and (6) Conduct a Post-Implementation Review (PIR), update network baselines, and close the RFC.
The correct sequence strictly adheres to structured change management governance: drafting the initial RFC and rollback plan, proving concept stability via sandbox testing, acquiring formal CAB authorization, scheduling windows and alerting stakeholders, deploying changes with immediate verification during the window, and concluding with a Post-Implementation Review to update baselines and close the ticket.

Adım Adım Çözüm

1
Identify the initial proposal phase.
Drafting the Request for Change (RFC) establishes the technical scope, impact evaluation, and contingency rollback plan.
A formal change process cannot proceed without documented objectives, risk assessments, and recovery steps.
2
Determine pre-authorization testing requirements.
Executing non-production lab testing validates the configuration commands and verifies rollback procedures.
Empirical testing evidence is required to prove safety and refine risk metrics before seeking administrative authorization.
3
Identify the authorization checkpoint.
Presenting the RFC and lab validation evidence to the Change Advisory Board (CAB) secures formal organizational approval.
The CAB must assess high-level operational risks and business impacts before authorizing deployment into production.
4
Identify post-approval scheduling requirements.
Scheduling the maintenance window and broadcasting stakeholder advisories.
Stakeholder advisories and resource locking must only occur after the change has been officially approved by the CAB.
5
Determine execution and immediate verification phase.
Executing the configuration modifications during the maintenance window followed by immediate post-change testing.
Modifications must be confined to approved windows, and post-change testing ensures immediate detection of failures while the window is active.
6
Identify post-implementation closure requirements.
Conducting a Post-Implementation Review (PIR), updating configuration baselines and network documentation, and closing the RFC.
Closing the lifecycle requires capturing final network state baselines, updating CMDB records, and auditing the overall success of the change.

Anahtar Kavram

Standard Change Management Workflow
Soru 117Soru

A network administrator must remediate a critical software vulnerability discovered on an enterprise edge router. Arrange the standard patch management lifecycle procedures in the correct sequence from first to last.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence for the patch management lifecycle is: 1) Validate the vendor patch in an isolated staging environment, 2) Submit a change management ticket with risk assessment and rollback plan, 3) Create a full system state and configuration backup immediately prior to implementation, 4) Install the patch on the production router during the designated maintenance window, and 5) Perform post-deployment verification and document the updated baseline.
The standard patch management process requires structured progression: isolated lab testing first, followed by change advisory board authorization, pre-update baseline backups, scheduled production rollout, and final post-implementation auditing.

Adım Adım Çözüm

1
Initial Staging & Lab Testing
Patch compatibility and firmware stability are confirmed in sandbox isolation.
Deploying unverified code directly into active environments risks widespread outages.
2
Change Control & Governance Approval
Stakeholders approve the operational risk, maintenance window schedule, and rollback strategy.
Unapproved production modifications violate administrative policy and risk uncoordinated downtime.
3
Pre-Deployment Configuration Baseline & Backup
A clean system restore point is saved.
If the upgrade encounters errors or memory corruption, the device can be rapidly restored to its prior state.
4
Production Window Rollout Execution
The firmware update is applied to target hardware.
Performing updates during low-impact maintenance windows avoids operational impact.
5
Post-Implementation Audit & Documentation
Device stability is verified, baseline documentation updated, and change ticket closed.
Ensures the vulnerability is successfully remediated and asset inventory records remain current.

Anahtar Kavram

Standard Patch Management Lifecycle
Soru 118Soru

An enterprise network uses two routers, Router-A and Router-B, to provide default gateway redundancy for the 192.168.50.0/24192.168.50.0/24 subnet using Hot Standby Router Protocol (HSRP). Router-A has a physical interface IP address of 192.168.50.2192.168.50.2, Router-B has a physical interface IP address of 192.168.50.3192.168.50.3, and the configured HSRP virtual IP (VIP) is 192.168.50.1192.168.50.1. During scheduled maintenance, Router-A is rebooted, causing Router-B to successfully transition from Standby to Active status. However, hosts on the 192.168.50.0/24192.168.50.0/24 subnet immediately lose all outbound network access. Which of the following is the most likely cause of this issue?

Cevabı ve açıklamayı göster

Cevap: The host workstations were statically assigned the physical interface IP address 192.168.50.2192.168.50.2 as their default gateway instead of the virtual IP address 192.168.50.1192.168.50.1.

Cevap

The host workstations were statically assigned the physical interface IP address 192.168.50.2 as their default gateway instead of the virtual IP address 192.168.50.1.
First Hop Redundancy Protocols like HSRP, VRRP, and CARP provide default gateway redundancy by presenting a shared Virtual IP (VIP) address to client hosts. When Router-A reboots, Router-B takes over ownership of the VIP (192.168.50.1192.168.50.1). However, if host workstations were misconfigured to use Router-A's physical interface IP address (192.168.50.2192.168.50.2) as their default gateway, their outbound packets continue targeting 192.168.50.2192.168.50.2, which is currently unreachable, leading to complete outbound access failure.

Adım Adım Çözüm

1
Analyze the HSRP topology configuration
Router-A physical IP = 192.168.50.2192.168.50.2, Router-B physical IP = 192.168.50.3192.168.50.3, Virtual IP (VIP) = 192.168.50.1192.168.50.1.
First Hop Redundancy Protocols (FHRP) create a shared Virtual IP (VIP) that acts as the single logical default gateway address for client devices.
2
Evaluate host traffic behavior during failover
Router-B became Active and claimed control of the VIP (192.168.50.1192.168.50.1), but host traffic stopped flowing.
If hosts send packets directly to 192.168.50.2192.168.50.2 (Router-A's physical interface), those packets will be dropped when Router-A reboots, because Router-B only listens for ARP and traffic destined for the VIP (192.168.50.1192.168.50.1) and its own physical IP (192.168.50.3192.168.50.3).
3
Identify the root cause of the misconfiguration
Host default gateway addresses were set to Router-A's physical IP address instead of the HSRP VIP.
To benefit from high availability gateway redundancy, all network clients must point to the Virtual IP address as their default gateway.

Anahtar Kavram

First Hop Redundancy Protocol (FHRP) Virtual IP Assignment
Soru 119Soru

A network engineer is executing a scheduled operating system software update on a core managed switch equipped with dual flash memory banks (Bank 0 and Bank 1). The switch currently executes its operational firmware from Bank 0. To follow software maintenance best practices for risk mitigation and rapid rollback capability, which of the following procedures should the engineer execute?

Cevabı ve açıklamayı göster

Cevap: Upload the new software image into Bank 1, update the startup boot environment variable to target Bank 1, and preserve the active software image in Bank 0.

Cevap

Uploading the updated software image into Bank 1, setting the boot system configuration to point to Bank 1, and keeping the proven operational software in Bank 0 represents the correct operational maintenance procedure.
Utilizing dual flash memory banks allows network engineers to perform non-destructive software updates. By writing the new software image to the alternate bank (Bank 1) and updating the boot configuration parameters while leaving the known-working image untouched on Bank 0, the engineer retains an immediate, verified recovery option if the new software image experiences boot loops, memory corruptions, or feature regressions.

Adım Adım Çözüm

1
Transfer the validated software patch image to the secondary, non-active flash storage partition (Bank 1).
The new firmware file is stored locally on the switch without altering the currently running operating system.
Staging the image in secondary storage preserves the running software image in primary storage.
2
Modify the startup configuration system boot path variable to point to the newly written image on Bank 1.
The switch configuration instructs the bootloader to read the updated software binary upon next system reload.
Explicitly updating the boot variable directs the control plane to initialize the new version.
3
Reboot the switch during the designated maintenance window while leaving Bank 0 intact.
The device boots into the updated operating system version while maintaining Bank 0 as an instantaneous fall-back target.
Preserving the previous image in Bank 0 ensures a instant rollback procedure can be executed if post-patch sanity checks fail.

Anahtar Kavram

Dual-Bank Flash Firmware Maintenance and Rollback Strategy
Soru 120Soru

An enterprise network administrator maintains a disaster recovery plan for an active database server. The backup schedule performs a full backup every Sunday at 01:00, daily differential backups every evening at 23:00 (Monday through Saturday), and incremental transaction log backups every two hours between 08:00 and 18:00 daily. On Thursday at 15:30, a primary storage failure occurs. Which sequence of backup sets must be restored to recover the server to its 14:00 Thursday point-in-time state with the fewest restoration operations?

Cevabı ve açıklamayı göster

Cevap: The Sunday full backup, the Wednesday differential backup, and the Thursday 08:00, 10:00, 12:00, and 14:00 incremental backups in chronological order

Cevap

Restoring the Sunday full backup, the Wednesday differential backup, and the sequential Thursday incremental backups (08:00, 10:00, 12:00, and 14:00) provides the fastest, complete point-in-time recovery.
To achieve a point-in-time restore with the minimum number of steps, the restoration process begins with the last full backup (Sunday). The latest differential backup (Wednesday at 23:00) is applied next, which rolls all data forward to Wednesday night in one operation, superseding Monday and Tuesday differentials. Finally, because incremental backups record only changes since the last backup of any type, each incremental backup on Thursday (08:00, 10:00, 12:00, and 14:00) must be applied sequentially to recover up to 14:00.

Adım Adım Çözüm

1
Restore the baseline full backup
Establishes the initial baseline full system image state from Sunday at 01:00.
All recovery processes require an initial full backup baseline before applying differential or incremental changes.
2
Restore the latest differential backup prior to the outage
Applies all cumulative data changes made between Sunday 01:00 and Wednesday 23:00 in a single step.
Differential backups capture all changes since the last full backup, rendering earlier differential backups (Monday and Tuesday) obsolete for restoration.
3
Restore all incremental backups created after the latest differential backup up to the recovery target time
Applies Thursday's 08:00, 10:00, 12:00, and 14:00 incremental backups in sequential order.
Incremental backups contain only data changed since the previous backup event. Each incremental backup depends on the preceding incremental file.

Anahtar Kavram

Disaster recovery backup restoration sequences using full, differential, and incremental backup types
ÖncekiSayfa 6 / 19Sonraki
Network Operations Alıştırma Soruları — CompTIA Network+ — Sayfa 6 | Examkin