Examkin

Network Fundamentals

398 questions

All types398Multiple choice205Multiple select92Numeric18Matching68Ordering7Short answer8
Question 41Question →

A network engineer is troubleshooting performance degradation on a link between Switch-A and Switch-B. The engineer executes the command `show interfaces fastEthernet 0/1` on Switch-A and observes the following CLI output:

text
FastEthernet0/1 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is 0007.eb78.8901 (bia 0007.eb78.8901)
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)
Full-duplex, 100Mb/s, media type is 100BaseTX
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
5 minute input rate 12000 bits/sec, 15 packets/sec
5 minute output rate 15000 bits/sec, 18 packets/sec
482910 packets input, 54910284 bytes, 0 no buffer
0 runts, 0 giants, 0 throttles
8942 input errors, 8942 CRC, 0 frame, 0 overrun, 0 ignored
512049 packets output, 61029481 bytes, 0 underruns
0 output errors, 0 collisions, 0 late collision, 0 deferred

Meanwhile, the connected interface on Switch-B reports `Half-duplex, 100Mb/s` and shows a rapidly incrementing counter for late collisions and deferred transmissions. Which of the following is the root cause of this troubleshooting issue?

Show answer & explanation

Answer: Switch-A is manually configured for full duplex while Switch-B relies on auto-negotiation, forcing Switch-B to default to half duplex.

Answer

Switch-A is manually configured for full duplex while Switch-B relies on auto-negotiation, forcing Switch-B to default to half duplex.
The correct answer identifies a classic duplex mismatch scenario. When Switch-A is manually set to full duplex, it stops participating in auto-negotiation. Switch-B, left on auto-negotiation, can sense the 100 Mbps link speed via fast link pulses (FLP) but cannot negotiate the duplex setting. Following IEEE rules, Switch-B falls back to half duplex. Switch-A transmits whenever it has data, while Switch-B attempts CSMA/CD. This causes Switch-B to see late collisions and Switch-A to record CRC input errors.

Step-by-Step Solution

1
Analyze the interface output on Switch-A
Switch-A is operating at Full-duplex 100Mb/s, has 0 collisions/late collisions recorded, but shows a high number of input errors and CRC errors.
Full-duplex interfaces do not perform carrier sense multiple access with collision detection (CSMA/CD), so they never register collisions. However, incoming frames from a half-duplex partner transmitting during local transmissions will be truncated or corrupted, resulting in CRC errors.
2
Analyze the counter symptoms on Switch-B
Switch-B operates at Half-duplex and increments late collisions and deferred packets.
Because Switch-B is in half-duplex mode, it uses CSMA/CD. When Switch-A transmits continuously in full duplex, Switch-B detects collisions past the 64-byte slot time (late collisions).
3
Determine the cause of the duplex asymmetry
Disabling auto-negotiation on one end (hardcoding Switch-A to Full) causes the auto-negotiating peer (Switch-B) to fall back to the standard default of Half-duplex.
Cisco and IEEE 802.3 standards require auto-negotiation on both ends or manual configuration on both ends. Mixing hardcoded settings with auto-negotiation results in a duplex mismatch.

Key Concept

Ethernet Auto-Negotiation and Duplex Mismatch Troubleshooting
Question 42Question →

An enterprise network deployment uses Cisco Lightweight Access Points (LAPs) operating in a Centralized Split-MAC architecture managed by a Wireless LAN Controller (WLC). During high-density traffic analysis, an engineer must verify which frame processing tasks are handled locally by the AP in real time to minimize latency. Which function is executed directly by the Lightweight AP rather than being processed by the Wireless LAN Controller?

Show answer & explanation

Answer: Transmission of 802.11 beacon frames and processing of real-time 802.11 frame acknowledgments

Answer

Transmission of 802.11 beacon frames and processing of real-time 802.11 frame acknowledgments
Under Cisco Split-MAC architecture, time-sensitive (real-time) 802.11 protocol functions are executed directly on the Lightweight Access Point. These include beacon transmission, probe responses, MAC-level frame acknowledgments (ACKs), frame buffering/queuing, and signal strength measurements.

Step-by-Step Solution

1
Analyze the Split-MAC architecture division of responsibilities in Cisco centralized wireless networks.
Split-MAC divides 802.11 protocol handling between real-time MAC functions and management/non-real-time MAC functions.
Real-time functions must react within microsecond thresholds directly on the AP radio hardware.
2
Identify AP-specific real-time MAC functions.
The AP performs beacon generation, probe responses, 802.11 MAC layer acknowledgments (ACK), frame buffering, and Layer 1/2 encryption/decryption.
Sending real-time ACKs or beacons back and forth across a CAPWAP tunnel to a WLC would introduce intolerable latency.
3
Identify WLC-specific management functions.
The WLC manages 802.11 authentication, association/reassociation processing, 802.1X/EAP key handshakes, RRM, and CAPWAP tunnel termination.
Centralizing management policy ensures seamless mobility, central security control, and global RF optimization.

Key Concept

Split-MAC Architecture Division of Responsibilities
Question 43Question →

Refer to the following Cisco IOS CLI output from a switch interface:

text
Switch# show interfaces gigabitEthernet 0/1
GigabitEthernet0/1 is up, line protocol is up (connected)
Hardware is GigabitEthernet, address is 0007.7d04.1a01
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 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:01, output 00:00:00, 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 12000 bits/sec, 15 packets/sec
5 minute output rate 45000 bits/sec, 32 packets/sec
41205 packets input, 5142091 bytes, 0 no buffer
Received 104 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
58912 packets output, 7120491 bytes, 0 underruns
3412 output errors, 3290 late collisions, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output

Based on the output, which condition is the most probable cause of the accumulated interface errors?

Show answer & explanation

Answer: The local interface is operating in half-duplex mode while the connected neighbor is hardcoded for full-duplex mode.

Answer

The local interface is operating in half-duplex mode while the connected neighbor is hardcoded for full-duplex mode.
The combination of an 'up/up' link status, half-duplex local operational mode, and high late collision counts specifically indicates a duplex mismatch. When the remote device is manually set to full-duplex, auto-negotiation on the local device fails to detect duplex and falls back to half-duplex. As the full-duplex neighbor transmits at will without checking carrier sense, it interrupts ongoing local transmissions after the 64-byte collision window, causing late collisions to increment on the half-duplex side.

Step-by-Step Solution

1
Analyze line status and line protocol state.
Interface status is 'up' and line protocol is 'up', confirming physical Layer 1 connectivity and Layer 2 framing operational state.
This rules out physical disconnection or complete cable pinout failures.
2
Examine operating duplex settings and interface error counters.
The interface operates at 'Half-duplex, 100Mb/s' and shows significant 'late collisions' (3,290) and 'output errors' (3,412), but 0 CRC/input errors.
Late collisions occur when a collision is detected after the first 64 bytes (512 bits) of a frame have been transmitted.
3
Correlate symptoms with duplex operation mechanics.
Late collisions on a half-duplex interface are a textbook symptom of a duplex mismatch, occurring because the remote full-duplex node transmits while the local half-duplex node is midway through sending a frame.
In auto-negotiation fallback, if one side is set manually to full-duplex, the auto-negotiating side defaults to half-duplex, creating this exact symptom pattern.

Key Concept

Duplex Mismatch Identification via Interface Counters
Estimated Time:2m 0s
Question 44Question →

Network administrators deploy various hardware devices to perform specific roles within an enterprise network infrastructure. Match each network component on the left to its primary operational function on the right.

Click a left item, then click its matching right item

Items

Router
Layer 2 Switch
Next-Generation Firewall (NGFW)
Wireless LAN Controller (WLC)

Matches

Show answer & explanation

Answer

Router matches with 'Forwards packets between distinct IPv4/IPv6 subnets based on Layer 3 IP addresses.'; Layer 2 Switch matches with 'Forwards frames based on Layer 2 MAC addresses and separates collision domains.'; Next-Generation Firewall (NGFW) matches with 'Inspects deep application-layer traffic and enforces stateful security policies.'; Wireless LAN Controller (WLC) matches with 'Centrally manages lightweight access points, wireless SSIDs, and radio resources.'
Each network component is correctly paired with its primary operational layer and function in enterprise architecture: Routers for inter-subnet Layer 3 packet forwarding, Layer 2 switches for intra-subnet Ethernet frame switching, NGFWs for security filtering, and WLCs for central wireless management.

Step-by-Step Solution

1
Identify Layer 3 forwarding device
Router matches with forwarding packets between IP subnets.
Routers make forwarding decisions based on Layer 3 IP routing tables to interconnect different subnets.
2
Identify Layer 2 switching device
Layer 2 Switch matches with forwarding frames using MAC addresses.
Layer 2 switches operate within a single broadcast domain and make forwarding decisions using MAC address tables.
3
Identify perimeter security device
NGFW matches with inspecting application-layer traffic and stateful policies.
Firewalls filter network traffic based on security rules, state tables, and application signatures.
4
Identify centralized wireless management component
WLC matches with managing lightweight access points centrally.
WLCs aggregate control-plane functionality for Lightweight APs (LAP/CAPWAP).

Key Concept

Core roles and functions of enterprise network devices
Question 45Question →

Match each wireless radio frequency (RF) propagation behavior on the left with its corresponding physical effect on Wi-Fi signals on the right.

Click a left item, then click its matching right item

Items

Absorption
Reflection
Refraction
Scattering

Matches

Show answer & explanation

Answer

Absorption pairs with RF energy being converted to heat through dense materials; Reflection pairs with the signal bouncing off large flat conductive surfaces; Refraction pairs with signal bending through medium density changes; Scattering pairs with signal dispersion across rough or small obstacles.
Absorption describes energy loss in dense obstacles, Reflection describes signals bouncing off smooth metal surfaces, Refraction describes signal bending through media density changes, and Scattering describes multi-directional dispersion off irregular surfaces.

Step-by-Step Solution

1
Identify the mechanism of signal attenuation caused by solid building materials.
Absorption is the physical conversion of RF energy into heat as it penetrates dense obstacles.
Materials like concrete and brick absorb RF energy.
2
Identify the behavior when RF encounters large flat metallic objects.
Reflection is the bouncing back of an RF wave from a large conductive boundary.
Smooth metallic surfaces act as reflectors for wireless signals.
3
Identify the behavior associated with signal bending.
Refraction is the deflection of an RF wave passing through media of varying density.
Changes in medium propagation speed cause the wave vector to change direction.
4
Identify the behavior when signals hit small or non-uniform objects.
Scattering causes multi-directional redirection of RF energy.
Irregular boundaries prevent cohesive specular reflection.

Key Concept

RF Propagation Behaviors in Wireless Networks
Question 46Question →

A network administrator is provisioning a new VLAN for an enterprise VoIP deployment that requires support for up to 500500 usable IP phones. The network block allocated for this subnetwork starts at 172.25.100.0172.25.100.0. To accommodate the required number of host devices while minimizing unallocated address space, what is the broadcast address of this subnetwork?

Show answer & explanation

Answer: 172.25.101.255172.25.101.255

Answer

The broadcast address of the subnetwork is 172.25.101.255172.25.101.255.
To support 500 usable host devices, 9 host bits are required (29−2=5102^9 - 2 = 510 hosts). This yields a prefix length of /23/23 (32−9=2332 - 9 = 23). Starting at network address 172.25.100.0172.25.100.0, a /23/23 subnet encompasses the range 172.25.100.0172.25.100.0 through 172.25.101.255172.25.101.255, making 172.25.101.255172.25.101.255 the correct broadcast address.

Step-by-Step Solution

1
Determine the minimum number of host bits required.
n=9n = 9 host bits because 29−2=510≥5002^9 - 2 = 510 \ge 500.
A host bit count of 8 (28−2=2542^8 - 2 = 254) is insufficient for 500 hosts.
2
Calculate the prefix length and subnet mask.
Prefix length is /23/23 (32−9=2332 - 9 = 23), corresponding to subnet mask 255.255.252.0255.255.252.0.
Subtracting 9 host bits from 32 total bits yields a 23-bit network prefix.
3
Determine the subnet boundaries for 172.25.100.0/23172.25.100.0/23.
Network address is 172.25.100.0172.25.100.0, usable host range is 172.25.100.1172.25.100.1 to 172.25.101.254172.25.101.254, and the broadcast address is 172.25.101.255172.25.101.255.
The block size in the third octet for a /23 subnet is 256−252=4256 - 252 = 4 or 21=22^1 = 2, spanning 172.25.100.0172.25.100.0 through 172.25.101.255172.25.101.255.

Key Concept

Subnet Mask Derivation and Broadcast Address Calculation
Estimated Time:1m 30s
Question 47Question →

A network administrator is selecting an IPv4 subnetwork block for a new internal department segment that requires support for up to 6060 usable host interfaces. The network design policy requires using an RFC 1918 private IPv4 address block and selecting the most efficient prefix length to avoid wasting addresses. Which subnetwork address and CIDR prefix satisfies all requirements?

Show answer & explanation

Answer: 10.40.16.0/2610.40.16.0/26

Answer

The subnetwork 10.40.16.0/2610.40.16.0/26 meets all design requirements by using an RFC 1918 private IPv4 address and providing 6262 usable host IP addresses, which is the most efficient subnet size for 6060 hosts.
The subnetwork 10.40.16.0/2610.40.16.0/26 utilizes an address within the RFC 1918 Class A private block (10.0.0.0/810.0.0.0/8). A /26/26 prefix leaves 66 host bits (32−26=632 - 26 = 6), providing 26−2=622^6 - 2 = 62 usable host IP addresses. This accommodates the required 6060 host interfaces with the minimum possible address waste.

Step-by-Step Solution

1
Determine the required number of host bits (hh) for 6060 usable hosts
Using the formula 2h−2≥602^h - 2 \ge 60, we test h=5→30h = 5 \rightarrow 30 usable hosts (too small) and h=6→62h = 6 \rightarrow 62 usable hosts (sufficient). Thus, 66 host bits are needed.
Two addresses in every IPv4 subnet are reserved for the network ID and the directed broadcast address.
2
Calculate the CIDR prefix length
Prefix length =32−6=/26= 32 - 6 = /26.
An IPv4 address consists of 32 total bits.
3
Verify RFC 1918 private IPv4 address range compliance
10.40.16.010.40.16.0 is inside the 10.0.0.0/810.0.0.0/8 private address block (10.0.0.010.0.0.0 to 10.255.255.25510.255.255.255).
RFC 1918 defines private address spaces: 10.0.0.0/810.0.0.0/8, 172.16.0.0/12172.16.0.0/12, and 192.168.0.0/16192.168.0.0/16.

Key Concept

IPv4 Subnet Sizing and RFC 1918 Private Addressing
Question 48Question →

A network engineer is troubleshooting various network interface issues on Cisco switches and routers. Match each interface status or error counter symptom on the left with its most likely physical or data-link layer root cause on the right.

Click a left item, then click its matching right item

Items

Interface status is down, line protocol is down
Interface status is up, line protocol is down
Interface status is up, line protocol is up, with rapidly incrementing late collisions
Interface status is up, line protocol is up, with rapidly incrementing giants and jabber errors

Matches

Show answer & explanation

Answer

The interface symptoms match as follows: 'down/down' corresponds to a Layer 1 physical fault; 'up/down' corresponds to a Layer 2 framing or keepalive failure; incrementing late collisions corresponds to a half-duplex/full-duplex mismatch; and incrementing giants/jabbers corresponds to oversized frames or a defective NIC.
Each status pattern and counter maps directly to standard Cisco IOS interface troubleshooting logic: Layer 1 physical link failures cause 'down/down'; Layer 2 framing/keepalive failures cause 'up/down'; half-duplex operating against full-duplex causes late collisions; and frames exceeding 1518 bytes with invalid FCS register as giants/jabber errors.

Step-by-Step Solution

1
Analyze interface states by differentiating Layer 1 (Line Status) from Layer 2 (Line Protocol).
Line status indicates physical carrier detection, whereas line protocol indicates data link layer framing and keepalive state.
A physical failure results in 'down/down', whereas a framing or encapsulation mismatch maintains physical link ('up') but drops data link signaling ('down').
2
Diagnose the cause of late collision error counters on Ethernet interfaces.
Late collisions indicate that collision detection occurred after transmitting 512 bits (64 bytes).
Because half-duplex expects collisions only during the slot time (first 64 bytes), late collisions uniquely signal that the remote peer is operating in full-duplex mode and ignoring CSMA/CD rules.
3
Evaluate framing error statistics such as giants and jabbers.
Giants represent frames larger than the standard Ethernet MTU (1518 bytes) with bad CRC, while jabbers represent invalid continuous signals.
These symptoms point directly to MTU misconfigurations or damaged Network Interface Cards (NICs) transmitting invalid frame sizes.

Key Concept

Interface Line Status Combinations and Error Counter Root Causes
Question 49Question →

A network architect is establishing standard address allocations and boundary checks for an enterprise network redesign. Match each IPv4 address block or prefix range on the left with its corresponding RFC 1918 classification, CIDR specifications, or Internet routing characteristics on the right.

Click a left item, then click its matching right item

Items

10.0.0.0/810.0.0.0/8
172.16.0.0/12172.16.0.0/12
192.168.0.0/16192.168.0.0/16
172.32.0.0/11172.32.0.0/11

Matches

Show answer & explanation

Answer

10.0.0.0/8 matches the single Class A private block (10.0.0.0 to 10.255.255.255); 172.16.0.0/12 matches the 16 contiguous Class B private subnets (172.16.0.0 to 172.31.255.255); 192.168.0.0/16 matches the 256 contiguous Class C private subnets (192.168.0.0 to 192.168.255.255); 172.32.0.0/11 matches the globally routable public address space.
Each item matches its corresponding RFC 1918 definition or boundary specification correctly: 10.0.0.0/8 is the single Class A private block, 172.16.0.0/12 spans 16 contiguous Class B private /16 networks (172.16.0.0 - 172.31.255.255), 192.168.0.0/16 spans 256 Class C /24 networks (192.168.0.0 - 192.168.255.255), and 172.32.0.0/11 consists of public addresses immediately above the 172.31.255.255 RFC 1918 upper bound.

Step-by-Step Solution

1
Identify the Class A RFC 1918 block
10.0.0.0/810.0.0.0/8 encompasses the host range 10.0.0.010.0.0.0 to 10.255.255.25510.255.255.255 (16,777,21616,777,216 addresses).
RFC 1918 reserves one /8/8 prefix in the 10.0.0.0 network space for private internal use.
2
Analyze the Class B RFC 1918 block and boundary limits
172.16.0.0/12172.16.0.0/12 encompasses 16 contiguous /16/16 blocks (172.16.0.0172.16.0.0 through 172.31.255.255172.31.255.255).
The prefix length /12/12 spans from 172.16.0.0172.16.0.0 up to 172.31.255.255172.31.255.255. Addresses starting with 172.32.0.0172.32.0.0 are public.
3
Identify the Class C RFC 1918 block
192.168.0.0/16192.168.0.0/16 encompasses 256 contiguous /24/24 subnets (192.168.0.0192.168.0.0 through 192.168.255.255192.168.255.255).
RFC 1918 defines a single /16/16 prefix block within the 192.168.0.0 space for Class C private addressing.
4
Distinguish public ranges from RFC 1918 private ranges
172.32.0.0/11172.32.0.0/11 starts at 172.32.0.0172.32.0.0, which is beyond the 172.31.255.255172.31.255.255 boundary and is therefore public.
Any IP address in the range 172.32.0.0172.32.0.0 to 172.63.255.255172.63.255.255 is public and routable on the global Internet.

Key Concept

RFC 1918 Private IPv4 Address Space Ranges and Public Boundaries
Estimated Time:2m 0s
Question 50Question →

A company operates several branch offices connected to a main data center where a centralized Wireless LAN Controller (WLC) resides. Following a WAN link outage at one branch, local wireless users at that site can still access local printers and file servers, even though their CAPWAP control connection to the WLC is temporarily down. Which operational mode must be configured on the branch lightweight access points (LAPs) to support local data switching when WLC reachability is lost?

Show answer & explanation

Answer: FlexConnect mode

Answer

FlexConnect mode
FlexConnect mode allows lightweight access points deployed at remote branch sites to locally switch user traffic onto the local VLAN without sending it across the CAPWAP data tunnel to the centralized controller. When the WAN link fails and controller reachability is lost, FlexConnect APs can operate in standalone mode, preserving local client connectivity.

Step-by-Step Solution

1
Analyze the operational requirements of the branch office deployment
The branch access points must maintain local client traffic forwarding even when the WAN connection to the centralized Wireless LAN Controller fails.
Centralized WLC architectures typically tunnel all client data to the controller via CAPWAP, creating a dependency on WAN availability unless a localized switching mode is enabled.
2
Evaluate Cisco Lightweight Access Point (LAP) operational modes
FlexConnect mode (formerly known as HREAP) is specifically designed for remote branch deployments to allow local traffic switching at the AP level when the CAPWAP control tunnel to the centralized WLC drops.
In Local mode, an AP drops client associations if controller connection fails because all user data MUST pass through the CAPWAP tunnel.

Key Concept

Lightweight Access Point Operational Modes (FlexConnect vs Local)
Estimated Time:1m 15s
Question 51Question →

A technician connects two legacy switch ports directly to each other using a standard straight-through Ethernet cable. Neither port supports Automatic Medium-Dependent Interface Crossover (Auto-MDIX). Running a status check on the local switch port yields the following CLI output:

text
FastEthernet0/1 is down, line protocol is down
Hardware is FastEthernet, address is 000d.bd2c.4a01 (bia 000d.bd2c.4a01)
MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set

Which physical cabling issue is the direct cause of the interface remaining in a down/down state?

Show answer & explanation

Answer: A straight-through Ethernet cable was used instead of a crossover Ethernet cable to connect two like switch devices.

Answer

Using a straight-through Ethernet cable instead of a crossover cable to connect two switch ports (like devices) without Auto-MDIX support prevents physical link establishment, resulting in a down/down interface state.
Switches are MDI-X devices that transmit on pins 3 and 6 and receive on pins 1 and 2. When connecting two switches together directly without Auto-MDIX functionality, a crossover cable must be used to map transmit pins on one switch to receive pins on the other switch. Using a straight-through cable connects transmit pins to transmit pins, resulting in no electrical link and keeping the interface state down/down.

Step-by-Step Solution

1
Analyze the CLI interface state
The interface status shows 'FastEthernet0/1 is down, line protocol is down', indicating a Layer 1 physical link failure.
When both line status and line protocol are down, the physical layer cannot detect electrical signaling or link integrity.
2
Evaluate device pinout roles and cable types
Switches use MDI-X pinouts (transmitting on pins 3/6 and receiving on pins 1/2). Connecting MDI-X to MDI-X requires a crossover cable to map transmit pins to receive pins.
Without Auto-MDIX to automatically adjust pin roles, a straight-through cable connects transmit pins directly to transmit pins, preventing link detection.

Key Concept

Ethernet cable pinouts and physical interface troubleshooting (straight-through vs crossover cable selection)
Question 52Question →

A network architect is designing a high-density Wi-Fi deployment across an enterprise facility with reinforced concrete walls and heavy multipath interference. During site survey planning, the architect must select between using 2.4 GHz channels (11, 66, 1111) and 5 GHz channels (3636, 4040, 4444, 4848) for coverage while maintaining non-overlapping channel designs and minimizing free-space path loss and attenuation. Which statement accurately reflects the physical radio frequency (RF) propagation characteristics and channel planning constraints between these two frequency bands in this scenario?

Show answer & explanation

Answer: The 2.4 GHz band experiences lower attenuation through solid obstacles compared to 5 GHz, but offers fewer non-overlapping channels in the US regulatory domain, making high-density channel reuse more susceptible to co-channel interference.

Answer

The 2.4 GHz band experiences lower attenuation through solid obstacles compared to 5 GHz, but offers fewer non-overlapping channels in the US regulatory domain, making high-density channel reuse more susceptible to co-channel interference.
The 2.4 GHz frequency band operates at longer wavelengths than 5 GHz, resulting in lower attenuation when passing through solid barriers like reinforced concrete walls. However, because the 2.4 GHz ISM band only contains 3 non-overlapping 20 MHz channels (channels 1, 6, and 11 in standard regulatory domains), high-density deployments using 2.4 GHz quickly run out of channels, leading to co-channel interference.

Step-by-Step Solution

1
Analyze signal propagation and attenuation across frequency bands.
Lower frequencies (2.4 GHz) have longer wavelengths, resulting in lower free-space path loss and greater ability to penetrate physical obstacles such as concrete walls compared to higher frequencies (5 GHz).
RF signal attenuation increases as frequency increases.
2
Evaluate channel availability for co-channel interference mitigation.
2.4 GHz only has 3 non-overlapping 20 MHz channels (1, 6, 11) in North America, whereas 5 GHz provides many more non-overlapping channels.
High-density access point deployments require multiple non-overlapping channels to avoid co-channel interference.
3
Synthesize propagation characteristics and channel planning constraints.
2.4 GHz penetrates solid obstacles better, but its limited count of 3 non-overlapping channels severely restricts high-density channel reuse compared to 5 GHz.
Balancing coverage (attenuation) with capacity (channel availability) is a core wireless architecture decision.

Key Concept

RF Propagation and Channel Planning Differences Between 2.4 GHz and 5 GHz
Question 53Question →

An enterprise data center infrastructure deploys virtualized server hosts running Type 1 hypervisors. On a single physical host, multiple Virtual Machines (VMs) belong to different VLANs. Network monitoring reveals that intra-VLAN frame delivery between VMs on the host occurs locally without utilizing physical switch bandwidth, whereas inter-VLAN traffic between VMs on the same host must be forwarded out to an external Layer 3 gateway device. Which component operating within the hypervisor framework is responsible for performing local Layer 2 frame forwarding while enforcing VLAN isolation on the host?

Show answer & explanation

Answer: The internal virtual switch (vSwitch) provisioned within the hypervisor software

Answer

The internal virtual switch (vSwitch) provisioned within the hypervisor software is responsible for switching intra-VLAN frames locally on the physical host while leaving inter-VLAN forwarding to a Layer 3 routing boundary.
The internal virtual switch (vSwitch) operates at Layer 2 within the hypervisor software environment. It inspects Ethernet frame headers and MAC addresses to bridge traffic between virtual machines assigned to the same VLAN on the same physical host. Because it operates at Layer 2, frames destined for a different VLAN must be sent across a trunk link to a Layer 3 device (such as a router or L3 switch) for inter-VLAN routing.

Step-by-Step Solution

1
Analyze the operational requirements of host-internal VM communication.
Intra-VLAN traffic stays on the local host, while inter-VLAN traffic requires Layer 3 routing.
VLANs define separate broadcast domains at Layer 2. Passing traffic between different VLANs requires a routing decision.
2
Identify the software component inside a Type 1 hypervisor that handles Layer 2 frame forwarding.
The virtual switch (vSwitch) acts as a software-based Layer 2 switch connected to virtual network interface cards (vNICs) of virtual machines.
The vSwitch maintains MAC address tables per VLAN, enabling direct local frame delivery between VMs on the same VLAN without sending frames onto the physical network uplink.
3
Evaluate why inter-VLAN traffic must exit the host.
Standard Layer 2 virtual switches do not perform inter-VLAN routing unless a Layer 3 virtual router or external router interface is configured.
Without an integrated Layer 3 virtual router, inter-VLAN frames must be forwarded over physical uplinks to an external router or Layer 3 switch acting as the default gateway.

Key Concept

Hypervisor Virtual Switching and Traffic Isolation
Estimated Time:1m 30s
Question 54Question →

A network engineer is configuring interface IP addresses on a core layer switch for an internal corporate segment. Company policy strictly dictates that all internal devices must use RFC 1918 private IPv4 addresses and that addresses must be usable host assignments. Which of the following IP address and subnet mask combinations represents a valid, usable host address located strictly within the upper boundary limit of the RFC 1918 Class B private address space?

Show answer & explanation

Answer: 172.31.255.254 255.240.0.0

Answer

The address 172.31.255.254 with subnet mask 255.240.0.0 is the correct choice as it represents the highest usable host address within the RFC 1918 Class B private range.
The correct answer specifies 172.31.255.254 with mask 255.240.0.0 (/12). RFC 1918 reserves 172.16.0.0 to 172.31.255.255 for Class B private networking. In the 172.16.0.0/12 block, 172.31.255.255 is the broadcast address, making 172.31.255.254 the highest usable host address within the private Class B scope.

Step-by-Step Solution

1
Identify the exact RFC 1918 Class B private IPv4 address range boundaries.
RFC 1918 defines the Class B private address space as 172.16.0.0/12172.16.0.0/12, which encompasses IP addresses from 172.16.0.0172.16.0.0 through 172.31.255.255172.31.255.255.
Understanding exact RFC 1918 boundaries is required to filter out public IP addresses.
2
Evaluate candidate addresses against the upper boundary (172.31.255.255172.31.255.255).
172.32.0.1172.32.0.1 exceeds the upper limit and is public. 172.15.255.254172.15.255.254 is below the lower limit (172.16.0.0172.16.0.0) and is public. Both 172.31.255.254172.31.255.254 and 172.31.255.255172.31.255.255 fall inside the private range.
Only addresses between 172.16.0.0172.16.0.0 and 172.31.255.255172.31.255.255 comply with the RFC 1918 private addressing requirement.
3
Determine host address usability for the remaining compliant addresses.
For the network block, 172.31.255.255172.31.255.255 acts as a broadcast address and is unusable for host assignment. 172.31.255.254172.31.255.254 is the last valid, assignable host address in the block.
Host IP assignments must exclude the network ID and broadcast address of the given subnet.

Key Concept

RFC 1918 Private IPv4 Address Space Boundaries and Usable Host Restrictions
Question 55Question →

A network engineer is assigned the IPv4 subnetwork block 192.168.100.0/23192.168.100.0/23 for a high-density enterprise server rack. What is the maximum number of usable host IPv4 addresses that can be assigned to active network interfaces within this subnet?

Show answer & explanation

Answer: 510

Answer

510 usable host addresses
A /23/23 prefix leaves 32−23=932 - 23 = 9 bits for host addresses. Total addresses equal 29=5122^9 = 512. Subtracting 2 for the network address (192.168.100.0192.168.100.0) and broadcast address (192.168.101.255192.168.101.255) leaves exactly 510 usable host IP addresses.

Step-by-Step Solution

1
Calculate the number of host bits from the prefix length.
Host bits = 32−23=932 - 23 = 9 bits
An IPv4 address consists of 32 bits. Subtracting the prefix length yields the remaining host portion bits.
2
Calculate the total number of IPv4 addresses in the subnetwork block.
29=5122^9 = 512 total addresses
The formula 2n2^n gives the complete block size in total IP addresses.
3
Subtract reserved subnetwork and broadcast addresses to determine usable host capacity.
512−2=510512 - 2 = 510 usable hosts
The lowest address in the subnet acts as the subnet ID, and the highest address acts as the directed broadcast address; neither can be assigned to host interfaces.

Key Concept

IPv4 Usable Host Calculation
Question 56Question →

A network administrator is deploying a centralized Wireless LAN Controller (WLC) within an enterprise campus network. Which two operational functions are primary responsibilities of the WLC? (Select two.)

Select all that apply

Show answer & explanation

Answer: Automating radio frequency (RF) management and dynamic channel assignment across Lightweight Access Points; Providing centralized configuration management and security policy enforcement for managed Access Points

Answer

The primary operational responsibilities of a Wireless LAN Controller (WLC) include automating radio frequency (RF) management across Lightweight Access Points and providing centralized configuration management and security policy enforcement.
Wireless LAN Controllers (WLCs) serve as the central intelligence in a split-MAC architecture. They handle control-plane functions including dynamic radio frequency (RF) management, channel assignment, transmit power control, centralized authentication, firmware updates, and security policy distribution to lightweight access points.

Step-by-Step Solution

1
Identify the primary role of a Wireless LAN Controller (WLC) in a split-MAC architecture.
The WLC offloads control plane functions—such as provisioning, security policies, RF management, and firmware management—from lightweight access points (LAPs).
Centralizing AP management simplifies enterprise wireless deployments and ensures consistent security and performance enforcement.
2
Evaluate the candidate options to select the two valid WLC functions.
Dynamic RF management/channel assignment and centralized configuration/policy management are correct. Hypervisor virtualization functions and CDP/LLDP TLV neighbor discovery reflect unrelated hardware and protocol roles.
Only RF management and centralized configuration/policy enforcement align with WLC responsibilities.

Key Concept

Wireless LAN Controller (WLC) Roles and Operational Functions
Question 57Question →

A network engineer is configuring static IPv4 addresses for new host interfaces within a server cluster assigned the subnetwork block 172.24.16.0/21172.24.16.0/21. Which TWO of the following IPv4 addresses are valid, usable host addresses within this subnetwork?

Select all that apply

Show answer & explanation

Answer: 172.24.22.255172.24.22.255; 172.24.16.1172.24.16.1

Answer

The valid usable host addresses for the 172.24.16.0/21172.24.16.0/21 subnetwork are 172.24.22.255172.24.22.255 and 172.24.16.1172.24.16.1.
For a /21 prefix (255.255.248.0255.255.248.0), the third octet increments by 8. The network block starting at 172.24.16.0172.24.16.0 covers 172.24.16.0172.24.16.0 to 172.24.23.255172.24.23.255. The network address is 172.24.16.0172.24.16.0 and the broadcast address is 172.24.23.255172.24.23.255. Therefore, the range of usable host addresses is 172.24.16.1172.24.16.1 through 172.24.23.254172.24.23.254. Both 172.24.16.1172.24.16.1 and 172.24.22.255172.24.22.255 fall within this valid usable host range.

Step-by-Step Solution

1
Determine the subnet mask and block size for CIDR prefix /21.
A /21 prefix corresponds to the dotted-decimal subnet mask 255.255.248.0255.255.248.0. The block size in the third octet is 256−248=8256 - 248 = 8.
Calculating block size establishes the boundary interval for networks incrementing in the third octet.
2
Calculate the network address, broadcast address, and usable host range.
Network ID: 172.24.16.0172.24.16.0; Broadcast address: 172.24.23.255172.24.23.255; Usable host range: 172.24.16.1172.24.16.1 through 172.24.23.254172.24.23.254.
The third octet spans from 1616 up to 16+8−1=2316 + 8 - 1 = 23.
3
Evaluate candidate addresses against the usable host range.
172.24.16.1172.24.16.1 is the first usable host address. 172.24.22.255172.24.22.255 falls strictly between 172.24.16.1172.24.16.1 and 172.24.23.254172.24.23.254. 172.24.23.255172.24.23.255 is the reserved broadcast address. 172.32.20.5172.32.20.5 is outside the network and not in the private RFC 1918 Class B space.
Identify which candidates lie within the inclusive host boundary without matching the network or broadcast ID.

Key Concept

Subnet Boundary and Usable Host Range Calculation for Supernets/Subnets wider than /24
Question 58Question →

Match each network topology architectural layer to its primary functional responsibility within an enterprise campus or data center network.

Click a left item, then click its matching right item

Items

Campus Core Layer
Campus Access Layer
Data Center Spine Layer
Data Center Leaf Layer

Matches

Show answer & explanation

Answer

Campus Core Layer matches high-speed non-blocking backbone transport. Campus Access Layer matches direct end-user endpoint connectivity and edge policy enforcement. Data Center Spine Layer matches interconnecting all leaf switches via ECMP routing without host connections. Data Center Leaf Layer matches directly connecting servers and storage while linking to every spine switch.
Each functional layer serves a distinct architectural purpose: the Campus Core provides rapid backbone transit; the Campus Access layer connects user devices and enforces edge policies; the Data Center Spine interconnects leaf switches via ECMP without host attachments; and the Data Center Leaf connects endpoints while maintaining links to every spine.

Step-by-Step Solution

1
Identify the role of the Campus Core Layer in a 3-Tier model.
Match with high-speed packet transport without CPU-intensive filtering.
The core layer must maintain maximum packet throughput across the campus core network.
2
Identify the role of the Campus Access Layer.
Match with direct connectivity and security enforcement for user endpoints.
Access switches form the network edge where workstations and IP phones plug into the network.
3
Differentiate between Spine and Leaf layers in a Clos data center topology.
Spine switches interconnect leaf switches via ECMP, while Leaf switches connect hosts and link to all spines.
Spine switches form the core interconnect fabric without host attachment, whereas leaf switches act as access nodes for servers.

Key Concept

Campus 3-Tier and Data Center Spine-Leaf Layer Responsibilities
Question 59Question →

A network engineer is configuring a virtualized server that runs a bare-metal hypervisor. Multiple virtual machines (VMs) residing on the same host belong to different IP subnets. Which device or functional role is required to route traffic between these subnets while maintaining separate broadcast domains?

Show answer & explanation

Answer: A Layer 3 routing function (router or Layer 3 switch) that interconnects subnets and bounds broadcast traffic

Answer

A Layer 3 routing function (router or Layer 3 switch) that interconnects subnets and bounds broadcast traffic.
Inter-subnet traffic requires a Layer 3 device (router or L3 switch/vRouter). Layer 3 devices terminate Layer 2 broadcast domains, ensuring broadcast packets do not cross subnet boundaries while allowing unicast packets to be routed between different networks.

Step-by-Step Solution

1
Identify the requirement for inter-subnet communication and broadcast separation.
IP subnets represent separate Layer 3 networks, which require Layer 3 routing to forward packets between them.
Layer 2 switches only forward frames within the same broadcast domain (VLAN).
2
Evaluate the role of Layer 3 devices in broadcast domain management.
Routers and Layer 3 switches drop Layer 2 broadcast frames by default, creating boundaries for broadcast domains.
This prevents broadcast storms from traversing between distinct subnets.

Key Concept

Layer 3 Routing and Broadcast Domain Separation
Estimated Time:1m 30s
Question 60Question →

Match each enterprise network component on the left to its primary operational role on the right.

Click a left item, then click its matching right item

Items

Core Router
Wireless LAN Controller (WLC)
Layer 2 Switch
Next-Generation IPS (NGIPS)

Matches

Show answer & explanation

Answer

Core Router maps to Layer 3 path selection and broadcast domain separation; Wireless LAN Controller maps to centralized AP configuration and RF management; Layer 2 Switch maps to frame forwarding via MAC address table within a single broadcast domain; Next-Generation IPS maps to deep packet inspection for real-time malicious payload prevention.
Each component is correctly matched to its defined operational role: core routers route packets between subnets and delineate broadcast domains; WLCs manage lightweight wireless deployments centrally; Layer 2 switches forward frames using MAC tables within a broadcast domain; and NGIPS performs deep inspection on packet payloads.

Step-by-Step Solution

1
Identify the OSI layer and primary functional scope for each listed network component.
Categorize Core Router (Layer 3 routing/broadcast boundary), WLC (centralized wireless control plane), Layer 2 Switch (Layer 2 frame switching), and NGIPS (deep packet security inspection).
Matching components requires isolating their exact architectural responsibilities within enterprise network infrastructure.
2
Correlate each device with its matching operational descriptor.
Pair left_1 to right_2, left_2 to right_1, left_3 to right_4, and left_4 to right_3.
Each functional statement accurately describes the core operation of the corresponding hardware or software control component.

Key Concept

Enterprise Network Components Roles and Functions
Estimated Time:1m 30s
PreviousPage 3 / 20Next
Network Fundamentals Practice Questions — Cisco CCNA — Page 3 | Examkin