Network Operations

362 soru

Soru 41Soru

A network administrator needs to apply a critical vendor security update to the organization's core infrastructure routers. In what order should the administrator execute the patch management lifecycle steps 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) Verify the cryptographic hash of the patch file, 2) Test the patch in an isolated sandbox lab, 3) Perform a baseline backup and obtain change management approval, 4) Install the patch across production devices during an approved maintenance window, and 5) Conduct post-installation system audits and performance monitoring.
A structured patch management lifecycle prioritizes risk reduction by verifying package integrity and testing in a lab staging environment first. After validating stability, administrators secure device baseline backups and obtain change management authorization. The patch is then deployed during an approved maintenance window, followed by post-implementation verification to ensure system integrity.

Adım Adım Çözüm

1
Verify patch file integrity
Confirmed authentic update package file
Ensures corrupted or altered binary files are never staged or executed.
2
Lab staging and non-production testing
Validated patch stability in isolation
Exposes unexpected software behavior or service defects before impacting active production networks.
3
Configuration baseline backup and change approval
Authorized change ticket with a rollback baseline
Establishes administrative compliance and secures a recovery point if installation fails.
4
Production deployment during maintenance window
Patch applied using a phased rollout strategy
Restricts operational impact to scheduled downtime and limits blast radius.
5
Post-patch verification and telemetry monitoring
Verified operational compliance and remediated security posture
Ensures services are functioning as intended without performance degradation.

Anahtar Kavram

Standard Patch Management Lifecycle
Soru 42Soru

An administrator is auditing an enterprise network's device monitoring architecture to satisfy compliance guidelines. The policy mandates that all SNMP telemetry and event notifications transmitted between network switches and the central management station must enforce both sender identity verification and full packet payload encryption. Which of the following SNMPv3 security levels must be configured on the devices to meet these audit requirements?

Cevabı ve açıklamayı göster

Cevap: authPriv

Cevap

The correct option is authPriv, as it provides both user authentication and data encryption for SNMPv3 management traffic.
The authPriv (Authentication and Privacy) security level in SNMPv3 uses cryptographic hashing for identity verification and symmetric encryption (such as AES) to ensure data confidentiality, fulfilling both requirements of the audit policy.

Adım Adım Çözüm

1
Analyze the security audit compliance requirements.
The requirements demand sender authentication (identity verification) and packet privacy (payload encryption).
Auditing standards mandate protecting network management telemetry against unauthorized tampering and eavesdropping.
2
Evaluate SNMPv3 User-based Security Model (USM) levels.
noAuthNoPriv offers no authentication or encryption; authNoPriv offers authentication without encryption; authPriv offers both authentication and encryption.
SNMPv3 defines three security modes with escalating cryptographic protection levels.
3
Select the security level matching both audit criteria.
authPriv satisfies both identity verification and encryption requirements.
It is the only SNMP level that combines HMAC authentication hashing with AES encryption.

Anahtar Kavram

SNMPv3 Security Levels (noAuthNoPriv, authNoPriv, authPriv)
Soru 43Soru

A systems engineer is implementing high availability and link redundancy for a critical database host connected to two independent physical switches. The network architecture must support simultaneous active-active frame forwarding across both links for throughput aggregation while preventing Layer 2 loops, without utilizing vendor-proprietary physical stacking cables. Which TWO of the following configurations or technologies must be deployed together to achieve this redundancy design?

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

Cevabı ve açıklamayı göster

Cevap: Multi-Chassis Link Aggregation (MLAG / MC-LAG) enabled across the physical switches; Link Aggregation Control Protocol (LACP / IEEE 802.3ad) in active mode on the host network interfaces

Cevap

Multi-Chassis Link Aggregation (MLAG / MC-LAG) enabled across the physical switches AND Link Aggregation Control Protocol (LACP / IEEE 802.3ad) in active mode on the host network interfaces
To achieve active-active bandwidth aggregation and link-level failover across two separate switches without physical stacking, Multi-Chassis Link Aggregation (MLAG) must be configured on the switch pair so they appear as a single logical switch. Concurrently, the host must use Link Aggregation Control Protocol (LACP) in active mode to dynamically negotiate the multi-chassis aggregated link.

Adım Adım Çözüm

1
Identify the requirement for active-active link redundancy across two distinct physical switches without switch stacking.
Recognize that standard LACP cannot bridge across independent switches without Multi-Chassis Link Aggregation (MLAG).
Standard LACP requires all aggregated links to terminate on a single logical switch control plane; MLAG presents two separate switches as one logical entity.
2
Select the host-side link aggregation protocol.
Choose LACP (802.3ad) active mode for the host bonding configuration.
LACP dynamically negotiates link aggregation with the MLAG-enabled switches to form a resilient multi-homed link.

Anahtar Kavram

Multi-Chassis Link Aggregation and Dynamic NIC Teaming for High Availability
Soru 44Soru

Match each network logging mechanism or Syslog severity level on the left with its corresponding description or operational characteristic on the right.

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

Öğeler

Syslog Severity 0 (Emergency)
Syslog Severity 4 (Warning)
NetFlow / IPFIX
SNMP Trap

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Syslog Severity 0 matches system panic/unusable condition; Syslog Severity 4 matches non-disruptive abnormal warning condition; NetFlow / IPFIX matches export of traffic flow statistics; SNMP Trap matches unsolicited event notifications from agent to collector.
Each logging mechanism and severity rating accurately corresponds to its defining operational definition within enterprise network management.

Adım Adım Çözüm

1
Differentiate Syslog severity levels based on numerical values.
Severity 0 corresponds to Emergency (highest severity), while Severity 4 corresponds to Warning.
Syslog RFC standards rank severities from 0 (Emergency) to 7 (Debug).
2
Distinguish between session telemetry and asynchronous alert protocols.
NetFlow aggregates IP session metadata for flow analysis, whereas SNMP Traps transmit asynchronous event notifications.
Flow telemetry measures volume and communication paths, while SNMP traps notify administrators of real-time status changes.

Anahtar Kavram

Syslog Severity Levels and Network Logging Telemetry Protocols
Soru 45Soru

A network administrator is updating the telemetry and auditing configuration across core switch infrastructure to adhere to security compliance standards. The compliance policy mandates that all remote device management queries must provide cryptographic authentication and payload privacy, and that system log messages must be securely forwarded to a central server using a reliable, encrypted transport protocol. Which TWO of the following configurations should the administrator implement to satisfy these mandates? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Enable SNMPv3 using the authPriv security level for device polling and monitoring.; Configure Syslog log forwarding using Transport Layer Security (TLS) over TCP port 6514.

Cevap

The administrator must implement SNMPv3 with the authPriv security level to ensure payload encryption and authentication for device management queries, and configure Syslog log forwarding using TLS over TCP port 6514 for secure and reliable log transmission.
Enabling SNMPv3 with the authPriv mode satisfies the mandate for administrative query privacy because authPriv adds payload encryption in addition to authentication. Configuring Syslog forwarding over TCP port 6514 using TLS satisfies the requirement for encrypted, reliable log transfer to the central repository.

Adım Adım Çözüm

1
Evaluate the security requirement for management queries.
Identified that cryptographic authentication and payload privacy require SNMPv3 authPriv.
SNMPv1 and SNMPv2c send community strings in plaintext. In SNMPv3, noAuthNoPriv provides no security, authNoPriv authenticates without encrypting data, and authPriv provides both authentication and privacy (encryption).
2
Evaluate the requirement for log message transport encryption and reliability.
Identified that Syslog over TCP 6514 with TLS provides encrypted, reliable log transport.
Traditional Syslog uses unencrypted UDP port 514, which lacks transport reliability and payload security. RFC 5425 specifies TLS over TCP port 6514 to secure Syslog communications with connection reliability.

Anahtar Kavram

Secure Network Logging and Device Monitoring Protocols
Tahmini Süre:1m 30s
Soru 46Soru

A network engineering team is preparing to deploy a vendor-released maintenance patch to address a critical security vulnerability across multiple enterprise edge routers. To ensure network stability and adhere to standard change management procedures, which of the following operational steps should be completed prior to applying the patch to production hardware? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Perform a verified baseline configuration backup of all target devices prior to initiating the update process.; Test and validate the patch inside an isolated laboratory environment that mirrors the production hardware configuration.

Cevap

Prior to deploying software maintenance patches to production network devices, engineers must perform a verified baseline backup of device configurations and thoroughly test the patch in an isolated lab environment that mirrors production.
Safe patch management procedures mandate creating a full, verified baseline configuration backup and validating software patches in an isolated staging/lab environment prior to production deployment. These steps ensure configuration recovery capability and minimize unexpected operational downtime.

Adım Adım Çözüm

1
Identify change management pre-deployment requirements
Recognize that baseline backups and lab/staging environment testing are mandatory risk mitigation controls.
Lab testing detects unforeseen bugs before production deployment, while backups enable rapid recovery if rollback is required.
2
Evaluate post-deployment and execution timing hazards
Reject updating live devices during peak hours or overwriting newly patched devices with incremental restorations.
Updates must occur during approved maintenance windows, and backups should only be restored if a rollback is explicitly required.

Anahtar Kavram

Pre-deployment validation, staging lab testing, baseline configuration backup, and scheduled maintenance windows in patch management workflows.
Soru 47Soru

During a high-availability audit of a corporate network, a technician evaluates a VRRP pair where Router 1 (10.1.1.2) and Router 2 (10.1.1.3) share Virtual IP (VIP) 10.1.1.1. When Router 1 is powered off for maintenance, workstations on the local subnet immediately lose connectivity to remote networks despite Router 2 assuming the active master role. Troubleshooting reveals that workstations cannot reach their default gateway during the outage. What is the most likely root cause of this failure?

Cevabı ve açıklamayı göster

Cevap: Workstations were configured with the physical IP address of Router 1 (10.1.1.2) as their default gateway instead of the virtual IP address (10.1.1.1).

Cevap

Workstations were configured with the physical IP address of Router 1 (10.1.1.2) as their default gateway instead of the virtual IP address (10.1.1.1).
In First Hop Redundancy Protocols (FHRP) such as VRRP or HSRP, hosts must be configured to point to the shared Virtual IP (VIP) as their default gateway. When hosts are instead configured with the physical IP of a specific router, traffic goes strictly to that physical device. When that router shuts down, hosts lose gateway reachability even though the standby router correctly assumes the master VRRP role.

Adım Adım Çözüm

1
Analyze the high-availability gateway architecture
Identify that Router 1 (10.1.1.2) and Router 2 (10.1.1.3) form a VRRP group with Virtual IP (VIP) 10.1.1.1.
VRRP creates a shared virtual gateway IP address so end devices have a single redundant default gateway destination.
2
Evaluate the symptom during failover
Router 2 becomes master as intended when Router 1 shuts down, but host workstations lose remote network access.
This indicates that VRRP protocol state transitions are functioning correctly, but client traffic is not reaching the new master router.
3
Determine the host configuration misconfiguration
Clients were using the physical IP of Router 1 rather than the VIP.
For gateway redundancy to work, end hosts must direct their default gateway traffic to the VIP (10.1.1.1) so VRRP can dynamically map the active router's MAC address.

Anahtar Kavram

FHRP Virtual Gateway IP Configuration
Tahmini Süre:1m 30s
Soru 48Soru

A network administrator needs to restore a corrupted domain controller on Thursday morning. The network backup strategy consists of a full backup executed every Sunday at 00:00, followed by daily incremental backups executed Monday through Wednesday at 23:00. Arrange the restoration steps in the correct chronological order required to recover the server to its most recent state prior to the failure.

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

Cevabı ve açıklamayı göster

Cevap

The correct order to restore the system using incremental backups is: 1) Restore the full baseline backup from Sunday, 2) Apply the incremental backup from Monday, 3) Apply the incremental backup from Tuesday, and 4) Apply the incremental backup from Wednesday.
Incremental backups capture only data that has changed since the last full or incremental backup and clear the archive bit. Therefore, to fully recover data to the most recent state (Wednesday night), you must first restore the full Sunday baseline backup, followed by every individual incremental backup in exact chronological sequence (Monday, then Tuesday, then Wednesday).

Adım Adım Çözüm

1
Identify the backup architecture type
Recognize that incremental backups capture only changes made since the previous backup of any type (full or incremental).
Understanding the backup type determines whether all intermediary backups are required or if only the latest differential backup is needed.
2
Determine the baseline restoration point
Select and restore the Sunday full backup first.
All backup restoration processes require restoring the foundational baseline image (full backup) before any delta changes can be applied.
3
Apply subsequent incremental backups in chronological sequence
Apply Monday's incremental backup, followed by Tuesday's incremental backup, and finally Wednesday's incremental backup.
Because each incremental backup clears the archive bit and depends on the state established by the immediately preceding incremental backup, skipping any incremental set will result in data loss or corrupted file states.

Anahtar Kavram

Incremental Backup Restoration Sequence
Soru 49Soru

A network technician is tasked with creating documentation for a newly installed equipment cabinet in a telecommunications room. Which of the following specifications belong specifically in a rack diagram? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: The vertical rack unit (U) position of each patch panel and switch; The physical height dimensions (measured in U space) of installed servers and PDUs

Cevap

The correct details to include in a rack diagram are the vertical rack unit (U) position of each patch panel and switch, and the physical height dimensions (in U space) of installed servers and power distribution units (PDUs).
A rack diagram is a physical documentation tool that shows the front and rear visual layouts of network hardware inside an equipment rack. Essential components include exact rack unit (U) position numbering (e.g., U1 through U42) and the physical height (in U space) of each device such as switches, patch panels, UPS units, and PDUs.

Adım Adım Çözüm

1
Identify the main purpose of a rack diagram.
A rack diagram visually maps out the physical placement, spacing, and inventory of devices mounted inside an IT enclosure or cabinet.
Understanding document types ensures correct selection of physical versus logical elements.
2
Evaluate candidate options for physical rack placement details.
Vertical unit positions (U space) and device height dimensions describe physical cabinet layout.
Rack diagrams strictly track vertical space (1U = 1.75 inches) and device slot locations.
3
Distinguish physical rack attributes from logical configuration parameters.
STP priorities, IP address pools, and OSI PDU encapsulations represent logical configuration settings rather than physical rack dimensions.
Logical attributes belong in network topology diagrams and IP address management documentation.

Anahtar Kavram

Rack Diagram Documentation
Soru 50Soru

An ON-site network technician is investigating a physical link failure between a wall outlet in a conference room and a switch located in the building's telecommunications closet. The technician needs to identify the precise wire pinouts, color coding standards, patch panel terminal punch-downs, and wall jack labeling schemes used for that specific horizontal cable run. Which of the following network documentation artifacts should the technician consult?

Cevabı ve açıklamayı göster

Cevap: Wiring schematic

Cevap

The technician should consult a wiring schematic, as it documents detailed physical cabling specifications including pinouts, color coding, wall jack designations, and terminal punch-downs.
A wiring schematic (or wiring diagram) is the specialized documentation artifact that details physical layer conductor pinouts, T568A/T568B color coding standards, wall plate jack IDs, and patch panel termination details for cabling runs.

Adım Adım Çözüm

1
Analyze the operational requirement from the scenario.
The technician specifically requires physical layer conductor details, wire pinouts, color codes, wall jack labels, and patch panel termination mappings.
Different network documentation types serve distinct operational purposes across Layer 1 physical layout, Layer 2/3 logical topology, and equipment rack layout.
2
Evaluate the purpose of a wiring schematic.
Wiring schematics and wiring diagrams focus explicitly on low-level physical wiring details, pin positions, T568A/T568B termination standards, and cable run endpoints.
This artifact directly supplies the pinout and termination information required to trace and repair the horizontal cable run.
3
Differentiate wiring schematics from logical diagrams, rack diagrams, and baselines.
Logical diagrams detail Layer 2/3 IP/VLAN topology, rack diagrams map rack unit space allocation, and baselines measure bandwidth/traffic performance metrics.
None of the alternative document types contain individual conductor color codes or wall outlet pinout specifications.

Anahtar Kavram

Wiring Schematics and Physical Cabling Documentation
Soru 51Soru

A enterprise network engineer is auditing a high-availability server cluster spanning two intermediate distribution frames (IDFs). During a simulated power failure on IDF-1, the secondary dual-homed database server lost network connectivity despite being physically connected to an uninterruptible power supply (UPS) in IDF-2. Upon investigation, the engineer discovers that the server's secondary network interface card (NIC) was patched into an unconfigured access port on a switch powered by a non-redundant PDU circuit, while the primary NIC was documented on VLAN 100 with 802.1Q trunking. To systematically rectify the physical layout, cable path, equipment mounting height, and logical subnet boundaries to prevent recurrence, which combination of documentation artifacts must the engineer update?

Cevabı ve açıklamayı göster

Cevap: Rack elevation diagrams, physical cable schedules, logical network topology diagrams, and port mapping documentation

Cevap

Rack elevation diagrams, physical cable schedules, logical network topology diagrams, and port mapping documentation
Addressing a complex multi-layer failure involving rack power distribution, physical switch patching, and logical VLAN/subnet boundaries requires updating four core documentation artifacts: rack elevation diagrams (for rack unit location and PDU power circuit mapping), physical cable schedules and port mappings (for exact physical patch connections and switch ports), and logical topology diagrams (for VLAN designations, subnets, and trunking pathways).

Adım Adım Çözüm

1
Analyze the physical rack power and mounting requirements.
Identified that rack elevation diagrams are needed to document equipment rack unit positions and PDU power circuit redundancy.
The failure involved a server connected to a non-redundant PDU circuit within the equipment rack.
2
Analyze physical patch cabling and port assignment needs.
Identified that cable schedules and port mapping documentation are required to record switch port destinations and physical cable runs between IDFs.
The secondary NIC was incorrectly patched into an unconfigured access port without proper records.
3
Analyze logical layer-2 and layer-3 network configurations.
Identified that logical network topology diagrams are required to document VLAN configurations, 802.1Q trunking, and IP subnets.
The primary interface relied on VLAN 100 trunking, which was missing on the secondary interface's port.

Anahtar Kavram

Comprehensive Network Documentation Artifacts (Physical vs. Logical Documentation)
Soru 52Soru

A network administrator receives a critical zero-day vulnerability advisory affecting the operating system of two enterprise core switches configured as a high-availability active/standby pair. Applying the software patch requires a full reboot of the updated switch. To mitigate operational risk, preserve service uptime, and ensure rollback capability during this emergency maintenance, which of the following procedures represents the correct workflow for deploying the patch?

Cevabı ve açıklamayı göster

Cevap: Staging and validating the patch in an isolated lab environment, backing up the current running configurations, securing emergency Change Advisory Board (CAB) approval, applying the patch to the standby switch first, verifying standby health, failing over active traffic to the standby switch, and subsequently patching the former active switch.

Cevap

The correct operational approach is to validate the patch in a lab environment, back up current configurations, obtain emergency change approval, patch the standby switch first, perform a controlled failover, and then patch the remaining switch.
Safe network software maintenance in high-availability environments requires a structured workflow: pre-test in a lab environment, create baseline configuration backups, obtain proper change management authorization, patch the standby device first, verify stability, execute a controlled failover, and patch the remaining device. This guarantees network uptime and provides clear rollback procedures at every step.

Adım Adım Çözüm

1
Pre-deployment staging and backup
Patch compatibility is verified in a non-production lab environment, and current operational configurations are safely backed up to allow rapid restoration if needed.
Prevents deploying untested firmware directly to production infrastructure and establishes a known-good restore baseline.
2
Change control and standby updating
Emergency CAB approval is secured, and the patch is applied to the standby switch while the active switch continues processing production traffic.
Protects production uptime by ensuring active network traffic is unaffected while updating the redundant node.
3
Validation, failover, and active updating
The upgraded standby switch is confirmed healthy, active traffic is manually failed over to it, and the former active switch is updated to achieve version parity.
Validates the stability of the newly patched OS in production with minimal disruption before completing the patch across both nodes.

Anahtar Kavram

High-Availability Patch Management & Controlled Rollout Sequences
Tahmini Süre:2m 0s
Soru 53Soru

An enterprise organization deploys two Layer 3 core switches, Core-A and Core-B, to provide default gateway redundancy for VLAN 10 (192.168.10.0/24192.168.10.0/24) using VRRPv3. Core-A is configured as the VRRP Master with a priority of 110, while Core-B acts as the Backup with a priority of 100. Preemption is enabled on both routers. To prevent black-holing traffic if Core-A loses its WAN connection, an interface tracking object is configured on Core-A to decrement its VRRP priority by 20 upon WAN uplink failure. Core-A is also manually configured as the Spanning Tree Protocol (STP) Primary Root Bridge for VLAN 10.

During a WAN link failure test on Core-A, tracking successfully decrements Core-A's priority to 90, and Core-B transitions to the VRRP Master state. However, telemetry shows that outbound host traffic from VLAN 10 experiences significant path latency and traverses the inter-switch trunk twice before leaving the network.

Which of the following root causes best explains why traffic is traversing the inter-switch trunk redundantly following the failover?

Cevabı ve açıklamayı göster

Cevap: Core-A remains the STP Root Bridge for VLAN 10, forcing access switches to continue forwarding Layer 2 traffic to Core-A first, which must then relay frames across the trunk to Core-B.

Cevap

Core-A remains the STP Root Bridge for VLAN 10, forcing access switches to continue forwarding Layer 2 traffic to Core-A first, which must then relay frames across the trunk to Core-B.
First Hop Redundancy Protocols (such as VRRP or HSRP) manage Layer 3 gateway availability but do not automatically adjust Layer 2 Spanning Tree Protocol (STP) topologies. When Core-A loses its WAN uplink, interface tracking lowers its VRRP priority, allowing Core-B to become the active gateway. However, Core-A remains the STP Root Bridge for VLAN 10. Access switches continue forwarding frames to Core-A according to the STP active topology. Upon receiving these frames, Core-A must forward them across the inter-switch trunk to Core-B (the active VRRP Master), which performs the routing out to the external network. To prevent this 'traffic hairpinning' or 'tromboning', STP bridge priorities should be aligned or tracked alongside FHRP state changes.

Adım Adım Çözüm

1
Analyze the state of the First Hop Redundancy Protocol (VRRP) after the WAN link failure.
Core-A's priority decremented from 110 to 90 via interface tracking. Core-B (priority 100) successfully preempted and became the VRRP Master, taking ownership of the Virtual IP (VIP) and Virtual MAC address.
Tracking mechanism functions as designed at Layer 3 to transfer default gateway routing responsibility.
2
Analyze the state of Spanning Tree Protocol (STP) after the WAN link failure.
STP operates independently of VRRP. Core-A's bridge priority was not modified by the VRRP interface tracking event, so Core-A remains the STP Primary Root Bridge for VLAN 10.
FHRP protocol state changes do not dynamically update Layer 2 STP bridge priorities.
3
Trace the path of an outbound frame sent by a host on VLAN 10.
1. Host resolves the default gateway VIP to the VRRP Virtual MAC.
2. Access switch receives the frame destined for Virtual MAC and sends it toward the Layer 2 STP Root (Core-A).
3. Core-A receives the frame, recognizes it does not own the active Virtual MAC state, and bridges it over the trunk to Core-B.
4. Core-B receives the frame and routes it out its functional WAN interface.
Misalignment between the Layer 2 STP Root Bridge and Layer 3 FHRP Master creates hairpinned/tromboned traffic across the inter-switch trunk.

Anahtar Kavram

Alignment of Layer 2 Spanning Tree Protocol (STP) Root Bridge role with Layer 3 First Hop Redundancy Protocol (FHRP) Active/Master state
Tahmini Süre:2m 0s
Soru 54Soru

A network administrator is updating core switch configurations to align with a security mandate requiring both cryptographic authentication and full payload encryption for network monitoring traffic. The legacy implementation relies on unencrypted management queries using community strings. Which protocol version and security level combination should the administrator configure to meet this mandate?

Cevabı ve açıklamayı göster

Cevap: SNMPv3 with authPriv security level

Cevap

SNMPv3 configured with the authPriv security level is required because it provides both cryptographic authentication and data privacy through payload encryption.
SNMPv3 with the authPriv (Authentication and Privacy) security level uses cryptographic hashing (such as SHA) for authentication and symmetric encryption algorithms (such as AES) to encrypt all management payloads. This satisfies the requirement for authenticated access and encrypted telemetry.

Adım Adım Çözüm

1
Identify the mandate requirements
The requirement specifies cryptographic authentication AND full payload encryption.
Security policies for administrative network monitoring often require protection against both spoofing and eavesdropping.
2
Evaluate Simple Network Management Protocol (SNMP) security models
SNMPv1 and SNMPv2c use cleartext community strings (noPriv/noAuth). SNMPv3 introduces USM with three security levels: noAuthNoPriv, authNoPriv, and authPriv.
Only SNMPv3 features modern User-based Security Model (USM) capabilities.
3
Select the SNMPv3 level matching both authentication and privacy requirements
authPriv offers authentication (using MD5/SHA) and privacy/encryption (using DES/AES).
authNoPriv lacks payload privacy (encryption), while authPriv fulfills both criteria.

Anahtar Kavram

SNMPv3 Security Models (authPriv vs authNoPriv)
Soru 55Soru

A network administrator is configuring centralized event logging on core switches using the standard Syslog protocol. Which port and transport protocol combination does standard Syslog use by default to transmit log messages to a central log server?

Cevabı ve açıklamayı göster

Cevap: UDP port 514

Cevap

Standard Syslog defaults to using UDP port 514 for sending log messages to a central server.
Standard Syslog logging services default to using UDP port 514 to transmit system notifications and log messages from network devices to a centralized log host.

Adım Adım Çözüm

1
Identify the primary service and protocol being configured.
The target service is centralized event logging via standard Syslog.
The scenario asks specifically for the default transport specifications of Syslog.
2
Recall the standard transport protocol and well-known port number for Syslog.
Standard Syslog messages are sent unencrypted over User Datagram Protocol (UDP) on port 514.
Syslog was designed as a lightweight, connectionless log transport mechanism using UDP port 514.

Anahtar Kavram

Syslog Protocol Transport and Port Configuration
Soru 56Soru

A network administrator is implementing a centralized monitoring solution for enterprise core switches. Organizational compliance policies dictate that network management queries and event trap messages transmitted across the network must guarantee cryptographic integrity, user authentication, and payload confidentiality to prevent eavesdropping and replay attacks. Which protocol implementation best satisfies all specified auditing and monitoring security requirements?

Cevabı ve açıklamayı göster

Cevap: SNMPv3 configured with the authPriv security model using SHA for authentication and AES for encryption

Cevap

SNMPv3 configured with the authPriv security model using SHA for authentication and AES for encryption
The option specifying SNMPv3 configured with the authPriv security model using SHA for authentication and AES for encryption is correct because authPriv (Authentication and Privacy) is the only SNMP security level that enforces both cryptographic user authentication and payload encryption, meeting the security baseline requirements.

Adım Adım Çözüm

1
Analyze security baseline requirements
Identified the need for message integrity, user authentication, and data privacy (payload confidentiality).
Compliance demands protection against both active tampering and passive packet capture/eavesdropping.
2
Evaluate protocol security models for SNMP versions
SNMPv1 and SNMPv2c use unencrypted community strings (no privacy/authentication). SNMPv3 introduces security models: noAuthNoPriv, authNoPriv, and authPriv.
Only SNMPv3 authPriv provides both message authentication (SHA/MD5) and payload encryption (AES/DES).
3
Verify port and operational parameters
SNMP queries use UDP 161 and SNMP traps use UDP 162. SNMPv3 authPriv directly fulfills management and alerting security controls.
Selecting SNMPv3 authPriv satisfies all audit, logging, and security baseline controls.

Anahtar Kavram

SNMPv3 Security Levels (authPriv vs. authNoPriv vs. noAuthNoPriv)
Tahmini Süre:1m 30s
Soru 57Soru

A network administrator receives a high-severity security bulletin requiring a critical firmware update on the organization's core switches. To adhere to standard patch management procedures and minimize operational risk, which of the following actions should the administrator perform FIRST before deploying the patch to the production environment?

Cevabı ve açıklamayı göster

Cevap: Test the firmware update in a lab or staging environment to verify system stability and compatibility.

Cevap

Testing the firmware update in a lab or staging environment to verify system stability and compatibility.
The correct action is testing the firmware update in a lab or staging environment first. Staging validates that the patch functions as intended without causing unexpected crashes, interface failures, or protocol instability on production hardware.

Adım Adım Çözüm

1
Identify the patch management lifecycle steps.
Recognize that patch management involves discovery, testing/staging, approval, deployment, and auditing.
Structured patch management prevents production downtime.
2
Evaluate initial deployment requirements prior to production release.
Determine that staging/lab testing must precede any live deployment.
Lab testing verifies that the firmware update does not introduce unforeseen software bugs or configuration conflicts.

Anahtar Kavram

Patch Management Testing and Staging Procedures
Soru 58Soru

A network technician is configuring Virtual Router Redundancy Protocol (VRRP) across two enterprise routers to provide default gateway fault tolerance for a local subnet. Which IP address must be configured as the default gateway on host computers to ensure uninterrupted network access during a gateway failure?

Cevabı ve açıklamayı göster

Cevap: The virtual IP address shared by the VRRP group

Cevap

The virtual IP address shared by the VRRP group must be configured as the default gateway on host computers.
First Hop Redundancy Protocols (FHRPs) like VRRP provide gateway redundancy by creating a virtual router with a shared Virtual IP (VIP) address. Host workstations configured to use this VIP send traffic to whichever physical router is actively serving as the master, ensuring continuous connectivity if one router fails.

Adım Adım Çözüm

1
Identify the purpose of First Hop Redundancy Protocols (FHRP) such as VRRP.
VRRP creates a single logical virtual router out of multiple physical routers.
End devices require a consistent IP address for their default gateway setting regardless of which physical router is actively forwarding packets.
2
Determine the proper default gateway setting for host devices.
Hosts must point to the Virtual IP (VIP) address managed by the VRRP group.
When the active router fails, the standby router assumes ownership of the VIP, keeping default gateway traffic flowing without host reconfiguration.

Anahtar Kavram

First Hop Redundancy Protocols (FHRP) Virtual IP Configuration
Tahmini Süre:45s
Soru 59Soru

An organization deploys two edge routers in a First Hop Redundancy Protocol (FHRP) group using HSRP to provide default gateway redundancy for an internal server VLAN. During a scheduled firmware upgrade, the primary active router is rebooted. Network logs confirm that the secondary router successfully transitions from standby to active state and assumes ownership of the virtual MAC address. However, all servers on the LAN immediately lose connection to external networks and fail to route outbound traffic until the primary router finishes rebooting. Which of the following is the most likely cause of this failure?

Cevabı ve açıklamayı göster

Cevap: The servers were statically configured with the physical interface IP address of the primary router as their default gateway rather than the virtual IP address.

Cevap

The host servers were statically configured using the physical interface IP address of the primary router as their default gateway instead of the HSRP virtual IP address.
For First Hop Redundancy Protocols (such as HSRP or VRRP) to provide seamless gateway failover, all host endpoints must configure the shared Virtual IP (VIP) address as their default gateway. If hosts are incorrectly configured with the physical IP address of a single router, their traffic is directed exclusively to that hardware unit and fails when the device shuts down, regardless of standby router availability.

Adım Adım Çözüm

1
Analyze the observed network symptom
HSRP standby router successfully transitions to active state and claims the virtual IP/MAC, but host devices fail to communicate externally.
This indicates that HSRP itself is operating correctly, but client traffic is not hitting the virtual gateway interface.
2
Evaluate host network configurations
Hosts configured with a physical IP address depend entirely on that specific hardware interface remaining online.
FHRP protocols require end devices to send default gateway traffic to the virtual IP (VIP) so that active role transitions transparently reroute client frames.
3
Confirm the root cause
Static point-to-point pointing to the physical IP bypasses redundancy mechanisms, causing full traffic loss when that specific device reboots.
Correcting the host default gateway setting to the FHRP VIP ensures seamless stateful/stateless failover.

Anahtar Kavram

First Hop Redundancy Protocol Virtual IP Configuration
Soru 60Soru

An enterprise network deployment utilizes two Layer 3 switches, Switch-A and Switch-B, configured with VRRP to provide default gateway redundancy for VLAN 20 (10.20.0.0/2410.20.0.0/24). Switch-A is configured with physical interface IP 10.20.0.2/2410.20.0.2/24 and a VRRP priority of 110. Switch-B is configured with physical interface IP 10.20.0.3/2410.20.0.3/24 and a VRRP priority of 100. The configured VRRP Virtual IP (VIP) is 10.20.0.1/2410.20.0.1/24. During an operational audit, it is discovered that half of the host workstations on VLAN 20 were manually configured with a static default gateway of 10.20.0.210.20.0.2, while the other half use the VIP 10.20.0.110.20.0.1. If Switch-A suddenly suffers a complete power loss, which of the following best describes the resulting traffic routing behavior for hosts on VLAN 20?

Cevabı ve açıklamayı göster

Cevap: Hosts configured with the gateway address 10.20.0.110.20.0.1 will maintain external connectivity as Switch-B transitions to the VRRP Master role, whereas hosts configured with gateway address 10.20.0.210.20.0.2 will lose all external connectivity.

Cevap

Hosts using the virtual IP address 10.20.0.1 will maintain continuous connectivity because the backup router automatically assumes the Master state for the VIP. Hosts statically configured with the physical IP 10.20.0.2 of the failed active router will lose external reachability.
In First Hop Redundancy Protocols (FHRP) such as VRRP, high availability is achieved by assigning host devices the shared Virtual IP (VIP) address as their default gateway. When the active Master router (Switch-A) fails, the Backup router (Switch-B) detects the missing advertisement frames and seamlessly assumes ownership of the VIP (10.20.0.110.20.0.1). Consequently, all hosts pointing to 10.20.0.110.20.0.1 experience minimal disruption. However, hosts misconfigured to use Switch-A's physical interface IP (10.20.0.210.20.0.2) experience total loss of external connectivity because Switch-B never adopts Switch-A's physical IP address.

Adım Adım Çözüm

1
Analyze VRRP Master/Backup state transitions upon hardware failure.
Switch-A (Priority 110, Master) fails and stops sending VRRP advertisements. Switch-B (Priority 100, Backup) misses advertisements beyond the Master_Down_Interval and transitions to Master state, taking ownership of the Virtual IP 10.20.0.1 and Virtual MAC address.
VRRP provides automated gateway failover by shifting the VIP ownership to the surviving node.
2
Evaluate host connectivity for clients using the Virtual IP 10.20.0.1.
Traffic sent to 10.20.0.1 is routed through Switch-B without requiring any host-side changes.
Hosts send packets to the virtual gateway address, which is now actively serviced by Switch-B.
3
Evaluate host connectivity for clients misconfigured with Switch-A's physical IP 10.20.0.2.
Traffic directed to 10.20.0.2 receives no ARP responses or Layer 3 processing, causing complete gateway unreachability.
Switch-B only assumes the VIP (10.20.0.1) during failover and does not take over Switch-A's unique physical IP address (10.20.0.2).

Anahtar Kavram

FHRP Virtual IP vs Physical Interface Addressing
Tahmini Süre:3m 0s
ÖncekiSayfa 3 / 19Sonraki
Network Operations Alıştırma Soruları — CompTIA Network+ — Sayfa 3 | Examkin