Examkin

Network Fundamentals

398 questions

All types398Multiple choice205Multiple select92Numeric18Matching68Ordering7Short answer8
Question 61Question →

A network engineer is deploying a high-availability infrastructure using Type 1 hypervisors in an enterprise data center. Which two statements accurately describe the operational and structural characteristics of Type 1 hypervisors and their virtual network components? (Select two.)

Select all that apply

Show answer & explanation

Answer: The hypervisor runs directly on the host hardware substrate without requiring an underlying general-purpose operating system.; Virtual switches inside the hypervisor forward Layer 2 frames between local virtual machines and map traffic to physical network interface cards.

Answer

The correct statements are that the hypervisor runs directly on the host hardware substrate without requiring an underlying general-purpose operating system, and that virtual switches inside the hypervisor forward Layer 2 frames between local virtual machines and map traffic to physical network interface cards.
Type 1 hypervisors (such as VMware ESXi or Cisco UCS hypervisors) operate directly on bare-metal server hardware without requiring a host operating system layer. Inside the hypervisor environment, software-defined virtual switches perform Layer 2 forwarding between virtual machine virtual NICs (vNICs) and multiplex frame traffic onto physical network interface card (pNIC) uplinks.

Step-by-Step Solution

1
Examine hypervisor architecture classification
Type 1 (bare-metal) hypervisors install directly on hardware without an intermediate host OS layer.
Hypervisor architecture determines resource overhead and direct hardware interaction capabilities.
2
Analyze virtual switch operation and frame forwarding
Virtual switches manage internal Layer 2 frame switching between vNICs and connect them to physical NIC (pNIC) uplinks.
Virtual switches provide network abstraction within hypervisor memory to bridge virtual interfaces to physical network ports.
3
Evaluate loop prevention mechanisms in virtual switches
Virtual switches prevent loops by architectural design (disallowing frame bridging directly between physical uplinks) rather than running STP elections.
Standard vSwitches do not process or exchange STP BPDUs across uplinks to form topology loops.

Key Concept

Type 1 Hypervisor Architecture and Virtual Switch Functionality
Question 62Question →

A network engineer is auditing wireless performance metrics across an enterprise deployment. Match each wireless radio frequency (RF) metric or unit on the left to its corresponding definition on the right.

Click a left item, then click its matching right item

Items

RSSI
Noise Floor
SNR
dBm

Matches

Show answer & explanation

Answer

RSSI matches the relative measurement vendor index; Noise Floor matches the background RF energy measure; SNR matches the comparative decibel difference between signal and noise; dBm matches the absolute unit of power referenced to 1 milliwatt.
RSSI is a relative vendor index for received power, Noise Floor is the total ambient background RF energy, SNR represents the decibel difference between signal strength and noise floor, and dBm is an absolute unit of power referenced to 1 milliwatt.

Step-by-Step Solution

1
Differentiate absolute power measurements from relative indicators.
dBm is an absolute power value referenced to 1 milliwatt (0 dBm=1 mW0\text{ dBm} = 1\text{ mW}), while RSSI is a relative vendor-dependent index of signal strength.
Understanding absolute versus relative units prevents mistaking arbitrary scales for standardized power measurements.
2
Identify environmental RF characteristics.
The noise floor measures ambient background RF interference from natural and non-Wi-Fi sources.
Establishing the noise floor baseline is required for assessing overall RF channel quality.
3
Evaluate the signal quality calculation.
SNR calculates the difference between the received signal level and the noise floor (SNR=Signal Power−Noise Floor\text{SNR} = \text{Signal Power} - \text{Noise Floor}).
A higher SNR value directly correlates with higher data transmission rates and lower frame retry rates.

Key Concept

Wireless RF Measurement Metrics and Units
Question 63Question →

A network engineer is troubleshooting latency spikes in a real-time financial market data feed. Packet analysis reveals that when minor packet loss occurs on the WAN link, the receiving application experiences head-of-line blocking, holding back newly arrived live data while waiting for lost segments to be retransmitted. The application developers require a transport solution that delivers incoming data segments immediately to the application layer upon arrival, accepting unacknowledged data loss in exchange for minimal overhead and zero retransmission delay. Which transport layer design recommendation satisfies these requirements?

Show answer & explanation

Answer: Migrate the streaming protocol to UDP and handle any required packet ordering at the application layer, reducing header overhead from 20 bytes to 8 bytes and eliminating TCP retransmission buffer delays.

Answer

Migrating the streaming protocol to UDP and handling any required packet ordering at the application layer satisfies the requirements by reducing header overhead from 20 bytes to 8 bytes and eliminating head-of-line blocking.
Migrating to UDP removes transport-layer retransmissions and stream sequencing delays. UDP operates connectionlessly with a fixed 8-byte header overhead (compared to TCP's minimum 20-byte header), allowing out-of-order packets to be delivered to the application immediately upon arrival without head-of-line blocking.

Step-by-Step Solution

1
Analyze the application requirements and current failure mode.
The current setup uses TCP, which enforces connection-oriented, reliable, strictly ordered delivery. When a packet is dropped, TCP receiver buffers hold subsequent segments (head-of-line blocking) while awaiting retransmission, causing latency spikes.
Real-time applications prioritize low latency and immediate processing of recent data over complete reliability.
2
Compare TCP and UDP transport characteristics and header structures.
TCP uses a minimum 20-byte header with fields for Sequence Number, Acknowledgment Number, and Window size to provide flow control and reliability. UDP uses a lean, 8-byte fixed header (Source Port, Destination Port, Length, Checksum) with zero retransmission mechanisms or connection setup overhead.
UDP eliminates head-of-line blocking and reduces per-packet transport overhead.
3
Select the appropriate transport protocol migration strategy.
Transitioning to UDP provides connectionless delivery. If sequence tracking is still necessary, the application layer can inspect embedded timestamps or sequence numbers without waiting for transport-layer retransmissions.
This directly fulfills the requirement for zero retransmission delay and minimal transport header overhead.

Key Concept

TCP vs UDP Transport Characteristics and Header Overhead
Question 64Question →

An organization is assigned the IPv6 global routing prefix 2001:db8:abc0::/482001:\text{db8}:\text{abc0}::/48. A network engineer needs to configure the 16th subnet (subnet index 15 in hexadecimal count starting from 0) using standard /64/64 subnets. The router interface on this subnet is configured to dynamically derive its 64-bit interface identifier using EUI-64 based on its MAC address of 70-69-79-A1-B2-C3\text{70-69-79-A1-B2-C3}. Which fully formed and compressed IPv6 global unicast address will be assigned to this interface?

Show answer & explanation

Answer: 2001:db8:abc0:f:7269:79ff:fea1:b2c3

Answer

The correct IPv6 address is 2001:db8:abc0:f:7269:79ff:fea1:b2c3.
The correct answer properly converts the 16th subnet index (15) to hexadecimal 'f', inserts the 'FFFE' pattern into the MAC address, and flips the 7th bit of the first byte (from 0x70 to 0x72) to form the valid EUI-64 interface identifier.

Step-by-Step Solution

1
Determine the Subnet ID
The subnet ID is 0x000F (compressed to 'f').
Starting from subnet index 0 (2001:db8:abc0:0::/642001:\text{db8}:\text{abc0}:0::/64), the 16th subnet corresponds to index 15, which in hexadecimal is 0x000F.
2
Insert FFFE into the MAC address
7069:79FF:FEA1:B2C3
EUI-64 construction requires splitting the 48-bit MAC address (70-69-79-A1-B2-C3) into two 24-bit halves and inserting 0xFFFE between them.
3
Invert the Universal/Local (7th) bit of the first byte
First byte changes from 0x70 to 0x72.
The first byte 0x70 in binary is 0111 0000. Inverting the 7th bit (bit position 7 from MSB) yields 0111 0010, which is 0x72 in hexadecimal. Thus, the interface ID becomes 7269:79ff:fea1:b2c3.
4
Combine the network prefix, subnet ID, and interface ID
2001:db8:abc0:f:7269:79ff:fea1:b2c3
Combining 2001:db8:abc0::2001:\text{db8}:\text{abc0}:: + f::f:: + 7269:79ff:fea1:b2c37269:79\text{ff}:\text{fea1}:b2c3 produces the complete IPv6 address.

Key Concept

EUI-64 Interface Identifier Construction and Hexadecimal IPv6 Subnetting
Question 65Question →

A network administrator is troubleshooting an issue where Lightweight Access Points (LAPs) across a WAN link are unable to form control tunnels with the central Wireless LAN Controller (WLC). ICMP reachability between the LAPs and the WLC is verified, but CAPWAP tunnel negotiation fails at the transport layer due to firewall filtering. Which transport protocol and destination port must be permitted on perimeter firewalls to allow CAPWAP control traffic to establish?

Show answer & explanation

Answer: UDP port 5246

Answer

UDP port 5246 is required for CAPWAP control traffic between Lightweight Access Points and the Wireless LAN Controller.
The Control and Provisioning of Wireless Access Points (CAPWAP) protocol uses UDP as its transport layer protocol. Specifically, CAPWAP Control messages operate over UDP port 5246 (secured via DTLS), enabling the LAP to join the WLC, receive configuration updates, and exchange management metrics. Permitting UDP port 5246 allows the control channel to initialize successfully.

Step-by-Step Solution

1
Identify the protocol used for Cisco Split-MAC architecture management plane communications.
Lightweight APs use the Control and Provisioning of Wireless Access Points (CAPWAP) protocol to communicate with the WLC.
CAPWAP establishes two distinct tunnels: a control tunnel for AP management/configuration and a data tunnel for encapsulated wireless client traffic.
2
Determine the transport protocol and port numbers assigned to CAPWAP control and data planes.
CAPWAP Control uses UDP port 5246 (secured with DTLS), while CAPWAP Data uses UDP port 5247.
UDP is chosen for lower overhead and real-time processing performance, relying on DTLS for control channel reliability and security.
3
Match the requirement in the scenario to the correct port.
To resolve the control tunnel initialization failure, UDP port 5246 must be allowed through the firewall.
Allowing UDP port 5246 ensures the LAP can perform CAPWAP discovery, join, and configuration state exchanges with the WLC.

Key Concept

CAPWAP Transport Layer Ports (Control vs Data)
Question 66Question →

An administrator is configuring a direct point-to-point link between two router interfaces (Router1 GigabitEthernet0/0/0 and Router2 GigabitEthernet0/0/0) in a lab. Auto-MDIX has been manually disabled on both interfaces. After connecting the routers using a standard straight-through Ethernet cable, the administrator checks Router1 with the following command:

text
Router1# show interfaces gigabitEthernet 0/0/0
GigabitEthernet0/0/0 is down, line protocol is down (disabled)
Hardware is Gigabit Ethernet, address is 0050.56be.1a01 (bia 0050.56be.1a01)
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255

Which physical layer issue is the primary cause of both the interface status and line protocol remaining in a down/down state?

Show answer & explanation

Answer: An incorrect pinout cable type is used between two like MDI devices when Auto-MDIX is disabled.

Answer

The primary cause is the use of a straight-through cable between like devices (router to router) when Auto-MDIX is disabled, which requires a crossover cable to complete the physical circuit.
The correct answer identifies that connecting two like devices (router to router) without Auto-MDIX enabled requires a crossover cable. A straight-through cable maps transmit pins to transmit pins and receive pins to receive pins, which prevents physical carrier detection and leaves the link in a down/down state.

Step-by-Step Solution

1
Analyze the CLI interface state
The output shows 'GigabitEthernet0/0/0 is down, line protocol is down', indicating a Layer 1 physical connectivity issue.
When both interface and line protocol are down, physical signal electrical detection has failed.
2
Evaluate cabling requirements for like devices
Routers are MDI devices. Connecting MDI to MDI directly requires pin 1/2 (Tx) to connect to pin 3/6 (Rx).
A straight-through cable connects pin 1 to 1 and pin 2 to 2, causing both routers to transmit on the same pins and receive on the same pins.
3
Factor in the Auto-MDIX setting
Because Auto-MDIX is disabled, the interfaces cannot automatically adjust pin assignments electronically, requiring a physical crossover cable.
Without Auto-MDIX or a crossover cable, no link pulse/signal is detected, keeping the link down/down.

Key Concept

Ethernet Cable Pinouts and Auto-MDIX Operation
Question 67Question →

A Cisco Catalyst switch receives an Ethernet frame on interface FastEthernet0/1. The frame contains a source MAC address that does not currently exist in the MAC address table, and a destination MAC address that is already registered to interface FastEthernet0/4. In what correct sequential order does the switch perform its internal frame processing and forwarding tasks?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

1. Receive the Ethernet frame on interface FastEthernet0/1 and inspect the Layer 2 header for source and destination MAC addresses.
2. Check the MAC address table for the source MAC address and create a dynamic entry associating it with FastEthernet0/1.
3. Perform a lookup in the MAC address table using the destination MAC address to identify the associated egress port.
4. Forward the unicast frame exclusively out interface FastEthernet0/4 without flooding.
When a switch receives a frame, it sequentially executes two main phases: MAC learning followed by frame forwarding. First, it extracts the header information on the ingress port. Second, it inspects the source MAC address; if missing from the MAC address table, it records a dynamic entry associating the source MAC with the receiving port and VLAN. Third, it checks the destination MAC address against its MAC address table. Fourth, because a matching entry exists for FastEthernet0/4, the switch forwards the frame directly out that single interface without flooding.

Step-by-Step Solution

1
Frame Ingress Inspection
Source and destination MAC address fields are read from the incoming Ethernet frame header.
The switch must inspect the frame header on port FastEthernet0/1 to extract the Layer 2 addressing information.
2
Source MAC Learning
A new entry is added to the MAC address table mapping the source MAC address to interface FastEthernet0/1.
Layer 2 switches learn source MAC addresses upon ingress prior to making any forwarding decisions.
3
Destination Address Table Query
The destination MAC address is matched to existing entry for interface FastEthernet0/4.
The switch inspects its Content Addressable Memory (CAM) table to determine where to direct the frame.
4
Known Unicast Egress Forwarding
The frame is transmitted directly out interface FastEthernet0/4.
Matching a known destination MAC address triggers point-to-point unicast forwarding instead of unknown unicast flooding.

Key Concept

Layer 2 frame processing pipeline: MAC learning occurs on ingress before destination lookup and forwarding.
Question 68Question →

A network engineer is troubleshooting performance degradation on switch interface FastEthernet0/1. The output of the `show interfaces fastethernet 0/1` command is shown below:

text
FastEthernet0/1 is up, line protocol is up (connected)
Hardware is FastEthernet, address is 0019.e762.a801 (bia 0019.e762.a801)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s, media type is 100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:02, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 32000 bits/sec, 28 packets/sec
5 minute output rate 88000 bits/sec, 64 packets/sec
521098 packets input, 68191044 bytes, 0 underruns
Received 42 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
12480 input errors, 12472 CRC, 8 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
889123 packets output, 118129033 bytes, 0 underruns
0 output errors, 38102 collisions, 9841 late collision, 0 deferred

Based on the CLI output, which two underlying issues could be causing the observed interface counters? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A duplex mismatch where the local interface is operating in half-duplex while the connected endpoint is operating in full-duplex; The Ethernet cable length exceeds the maximum 100-meter distance limit defined by Category 5e/6 specifications

Answer

The two probable causes are a duplex mismatch (where the local interface is operating in half-duplex while the remote end is in full-duplex) and an Ethernet cabling run that exceeds the maximum allowed 100-meter distance specification.
Late collisions are defined as collisions occurring after the first 64 bytes (512 bits) of a frame have been transmitted. The two primary causes of late collisions on an Ethernet link are: 1) A duplex mismatch where one end operates in half-duplex and the opposing end operates in full-duplex (the full-duplex side transmits without listening, interrupting ongoing transmissions after 64 bytes), and 2) Physical cable lengths exceeding the maximum specification (100 meters for UTP), which causes propagation delays longer than the 512-bit slot time.

Step-by-Step Solution

1
Analyze the interface operating mode and error counters from the CLI output
The interface is set to Half-duplex mode at 100 Mbps and shows significant late collision counters (9,841) and CRC errors (12,472).
Late collisions occur when a collision is detected after the first 64 bytes (512 bits) of a frame have already been transmitted.
2
Evaluate duplex mismatch mechanics
A full-duplex endpoint transmits at any time without performing carrier sensing, sending frames that collide with the half-duplex interface after its 64-byte transmission window has passed.
The full-duplex device ignores half-duplex collision domain rules, causing late collisions on the half-duplex receiver.
3
Evaluate physical cable distance limits
Exceeding the 100-meter UTP distance limit increases signal propagation delay beyond the standard Ethernet 512-bit slot time.
When propagation delay exceeds the slot time, normal collisions arrive too late to be handled as standard collisions, incrementing the late collision counter instead.

Key Concept

Late collisions on Ethernet interfaces are primarily caused by duplex mismatches or physical cable length limit violations (>100m).
Estimated Time:2m 0s
Question 69Question →

An enterprise data center environment utilizes bare-metal Type 1 hypervisors connected to an upstream physical Layer 3 switch acting as the default gateway for all host subnets. Host-A contains Virtual Machine 1 (VM-1) on VLAN 10 (10.1.10.0/2410.1.10.0/24) and Virtual Machine 2 (VM-2) on VLAN 20 (10.1.20.0/2410.1.20.0/24). The virtual switch (vSwitch) running inside Host-A operates strictly as a Layer 2 virtual device with no internal Layer 3 routing interface configured. When VM-1 sends the initial packet to establish a session with VM-2, which network component makes the forwarding decision to route traffic between these two virtual machines?

Show answer & explanation

Answer: The upstream physical Layer 3 switch receives the frame via the trunk link, performs a routing table lookup, and routes the packet back down the trunk to Host-A's vSwitch for delivery to VM-2.

Answer

The upstream physical Layer 3 switch receives the frame via the trunk link, performs a routing table lookup, and routes the packet back down the trunk to Host-A's vSwitch for delivery to VM-2.
Because VM-1 and VM-2 are situated on different VLANs (10.1.10.0/2410.1.10.0/24 and 10.1.20.0/2410.1.20.0/24), communication between them requires Layer 3 routing. Since the vSwitch on Host-A is explicitly operating as a Layer 2 switch without L3 capabilities, it cannot route packets between VLANs internally. Therefore, VM-1 sends the packet to its default gateway, causing the frame to exit Host-A via a trunk interface, reach the physical Layer 3 switch where the inter-VLAN routing decision occurs, and return back down the trunk to Host-A for delivery to VM-2.

Step-by-Step Solution

1
Determine the source and destination subnets
VM-1 (10.1.10.0/2410.1.10.0/24) and VM-2 (10.1.20.0/2410.1.20.0/24) belong to distinct IP subnets and VLANs.
Traffic between different IP subnets requires a Layer 3 routing decision (inter-VLAN routing).
2
Evaluate the capabilities of the host's virtual network infrastructure
The local vSwitch operates strictly at Layer 2 and lacks L3 routing interfaces.
A Layer 2 device can only switch frames within the same broadcast domain (VLAN). It cannot rewrite MAC headers or cross VLAN boundaries.
3
Trace the packet path for inter-VLAN routing
VM-1 sends the frame to its default gateway MAC address. The vSwitch forwards the frame up the physical trunk link to the physical Layer 3 switch. The L3 switch routes the packet from VLAN 10 to VLAN 20 and sends it back down the trunk to the vSwitch, which delivers it to VM-2.
Even though both VMs reside on the same hypervisor host, inter-VLAN traffic must traverse the default gateway on the upstream L3 switch ('router-on-a-stick' / external L3 forwarding pattern).

Key Concept

Inter-VLAN Routing and Layer 2 Virtual Switch Boundaries
Estimated Time:2m 0s
Question 70Question →

A network engineer is troubleshooting a custom financial trading application that streams tick data across an enterprise WAN link. During micro-burst traffic spikes, application logs report severe latency variations and out-of-order message processing, despite zero interface drops recorded on local router interfaces. Wireshark analysis reveals that the Layer 4 header of the application frames is fixed at 8 bytes in length, with no explicit Sequence Number or Acknowledgment Number fields present. However, the software development team insists that the transport protocol itself is executing dynamic windowing flow control to handle the latency. Which statement correctly identifies the transport protocol in use and explains why the developer's claim regarding Layer 4 flow control is incorrect?

Show answer & explanation

Answer: The protocol is UDP; UDP has a fixed 8-byte header and is completely connectionless and stateless, meaning any reliability, sequencing, or reordering mechanisms must be implemented in the application layer rather than at Layer 4.

Answer

The protocol is UDP; UDP has a fixed 8-byte header and is completely connectionless and stateless, meaning any reliability, sequencing, or reordering mechanisms must be implemented in the application layer rather than at Layer 4.
The correct answer identifies that an 8-byte L4 header without sequence or ACK fields uniquely characterizes UDP. UDP prioritizes speed and low overhead over reliability. It does not provide flow control, error recovery, or reordering at the transport layer. Any ordering or reliability logic must be built into the upper-layer application protocol.

Step-by-Step Solution

1
Analyze the Layer 4 header size provided in the packet analysis.
The packet capture indicates a fixed 8-byte Layer 4 header length.
UDP headers are always 8 bytes (containing Source Port, Destination Port, Length, and Checksum), whereas standard TCP headers have a minimum length of 20 bytes.
2
Examine the presence of reliability and flow control fields.
The capture shows no Sequence Number, Acknowledgment Number, or Window Size fields.
TCP requires these fields (within its 20-byte base header) to provide stateful, reliable connection management, retransmission, and sliding-window flow control. UDP omits all state management fields.
3
Evaluate the software developer's claim regarding transport layer flow control.
The claim is invalid for Layer 4; any sequencing or buffering mechanisms must reside at the application layer (Layer 7).
Because UDP operates without transport-layer state, applications using UDP must handle packet loss detection, reordering, and rate control within custom higher-layer protocols.

Key Concept

UDP versus TCP Header Fields and Reliability Mechanics
Question 71Question →

Match each Cisco IOS interface line status and line protocol state combination to its corresponding root cause.

Click a left item, then click its matching right item

Items

GigabitEthernet0/1 is down, line protocol is down
GigabitEthernet0/1 is administratively down, line protocol is down
GigabitEthernet0/1 is up, line protocol is down
GigabitEthernet0/1 is up, line protocol is up (disabled)

Matches

Show answer & explanation

Answer

The interface states map to their corresponding root causes based on Layer 1 vs. Layer 2 status: down/down indicates a Layer 1 physical connectivity issue; administratively down indicates the port is shut down by configuration; up/down indicates a Layer 2 encapsulation or keepalive failure; and up/up (disabled) indicates an err-disabled state triggered by switch security features.
Matching interface states to their root causes requires analyzing Layer 1 and Layer 2 status lines: 'down/down' corresponds to a Layer 1 physical failure like an unplugged cable; 'administratively down' corresponds to an interface disabled by the 'shutdown' command; 'up/down' indicates Layer 1 is operational while Layer 2 framing or keepalives failed; and 'up/up (disabled)' corresponds to a port placed in the err-disabled state due to security or protocol violations.

Step-by-Step Solution

1
Analyze 'down / down' interface output
Identified as a Layer 1 physical problem.
Lack of carrier signal or physical link pulse forces both the interface and protocol status to down.
2
Analyze 'administratively down / down' interface output
Identified as a software configuration shutdown state.
The 'shutdown' command explicitly disables the interface in software.
3
Analyze 'up / down' interface output
Identified as a Layer 2 Data Link problem.
Physical signal detection is successful ('up'), but protocol negotiation, keepalives, or encapsulation failed ('down').
4
Analyze 'up / up (disabled)' interface output
Identified as an error-disabled (err-disabled) port state.
Cisco IOS automatically disables active ports when severe error thresholds or port security limits are breached.

Key Concept

Cisco IOS Interface Status and Line Protocol Troubleshooting
Estimated Time:1m 0s
Question 72Question →

Match each IPv6 address prefix on the left to its designated address scope or function on the right.

Click a left item, then click its matching right item

Items

2000::/3
fe80::/10
fc00::/7
ff00::/8

Matches

Show answer & explanation

Answer

2000::/3 matches Global Unicast, fe80::/10 matches Link-Local, fc00::/7 matches Unique Local, and ff00::/8 matches Multicast.
Each prefix correctly maps to its standard RFC-defined IPv6 address scope: 2000::/3 is Global Unicast, fe80::/10 is Link-Local, fc00::/7 is Unique Local, and ff00::/8 is Multicast.

Step-by-Step Solution

1
Identify the Global Unicast range
2000::/3 covers 2000:: through 3fff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, which represents Global Unicast.
Standard IANA IPv6 allocation reserves 2000::/3 for public Internet routing.
2
Identify the Link-Local prefix
fe80::/10 covers fe80:: through febf::, which is reserved for Link-Local addresses.
Link-Local addresses are automatically configured on enabled IPv6 interfaces for local link communication.
3
Identify the Unique Local prefix
fc00::/7 covers fc00:: through fdff::, designated as Unique Local.
Unique Local addresses provide private addressing space within internal networks and are not routed on the global Internet.
4
Identify the Multicast prefix
ff00::/8 covers all multicast traffic.
IPv6 uses multicast exclusively instead of broadcast; all multicast addresses begin with ff00::/8.

Key Concept

IPv6 Address Scopes and Prefixes
Question 73Question →

An enterprise network engineer is auditing the IPv4 addressing scheme across several newly acquired branch office routers. Corporate security policy strictly mandates that all internal host interfaces must be configured within RFC 1918 private IPv4 address space to prevent internal routing leakage over the public Internet. During the audit, the engineer inspects four interface IP configurations. Which of the following IPv4 address and subnet mask assignments represents a public IPv4 host address that violates RFC 1918 guidelines?

Show answer & explanation

Answer: 172.32.14.50/20

Answer

The address 172.32.14.50/20 is a public IPv4 address because it falls outside the RFC 1918 private Class B prefix range of 172.16.0.0/12.
The RFC 1918 Class B private address space spans from 172.16.0.0 to 172.31.255.255 (CIDR prefix 172.16.0.0/12). The address 172.32.14.50 has a second octet of 32, placing it outside the private address block and into public IPv4 space.

Step-by-Step Solution

1
Recall the defined RFC 1918 private IPv4 address blocks
Class A: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), Class B: 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), Class C: 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
Identifying private space requires strict matching against the starting and ending boundaries of RFC 1918 blocks.
2
Evaluate the second octet of the Class B candidate addresses
The address 172.31.240.100 has a second octet of 31, which is inside the range 16–31. The address 172.32.14.50 has a second octet of 32, which is outside the range 16–31.
The /12 prefix for Class B private space covers second octet values from 16 to 31 inclusive (172.16.0.0−172.31.255.255172.16.0.0 - 172.31.255.255).
3
Determine which address violates RFC 1918 private designation
172.32.14.50 is public and cannot be routed across private networks without public IP ownership.
Addresses starting with 172.32.x.x are allocated globally by IANA as public IP addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Estimated Time:1m 30s
Question 74Question →

A network technician is reviewing transport layer protocol characteristics to evaluate protocol overhead. Which statement correctly describes the header size of UDP compared to TCP?

Show answer & explanation

Answer: UDP operates with a fixed header size of 8 bytes, whereas TCP has a minimum header size of 20 bytes.

Answer

UDP operates with a fixed header size of 8 bytes, whereas TCP has a minimum header size of 20 bytes.
UDP headers consist of four 2-byte fields (Source Port, Destination Port, Length, Checksum), resulting in a fixed size of 8 bytes. In contrast, TCP headers require a minimum of 20 bytes (up to 60 bytes with options) to accommodate fields such as Sequence Number, Acknowledgment Number, Data Offset, Flags, Window Size, and Urgent Pointer required for reliable, connection-oriented data transfer.

Step-by-Step Solution

1
Analyze UDP header structure
UDP contains 4 fields (Source Port, Destination Port, Length, Checksum) at 2 bytes each, totaling 8 bytes.
UDP provides connectionless delivery with minimal protocol overhead.
2
Analyze TCP header structure
TCP header includes sequence numbers, acknowledgment numbers, flags, window size, and checksum, requiring a minimum of 20 bytes without options.
TCP requires additional fields to guarantee stateful, reliable connection delivery.
3
Compare header overhead
UDP uses an 8-byte header and TCP uses a minimum 20-byte header.
Direct comparison identifies UDP as having lower protocol overhead than TCP.

Key Concept

TCP vs UDP Header Size Comparison
Question 75Question →

A network technician installs a standard Layer 2 Ethernet switch to connect multiple client computers in an office network. What is the primary operational function of this device?

Show answer & explanation

Answer: Forwarding Ethernet frames based on destination MAC addresses while separating collision domains per port

Answer

The primary operational function of a Layer 2 switch is forwarding Ethernet frames using MAC addresses and placing each switch port into its own independent collision domain.
A standard Layer 2 switch learns source MAC addresses and builds a MAC address table to forward incoming frames to their intended destination ports. Each physical port on the switch acts as an isolated collision domain, preventing frame collisions.

Step-by-Step Solution

1
Identify the OSI operational layer of a standard Ethernet switch.
Standard Layer 2 switches operate at the Data Link Layer (Layer 2).
Layer 2 switches process Ethernet frame headers rather than inspecting Layer 3 IP packet headers for forwarding decisions.
2
Determine the forwarding logic and domain boundaries established by the switch.
The switch inspects destination MAC addresses to forward frames and isolates collision domains on each individual port, while leaving all ports in a single broadcast domain by default.
Port micro-segmentation eliminates collisions on full-duplex Ethernet connections while preserving broadcast reachability.

Key Concept

Layer 2 Switch Roles and Collision Domain Isolation
Question 76Question →

Match each Cisco IOS interface line status or counter symptom on the left to its most likely physical or data link layer cause on the right.

Click a left item, then click its matching right item

Items

Interface status is 'GigabitEthernet0/1 is down, line protocol is down'
Interface status is 'FastEthernet0/1 is up, line protocol is down'
Interface status is 'GigabitEthernet0/2 is up, line protocol is up' with rapidly incrementing late collisions
Interface status is 'FastEthernet0/2 is administratively down, line protocol is down'

Matches

Show answer & explanation

Answer

The interface conditions match as follows: 'down/down' indicates a Layer 1 physical carrier loss; 'up/down' indicates a Layer 2 framing or encapsulation failure; 'late collisions' on an operational interface indicate a duplex mismatch; and 'administratively down' indicates the port is disabled by configuration.
In Cisco IOS interface diagnostics: physical layer carrier loss generates 'down/down'; data-link framing or keepalive failures generate 'up/down'; duplex mismatches generate late collisions; and administrative shutdown settings generate 'administratively down'.

Step-by-Step Solution

1
Analyze the 'down/down' state symptom.
Identified Layer 1 Physical connection failure.
When both hardware and line protocol report down, physical signal detection has failed completely.
2
Analyze the 'up/down' state symptom.
Identified Layer 2 Data Link framing or protocol failure.
The physical medium is receiving carrier signals, but data link frames or keepalives are not being successfully negotiated.
3
Analyze late collisions on an up/up link.
Identified duplex mismatch condition.
Late collisions happen when a full-duplex port sends frames without checking for carrier sense while the connected half-duplex port transmits simultaneously.
4
Analyze the 'administratively down' state symptom.
Identified local software configuration state ('shutdown').
Cisco IOS explicitly marks interfaces that have not been enabled with 'no shutdown' as administratively down.

Key Concept

Cisco IOS interface line status, protocol states, and error counter interpretation
Question 77Question →

A network engineer is troubleshooting severe wireless performance degradation in an enterprise cafeteria. Spectrum analysis reveals significant non-802.11 radio frequency (RF) interference originating from operating microwave ovens and legacy Bluetooth IoT sensors. Which modification to the wireless infrastructure will best mitigate this specific source of RF interference?

Show answer & explanation

Answer: Migrate client data traffic to the 5 GHz radio band

Answer

Migrate client data traffic to the 5 GHz radio band
Migrating wireless traffic to the 5 GHz band provides an effective solution because 5 GHz operates in a separate radio frequency spectrum unaffected by 2.4 GHz consumer emissions such as microwave ovens, Bluetooth devices, and cordless phones.

Step-by-Step Solution

1
Identify the RF frequency spectrum shared by the interference sources.
Microwave ovens and Bluetooth devices radiate RF energy within the 2.4 GHz2.4\text{ GHz} ISM frequency band (2.400 GHz2.400\text{ GHz} to 2.4835 GHz2.4835\text{ GHz}).
Understanding the physical band limitations isolates the cause of non-802.11 interference.
2
Evaluate alternative frequency bands available in enterprise wireless deployments.
The 5 GHz5\text{ GHz} frequency band operates completely outside the 2.4 GHz2.4\text{ GHz} range and offers significantly more non-overlapping channels unaffected by microwave radiation or Bluetooth signals.
Shifting wireless traffic to 5 GHz5\text{ GHz} bypasses the polluted spectrum entirely.

Key Concept

RF Interference and Frequency Band Characteristics (2.4 GHz vs 5 GHz)
Question 78Question →

A network administrator is configuring IPv6 auto-configuration using SLAAC and EUI-64 process on Cisco router interfaces. Match each 48-bit MAC address on the left to its corresponding EUI-64 derived IPv6 Link-Local address on the right.

Click a left item, then click its matching right item

Items

0012.3456.789A
0212.3456.789A
1012.3456.789A
1212.3456.789A

Matches

Show answer & explanation

Answer

MAC 0012.3456.789A matches fe80::212:34ff:fe56:789a; MAC 0212.3456.789A matches fe80::12:34ff:fe56:789a; MAC 1012.3456.789A matches fe80::1212:34ff:fe56:789a; MAC 1212.3456.789A matches fe80::1012:34ff:fe56:789a.
Each MAC address is correctly converted to EUI-64 format by inserting FFFE into the middle of the 48-bit address and inverting the 7th bit (the Universal/Local bit) of the first byte. The resulting 64-bit interface ID is appended to the Link-Local prefix fe80::/64, with leading zeros in any 16-bit block omitted per standard IPv6 address formatting rules.

Step-by-Step Solution

1
Split each MAC address into its OUI (first 24 bits) and NIC-specific extension (last 24 bits), and insert FFFE in hex between them.
For MAC 0012.3456.789A, the split sequence becomes 00-12-34-FF-FE-56-78-9A.
EUI-64 expansion requires inserting the 16-bit reserved value FFFE into the center of a 48-bit MAC address.
2
Invert the 7th bit (Universal/Local bit) of the first byte in binary representation.
Byte 0x00 (00000000200000000_2) becomes 0x02 (00000010200000010_2); 0x02 becomes 0x00; 0x10 (00010000200010000_2) becomes 0x12 (00010010200010010_2); 0x12 becomes 0x10.
IEEE EUI-64 specification requires flipping the 7th bit of the first octet to represent global/local scope.
3
Combine the inverted 64-bit interface ID with the fe80::/10 link-local prefix (defaulting to /64 subnet prefix fe80::/64) and apply standard RFC 4291 zero compression rules.
The 64-bit interface ID 0012:34ff:fe56:789a compresses leading zeros to 12:34ff:fe56:789a, resulting in fe80::12:34ff:fe56:789a.
Standard IPv6 address formatting suppresses leading zeros in each 16-bit hex field.

Key Concept

EUI-64 Interface Identifier Generation and SLAAC Link-Local Addressing
Question 79Question →

A network technician is configuring an isolated staging environment and must assign a dedicated IPv4 subnet using unroutable addresses specified in RFC 1918. Which of the following network prefixes represents a valid private IPv4 address block according to RFC 1918?

Show answer & explanation

Answer: 172.25.0.0/16

Answer

172.25.0.0/16 is the valid RFC 1918 private IPv4 network prefix.
The prefix 172.25.0.0/16 lies within the 172.16.0.0/12 block reserved by RFC 1918 for private IPv4 networks (spanning from 172.16.0.0 to 172.31.255.255).

Step-by-Step Solution

1
Recall the defined RFC 1918 private IPv4 address ranges
Class A: 10.0.0.0/8 (10.0.0.0 – 10.255.255.255), Class B: 172.16.0.0/12 (172.16.0.0 – 172.31.255.255), Class C: 192.168.0.0/16 (192.168.0.0 – 192.168.255.255).
RFC 1918 explicitly reserves these three specific IP address blocks for private internal networks.
2
Evaluate the candidate prefixes against the RFC 1918 boundaries
The prefix 172.25.0.0/16 is inside the Class B range of 172.16.0.0 to 172.31.255.255. All other options fall outside the private boundaries (172.33.0.0/16, 192.169.1.0/24, and 11.0.0.0/8 are all public IPv4 ranges).
Addresses outside the three defined blocks are globally routable public addresses.

Key Concept

RFC 1918 Private IPv4 Address Ranges
Question 80Question →

In network infrastructure virtualization, hypervisors are categorized based on their relationship with the underlying physical hardware. Which statement accurately describes the operation of a Type 1 hypervisor?

Show answer & explanation

Answer: It installs directly on server bare-metal hardware and manages virtual machine resource access without requiring a host operating system.

Answer

A Type 1 hypervisor installs directly on server bare-metal hardware and manages virtual machine resource access without requiring a host operating system.
Type 1 (bare-metal) hypervisors run directly on server physical hardware without an intervening host operating system. This provides direct resource scheduling, low latency, and enhanced reliability for enterprise virtual machine workloads.

Step-by-Step Solution

1
Identify the primary distinction in hypervisor architecture.
Hypervisors are classified as Type 1 (bare-metal) or Type 2 (hosted) depending on whether an underlying host operating system is present.
Type 1 hypervisors sit directly between the physical hardware and the virtual machine operating systems.
2
Evaluate the choices to find the description matching Type 1 virtualization.
Direct installation on physical bare-metal hardware without an intermediate host operating system defines a Type 1 hypervisor.
Direct hardware control minimizes overhead and improves resource management in enterprise deployments.

Key Concept

Type 1 (Bare-Metal) vs. Type 2 (Hosted) Hypervisor Architecture
PreviousPage 4 / 20Next
Network Fundamentals Practice Questions — Cisco CCNA — Page 4 | Examkin