Network Fundamentals

398 questions

Question 1Question

An enterprise network team is replacing standard server deployments with hypervisor-based virtualization. During the architecture review, an engineer explains that Type 1 hypervisors provide superior performance and lower latency for enterprise workloads compared to Type 2 hypervisors. Which architectural feature directly accounts for this performance advantage in Type 1 hypervisors?

Show answer & explanation

Answer: It accesses host hardware components directly without relying on an underlying host operating system.

Answer

The Type 1 hypervisor accesses host hardware components directly without relying on an underlying host operating system.
Type 1 (bare-metal) hypervisors install directly onto physical server hardware without requiring a host operating system. By managing physical hardware resources natively, Type 1 hypervisors eliminate the scheduling overhead and latency inherent to hosted (Type 2) hypervisors.

Step-by-Step Solution

1
Analyze the architecture of Type 1 (bare-metal) hypervisors.
Type 1 hypervisors run directly on physical hardware without a host OS.
Eliminating the host operating system reduces latency and resource overhead, allowing direct hardware interaction for virtual machines.
2
Compare Type 1 architecture with Type 2 (hosted) hypervisors.
Type 2 hypervisors require a host operating system to manage system calls, hardware devices, and memory allocation.
Host OS mediation introduces processing overhead, making Type 2 hypervisors less suitable for high-performance enterprise workloads.

Key Concept

Type 1 vs Type 2 Hypervisor Architecture
Question 2Question

A network administrator is configuring a router interface for IPv6 stateless address autoconfiguration (SLAAC) using EUI-64. The interface is assigned the IPv6 prefix 2001:db8:cafe:10::/642001:\text{db8}:\text{cafe}:10::/64 and has a MAC address of B4A9.5A12.3456\text{B4A9.5A12.3456}. Which complete IPv6 global unicast address will be generated for this interface?

Show answer & explanation

Answer: 2001:db8:cafe:10:b6a9:5aff:fe12:3456

Answer

2001:db8:cafe:10:b6a9:5aff:fe12:3456
The address ending in 'b6a9:5aff:fe12:3456' is correct because EUI-64 splits the MAC address B4:A9:5A:12:34:56 into two equal parts, inserts the 16-bit hex value FFFE into the middle, and flips the 7th bit of the first byte (changing 0xB4, which is 1011 0100 binary, into 0xB6, which is 1011 0110 binary).

Step-by-Step Solution

1
Split the MAC address into two 24-bit halves and insert FFFE in the middle.
The MAC address B4:A9:5A : 12:34:56 becomes B4A9:5AFF:FE12:3456.
EUI-64 expands a 48-bit MAC address into a 64-bit interface identifier by inserting the 16-bit hex value FFFE between the OUI and the NIC specific serial number.
2
Invert the 7th bit (Universal/Local bit) of the first byte.
First byte 0xB4 in binary is 1011 0100. Inverting the 7th bit gives 1011 0110, which is 0xB6. The interface ID becomes b6a9:5aff:fe12:3456.
RFC 4291 requires flipping the 7th bit of the first byte to indicate universal scope for IEEE MAC-derived interface identifiers.
3
Combine the /64 network prefix with the generated 64-bit interface identifier.
2001:db8:cafe:10:b6a9:5aff:fe12:3456.
The full IPv6 address is constructed by appending the EUI-64 interface ID to the assigned /64 network subnet prefix.

Key Concept

EUI-64 Interface Identifier Generation
Estimated Time:1m 15s
Question 3Question

Match each transport layer characteristic or protocol mechanism on the left to its corresponding protocol operation on the right.

Click a left item, then click its matching right item

Items

Three-way handshake (SYN, SYN-ACK, ACK)
Fixed 8-byte header structure without sequence numbers
Dynamic sliding windowing mechanism
Best-effort transmission without retransmissions

Matches

Show answer & explanation

Answer

The three-way handshake matches stateful connection establishment in TCP; the fixed 8-byte header matches low-overhead encapsulation in UDP; dynamic sliding windowing matches flow control in TCP; and best-effort transmission matches stateless data delivery in UDP.
Each feature correctly pairs with its protocol operation: TCP manages state initializations via the three-way handshake and regulates sender rate using sliding window flow control. Conversely, UDP minimizes encapsulation with an 8-byte header and delivers packets statelessly without retransmissions.

Step-by-Step Solution

1
Identify session initialization characteristics for TCP.
TCP establishes connection state prior to transferring application payload by exchanging SYN, SYN-ACK, and ACK control flags during the three-way handshake.
TCP requires explicit state synchronization between endpoints.
2
Analyze UDP header composition and encapsulation efficiency.
UDP utilizes a lightweight 8-byte header consisting of four 16-bit fields (Source Port, Destination Port, Length, Checksum).
UDP omits connection tracking fields like sequence numbers, acknowledgment numbers, and window size to minimize overhead.
3
Evaluate flow control mechanics in TCP.
TCP uses the Window Size field to implement dynamic sliding windowing, regulating how much data a sender can transmit before receiving an acknowledgment.
Flow control prevents a fast sender from flooding a receiver's incoming socket buffer.
4
Match delivery semantics for latency-sensitive applications.
UDP transmits datagrams using best-effort delivery without waiting for acknowledgments or initiating retransmissions.
Real-time applications (such as VoIP or live video streaming) prioritize low delay over guaranteed error correction.

Key Concept

Comparison of stateful, reliable TCP mechanics versus lightweight, connectionless UDP operations
Question 4Question

Match each IPv6 address scope or functional type on the left with its standardized reserved prefix or address range on the right.

Click a left item, then click its matching right item

Items

Global Unicast
Link-Local
Unique Local
Multicast
Loopback

Matches

Show answer & explanation

Answer

Global Unicast matches 2000::/32000::/3; Link-Local matches fe80::/10\text{fe80}::/10; Unique Local matches fc00::/7\text{fc00}::/7; Multicast matches ff00::/8\text{ff00}::/8; Loopback matches ::1/128::1/128.
Each IPv6 address type is mapped directly to its standard RFC 4291 prefix definition: Global Unicast to 2000::/32000::/3, Link-Local to fe80::/10\text{fe80}::/10, Unique Local to fc00::/7\text{fc00}::/7, Multicast to ff00::/8\text{ff00}::/8, and Loopback to ::1/128::1/128.

Step-by-Step Solution

1
Identify IPv6 unicast address scopes.
Global Unicast is assigned 2000::/32000::/3, Link-Local is assigned fe80::/10\text{fe80}::/10, and Unique Local is assigned fc00::/7\text{fc00}::/7.
RFC 4291 partitions the IPv6 address space into well-defined unicast functional scopes.
2
Identify special and multicast IPv6 prefixes.
Multicast addresses use ff00::/8\text{ff00}::/8, and the single host loopback address is ::1/128::1/128.
Multicast replaces IPv4 broadcasts and uses the ff00::/8\text{ff00}::/8 prefix, while ::1/128::1/128 is reserved exclusively for loopback operations.

Key Concept

IPv6 Reserved Prefixes and Address Scopes
Question 5Question

A network administrator is migrating a medium-sized enterprise campus from a traditional Cisco three-tier architecture (Access, Distribution, Core) to a two-tier collapsed core architecture. Which statement accurately describes the architectural shift in responsibilities resulting from this topology change?

Show answer & explanation

Answer: The core switches combine high-speed backbone switching with distribution-layer functions such as inter-VLAN routing, security policy enforcement, and QoS boundary control.

Answer

The core switches combine high-speed backbone switching with distribution-layer functions such as inter-VLAN routing, security policy enforcement, and QoS boundary control.
In a two-tier collapsed core enterprise design, the traditional distribution and core layers are merged into a single switch tier. Consequently, the collapsed core switches must handle both high-speed packet transport (core function) and policy/routing enforcement such as inter-VLAN routing, ACLs, and QoS boundaries (distribution function).

Step-by-Step Solution

1
Analyze the traditional Cisco Three-Tier hierarchy roles
Access layer provides end-node connectivity; Distribution layer provides routing, ACL policy enforcement, and VLAN aggregation; Core layer provides high-speed backbone transport.
Understanding individual tier responsibilities is necessary to evaluate topology consolidation.
2
Evaluate the effect of collapsing the distribution layer into the core layer
The physical distribution tier is eliminated, and its functional boundaries (inter-VLAN routing, filtering, security policies) are merged into the core devices.
A two-tier collapsed core design saves cost and reduces latency in smaller enterprise environments while combining distribution and core roles into a single switch tier.

Key Concept

Two-Tier Collapsed Core Topology Functions
Estimated Time:1m 30s
Question 6Question

Match each IPv6 addressing scenario or network description on the left with its corresponding prefix length or field bit length on the right.

Click a left item, then click its matching right item

Items

The standard prefix length required for an enterprise end-user LAN subnet to support Stateless Address Autoconfiguration (SLAAC)
The typical prefix length allocated by a Regional Internet Registry (RIR) or ISP to an enterprise customer site
The RFC 6164 recommended prefix length for point-to-point inter-router link interfaces
The standard bit length allocated strictly for the host Interface Identifier (ID) portion of a Global Unicast Address

Matches

Show answer & explanation

Answer

The SLAAC end-user LAN subnet requires a /64 prefix length; the enterprise customer ISP allocation is typically a /48 prefix length; the point-to-point inter-router link uses a /127 prefix length; and the host Interface Identifier occupies 64 bits.
Each scenario maps directly to IPv6 architectural conventions: SLAAC requires a /64 prefix, enterprise sites typically receive a /48 prefix, point-to-point inter-router links use /127 per RFC 6164, and the host Interface ID portion is 64 bits.

Step-by-Step Solution

1
Analyze SLAAC prefix length requirements.
SLAAC requires a /64 prefix length.
SLAAC relies on receiving a /64 prefix advertisement in ICMPv6 Router Advertisement (RA) messages to combine with a 64-bit Interface ID.
2
Determine standard enterprise IPv6 allocation from an ISP.
An enterprise customer site typically receives a /48 prefix.
A /48 global routing prefix leaves bits 49 through 64 (16 bits) available for the enterprise organization to construct up to 65,536 distinct /64 subnets.
3
Evaluate point-to-point link prefix standards.
Point-to-point router links use a /127 prefix length.
Per RFC 6164, using a /127 mask limits available addresses on the link to two, preventing ping-pong routing loops and ND CPU exhaustion attacks.
4
Identify the Interface ID length in a standard IPv6 unicast address.
The Interface ID is exactly 64 bits.
IPv6 address architecture divides a standard 128-bit address into a 64-bit network prefix and a 64-bit host Interface ID.

Key Concept

IPv6 Address Structure and Prefix Allocation Rules
Question 7Question

Match each transport layer protocol operational characteristic or header structure property on the left with its corresponding description on the right.

Click a left item, then click its matching right item

Items

20-byte minimum header size
8-byte fixed header size
Explicit Congestion Notification (ECN)
Stateless datagram transmission

Matches

Show answer & explanation

Answer

20-byte minimum header size matches TCP header structure accommodating sequence numbers, window size, and control flags; 8-byte fixed header size matches UDP header structure containing only source port, destination port, length, and checksum; Explicit Congestion Notification (ECN) matches TCP mechanism for network routers to signal impending network congestion to endpoints; Stateless datagram transmission matches UDP operational mode providing low-latency delivery without session setup or state maintenance.
TCP uses a minimum 20-byte header to support sequence numbers, acknowledgment numbers, control flags, and flow control mechanisms like ECN. UDP uses a minimal 8-byte fixed header containing only ports, length, and checksum to provide lightweight, connectionless datagram delivery.

Step-by-Step Solution

1
Analyze transport layer header length specifications for TCP and UDP.
TCP headers require at least 20 bytes of overhead due to sequence/ACK tracking and windowing fields, whereas UDP headers are strictly fixed at 8 bytes.
Transport layer operational guarantees directly determine header field complexity.
2
Evaluate transport layer signaling and congestion management features.
ECN allows network infrastructure to communicate buffer pressure to TCP endpoints so they can dynamically reduce transmission rates.
TCP maintains stateful mechanisms for connection flow control and congestion avoidance.
3
Compare connection state and delivery requirements.
UDP operates in a stateless datagram model that avoids connection setup latency and session state overhead.
Applications using UDP prioritize rapid, low-overhead transmission over packet delivery verification.

Key Concept

Transport Layer Header Fields and Operational Characteristics (TCP vs. UDP)
Question 8Question

A network administrator is evaluating transport layer requirements for a real-time voice conferencing application and a critical database replication service. Which two operational characteristics accurately describe User Datagram Protocol (UDP) when compared to Transmission Control Protocol (TCP)? (Select two.)

Select all that apply

Show answer & explanation

Answer: UDP operates as a connectionless protocol that transmits data without establishing a initial session handshake.; UDP utilizes a fixed 8-byte header overhead to minimize latency and processing burden.

Answer

UDP is characterized by its connectionless operation without a session handshake and its compact 8-byte fixed header structure.
The statements highlighting UDP as a connectionless protocol without session handshakes and noting its fixed 8-byte header overhead are correct. UDP provides low-latency transmission by dispensing with connection setup and header complexity.

Step-by-Step Solution

1
Analyze transport protocol connection state requirements.
Identify that UDP does not initiate sessions using a three-way handshake (SYN, SYN-ACK, ACK), making it connectionless.
Eliminates delay associated with connection establishment, ideal for time-sensitive applications like voice conferencing.
2
Compare transport layer header fields and overhead.
Confirm that UDP headers consist of only 4 fields totaling 8 bytes, whereas TCP headers require a minimum of 20 bytes.
The smaller header footprint minimizes processing overhead and reduces bandwidth consumption.
3
Evaluate distractor claims against UDP capabilities.
Recognize that sequence/acknowledgment tracking and sliding window flow control belong to stateful TCP operations.
UDP leaves packet ordering and reliability functions to higher-layer application protocols if needed.

Key Concept

Connectionless vs Connection-Oriented Transport Protocols and Header Overhead
Estimated Time:1m 15s
Question 9Question

A network administrator is evaluating campus design options for a multi-floor office building with modest bandwidth requirements. The team decides to implement a 2-Tier Collapsed Core topology instead of a traditional 3-Tier Cisco Campus architecture. Which of the following statements accurately describe the structural and operational traits of this Collapsed Core design? (Select two.)

Select all that apply

Show answer & explanation

Answer: The core and distribution layer functions are merged onto the same physical switch platform or redundant switch pair.; It reduces hardware expenditure and management overhead while providing adequate scalability for smaller to medium-sized networks.

Answer

The correct statements are that the core and distribution layer functions are merged onto the same physical switch platform or redundant switch pair, and that the design reduces hardware expenditure and management overhead while providing adequate scalability for smaller to medium-sized networks.
A 2-Tier Collapsed Core architecture combines the functional responsibilities of the distribution layer (routing boundaries, policy enforcement, VLAN aggregation) and core layer (high-speed transport) into a single logical or physical layer. This approach lowers equipment expenditures, simplifies maintenance, and provides an efficient design for small-to-medium enterprise campuses.

Step-by-Step Solution

1
Analyze the structural definition of a 2-Tier Collapsed Core architecture.
Identify that the core and distribution layers of a traditional 3-Tier model are combined into unified hardware.
This consolidation eliminates one tier of switches to simplify network complexity for smaller deployments.
2
Evaluate the financial and operational benefits of collapsing the core and distribution layers.
Recognize that fewer physical devices result in lower capital costs and simplified management.
Smaller campus environments do not generate enough inter-building aggregate traffic to justify a standalone core layer.
3
Differentiate access layer responsibilities and STP configuration rules.
Confirm that access switches remain necessary and that PortFast must not be applied to switch-to-switch trunks.
PortFast applied to switch interconnects leads to bridging loops, while access switches provide endpoint connectivity and local security enforcement.

Key Concept

Cisco 2-Tier Collapsed Core Campus Architecture
Question 10Question

A network administrator is allocated the IPv6 prefix block 2001:db8:acad:4000::/522001:\text{db8}:\text{acad}:4000::/52 for a corporate branch network. The administrator needs to divide this block into standard /64/64 subnets for local LAN segments. How many /64/64 subnets can be created from this /52/52 prefix block?

Show answer & explanation

Answer: 4,096

Answer

4,096 subnets can be created from a /52 prefix block when using a /64 prefix length.
To calculate the number of /64/64 subnets created from a /52/52 prefix, subtract the assigned prefix length from the target subnet length (6452=1264 - 52 = 12 bits). Raising 2 to the power of the subnet bit count (2122^{12}) gives 4,096 unique /64/64 subnets.

Step-by-Step Solution

1
Determine the number of bits available for subnetting
Subnet bits = 6452=1264 - 52 = 12 bits
The difference between the target prefix length (/64) and the assigned prefix length (/52) defines the subnet ID space.
2
Calculate total subnets using powers of 2
212=4,0962^{12} = 4,096
Each additional binary bit doubles the number of available subnets.

Key Concept

IPv6 Prefix Subnetting
Question 11Question

A network engineer is configuring IP address assignments for client workstations within a corporate VLAN allocated the 10.150.32.0/2110.150.32.0/21 IPv4 block. Which two IP addresses are valid host addresses that can be assigned to devices on this subnet?

Select all that apply

Show answer & explanation

Answer: 10.150.35.25510.150.35.255; 10.150.39.25410.150.39.254

Answer

The valid host addresses are 10.150.35.25510.150.35.255 and 10.150.39.25410.150.39.254.
For the prefix /21/21, the subnet mask is 255.255.248.0255.255.248.0, giving a block size of 88 in the third octet. The subnet 10.150.32.0/2110.150.32.0/21 ranges from network address 10.150.32.010.150.32.0 to broadcast address 10.150.39.25510.150.39.255. The usable host range is 10.150.32.110.150.32.1 through 10.150.39.25410.150.39.254. Both 10.150.35.25510.150.35.255 and 10.150.39.25410.150.39.254 fall within this usable range.

Step-by-Step Solution

1
Determine the subnet mask and block size for a /21 prefix
Prefix /21 corresponds to subnet mask 255.255.248.0. The third octet block size is 256 - 248 = 8.
Calculating block size in the interesting octet establishes subnet boundaries.
2
Calculate the network and broadcast addresses for the 10.150.32.0/21 subnet
Network address is 10.150.32.0. The next subnet starts at 10.150.40.0. Therefore, the broadcast address is 10.150.39.255.
Subnet boundaries define the start and end of the address block.
3
Determine the usable host IP address range
Usable host range spans from 10.150.32.1 to 10.150.39.254 inclusive.
Usable host IPs exclude the network ID (all host bits 0) and broadcast ID (all host bits 1).
4
Evaluate the given options against the usable host range
10.150.35.255 and 10.150.39.254 lie between 10.150.32.1 and 10.150.39.254. Address 10.150.39.255 is the broadcast IP and 10.150.40.0 belongs to the next subnet.
Verifies which IP addresses fall within the valid host envelope.

Key Concept

Usable host address range determination for IPv4 subnets with non-byte-aligned prefixes
Question 12Question

A network engineer is designing a 10 Gigabit Ethernet trunk link between two distribution switches located 250 meters apart in a campus environment. Which of the following transceiver and cabling combinations will successfully establish and support this 10 Gbps connection over the specified distance? (Select two.)

Select all that apply

Show answer & explanation

Answer: 10GBASE-SR SFP+ transceivers connected via OM3 multimode fiber optic cabling; 10GBASE-LR SFP+ transceivers connected via single-mode fiber optic cabling

Answer

The 10 Gigabit Ethernet link over 250 meters can be supported using 10GBASE-SR transceivers with OM3 multimode fiber or 10GBASE-LR transceivers with single-mode fiber.
The combination of 10GBASE-SR with OM3 multimode fiber supports 10 Gbps up to 300 meters, which comfortably reaches the required 250 meters. Similarly, 10GBASE-LR transceivers with single-mode fiber support 10 Gbps up to 10 kilometers, making both options fully compliant with the design constraints.

Step-by-Step Solution

1
Evaluate bandwidth and physical distance parameters.
Required data rate is 10 Gbps; required distance is 250 meters.
Transceiver optics and media standards are defined by maximum supported reach and speed capabilities.
2
Analyze multimode fiber (MMF) specifications for 10 Gbps operation.
10GBASE-SR over OM3 MMF supports distances up to 300 m (and up to 400 m on OM4), whereas legacy OM1 MMF only supports up to 33 m.
OM3 fiber has higher modal bandwidth allowing 10GBASE-SR light signals to travel up to 300 meters without unacceptable modal dispersion.
3
Analyze single-mode fiber (SMF) specifications for 10 Gbps operation.
10GBASE-LR over SMF supports distances up to 10 km (10,000 meters).
Single-mode fiber uses narrow core diameters and lasers, eliminating modal dispersion and easily covering 250 meters.

Key Concept

Physical Interface and Cabling Specifications for Ethernet Transceivers
Estimated Time:1m 30s
Question 13Question

A network administrator is configuring a interface on a switch assigned to the 192.168.4.128/26192.168.4.128/26 IPv4 network segment. Which IPv4 address represents a valid usable host address for this interface?

Show answer & explanation

Answer: 192.168.4.150192.168.4.150

Answer

The address 192.168.4.150192.168.4.150 is a valid usable host address in the 192.168.4.128/26192.168.4.128/26 subnet.
For a /26/26 prefix, 6 bits are available for hosts, providing a total of 26=642^6 = 64 addresses. The 192.168.4.128/26192.168.4.128/26 subnet spans from 192.168.4.128192.168.4.128 (Network ID) through 192.168.4.191192.168.4.191 (Broadcast Address). The usable host range is 192.168.4.129192.168.4.129 to 192.168.4.190192.168.4.190. The address 192.168.4.150192.168.4.150 falls within this valid usable range.

Step-by-Step Solution

1
Determine the total block size from the prefix length.
A /26/26 prefix leaves 3226=632 - 26 = 6 host bits. The block size is 26=642^6 = 64 addresses.
Calculating block size establishes the boundary for subnet ranges.
2
Identify the network and broadcast addresses of the subnet.
The network address is 192.168.4.128192.168.4.128. The broadcast address is 192.168.4.128+641=192.168.4.191192.168.4.128 + 64 - 1 = 192.168.4.191.
Network and broadcast addresses mark the unassignable outer boundaries of the IPv4 block.
3
Calculate the range of usable host addresses.
First usable host = 192.168.4.129192.168.4.129; Last usable host = 192.168.4.190192.168.4.190.
Usable host addresses consist of all IP addresses strictly between the network ID and broadcast address.
4
Evaluate the given choices against the usable host range.
The address 192.168.4.150192.168.4.150 falls within the range [192.168.4.129,192.168.4.190][192.168.4.129, 192.168.4.190].
Only IP addresses in the usable range can be statically assigned to network interfaces.

Key Concept

IPv4 Subnet Boundaries and Usable Host Identification
Estimated Time:1m 0s
Question 14Question

An application developer is configuring a telemetry collection service across a branch network. The service requires low transmission latency and minimal protocol processing overhead for periodic 50-byte metric updates. The developer selects User Datagram Protocol (UDP) instead of Transmission Control Protocol (TCP). Which characteristic of UDP directly accounts for its lower protocol overhead compared to TCP?

Show answer & explanation

Answer: UDP utilizes a fixed 8-byte header structure without connection establishment states or sequence tracking mechanisms.

Answer

UDP utilizes a fixed 8-byte header structure without connection establishment states or sequence tracking mechanisms.
UDP reduces protocol overhead because its header is fixed at 8 bytes (containing only Source Port, Destination Port, Length, and Checksum) and it operates without connection setup (handshake), sequencing, or flow control state tracking.

Step-by-Step Solution

1
Analyze transport protocol header overhead requirements.
TCP headers have a minimum size of 20 bytes, whereas UDP headers are fixed at 8 bytes.
Lower header overhead reduces bandwidth consumption for small payloads.
2
Evaluate transport protocol state tracking mechanisms.
TCP requires a 3-way handshake and tracks sequence/acknowledgment numbers, whereas UDP is connectionless and stateless.
Stateless transmission eliminates latency introduced by connection setup and flow control control loops.

Key Concept

Transport Layer Protocol Overhead and Header Comparison
Estimated Time:1m 30s
Question 15Question

A network administrator is assigning an IPv4 address to an enterprise border router interface connected directly to an Internet Service Provider (ISP) WAN link. The interface must communicate on the public Internet without employing Network Address Translation (NAT). Which of the following IPv4 addresses is globally routable over the Internet according to RFC 1918 specifications?

Show answer & explanation

Answer: 172.32.50.1

Answer

172.32.50.1 is a globally routable public address because it lies outside the RFC 1918 private address boundaries.
RFC 1918 defines three private IPv4 address ranges that are not routed on the public Internet: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. The Class B range covers 172.16.0.0 through 172.31.255.255. The IP address 172.32.50.1 falls outside this range, making it a valid public IPv4 address suitable for Internet communication without NAT.

Step-by-Step Solution

1
Recall the RFC 1918 private IPv4 address allocations.
Class A: 10.0.0.0/8 (10.0.0.0 to 10.255.255.255); Class B: 172.16.0.0/12 (172.16.0.0 to 172.31.255.255); Class C: 192.168.0.0/16 (192.168.0.0 to 192.168.255.255).
Identify which IP ranges are reserved for internal/private use and unroutable on the public Internet.
2
Evaluate each candidate IPv4 address against the RFC 1918 boundaries.
10.254.10.1 is in 10.0.0.0/8 (private). 192.168.250.1 is in 192.168.0.0/16 (private). 172.31.200.1 is in 172.16.0.0/12 (private). 172.32.50.1 is outside 172.16.0.0/12 (public).
The Class B private block ends at 172.31.255.255. Addresses starting at 172.32.0.0 are public IP addresses.
3
Select the address suitable for WAN interface routing without NAT.
172.32.50.1 is public and globally routable.
ISPs drop RFC 1918 private addresses at edge boundaries, so only public IP addresses can communicate over the global Internet without NAT.

Key Concept

RFC 1918 Private Address Ranges and Public Routability
Question 16Question

A network administrator is installing an outdoor wireless point-to-point bridge between two campus buildings. The access point transmitter power is configured to 14 dBm14\text{ dBm}, the coaxial cable connecting the access point to the antenna introduces 3 dB3\text{ dB} of attenuation, and the directional antenna has a gain of 16 dBi16\text{ dBi}. What is the Effective Isotropic Radiated Power (EIRP) for this wireless installation?

Show answer & explanation

Answer: 27 dBm27\text{ dBm}

Answer

The Effective Isotropic Radiated Power (EIRP) is 27 dBm27\text{ dBm}.
The correct calculation for Effective Isotropic Radiated Power (EIRP) accounts for the total power output from the transmitter, minus any insertion losses along the transmission cable, plus the passive power gain provided by the antenna. Computing 14 dBm3 dB+16 dBi14\text{ dBm} - 3\text{ dB} + 16\text{ dBi} gives 27 dBm27\text{ dBm}.

Step-by-Step Solution

1
Identify the given radio frequency values
Transmitter Power (PtxP_{\text{tx}}) = 14 dBm14\text{ dBm}, Cable Loss (LcableL_{\text{cable}}) = 3 dB3\text{ dB}, Antenna Gain (GantennaG_{\text{antenna}}) = 16 dBi16\text{ dBi}.
These parameters determine the total power radiated by the antenna in isotropic terms.
2
Apply the standard EIRP formula
EIRP=PtxLcable+Gantenna\text{EIRP} = P_{\text{tx}} - L_{\text{cable}} + G_{\text{antenna}}
Cable attenuation reduces signal power before it reaches the antenna, while antenna gain focuses and boosts the radiated signal power.
3
Substitute the values into the formula and calculate
EIRP=14 dBm3 dB+16 dBi=27 dBm\text{EIRP} = 14\text{ dBm} - 3\text{ dB} + 16\text{ dBi} = 27\text{ dBm}
Combining the transmitter output, cable attenuation, and passive antenna gain yields the total effective radiated power.

Key Concept

Effective Isotropic Radiated Power (EIRP) Calculation
Question 17Question

A network technician is evaluating transport layer requirements for real-time application traffic. Which two features are characteristic of the User Datagram Protocol (UDP) rather than the Transmission Control Protocol (TCP)? (Select two.)

Select all that apply

Show answer & explanation

Answer: Low fixed header size of 8 bytes; Connectionless datagram delivery without handshake overhead

Answer

The characteristics unique to UDP are its low fixed header size of 8 bytes and its connectionless datagram delivery without handshake overhead.
The correct features of UDP are its minimal 8-byte header length and connectionless nature, which avoids connection setup delays.

Step-by-Step Solution

1
Identify transport layer protocol overhead differences
UDP relies on a simple 8-byte header (Source Port, Destination Port, Length, Checksum), whereas TCP requires a minimum 20-byte header.
Understanding header structure helps evaluate bandwidth and processing efficiency.
2
Evaluate connection state properties
UDP operates connectionlessly without requiring a initial three-way handshake.
Connectionless delivery minimizes latency for real-time applications.

Key Concept

UDP is a lightweight, connectionless transport layer protocol with minimal header overhead (8 bytes) and no built-in flow control or reliability mechanisms.
Question 18Question

Host A sends an Ethernet frame addressed to Host B into port FastEthernet0/1 of a Layer 2 switch. The switch MAC address table already contains an entry for Host B on port FastEthernet0/2, but has no prior entry for Host A. What action does the switch take upon receiving this frame?

Show answer & explanation

Answer: Learns Host A's MAC address on port FastEthernet0/1 and forwards the frame directly out port FastEthernet0/2.

Answer

The switch records Host A's MAC address on FastEthernet0/1 and forwards the frame exclusively out FastEthernet0/2.
When a switch receives a frame, it always inspects the source MAC address to update its MAC table (learning Host A on FastEthernet0/1). It then checks the destination MAC address; since Host B is already recorded on FastEthernet0/2, the switch forwards the frame exclusively out that destination port.

Step-by-Step Solution

1
Examine the ingress frame's source MAC address
Host A's MAC address is learned and added to the MAC address table associated with port FastEthernet0/1.
Layer 2 switches dynamically populate their MAC address tables by inspecting incoming frame source MAC addresses and ingress port numbers.
2
Examine the ingress frame's destination MAC address
Host B's MAC address is found in the table associated with port FastEthernet0/2.
If the destination MAC address is already present in the MAC address table, the switch performs point-to-point known unicast forwarding.
3
Forward the frame
The frame is transmitted solely out port FastEthernet0/2.
Known unicast destination entries prevent unnecessary frame flooding across other switch ports.

Key Concept

Layer 2 MAC Address Table Learning and Forwarding Logic
Question 19Question

An administrator is configuring IPv6 addressing on a router interface and verifying reserved scope prefixes. Which two statements correctly describe IPv6 address representations and reserved prefix ranges? (Select two.)

Select all that apply

Show answer & explanation

Answer: The prefix fe80::/10 is reserved for IPv6 link-local addresses.; The IPv6 loopback address is represented as ::1/128.

Answer

The prefix fe80::/10 is reserved for IPv6 link-local addresses, and the IPv6 loopback address is represented as ::1/128.
Link-local addresses strictly use the fe80::/10 prefix, and the loopback address for an IPv6 host interface is ::1/128.

Step-by-Step Solution

1
Identify the reserved prefix ranges for link-local and unique local IPv6 address scopes.
The prefix fe80::/10 corresponds to link-local unicast addresses. The prefix fc00::/7 corresponds to Unique Local Addresses (ULA), not global unicast addresses (which use 2000::/3).
Understanding IPv6 scope prefixes is required to properly categorize address types.
2
Evaluate the rules of IPv6 address compression and special addresses.
The double colon (::) compression mechanism is allowed only once per address to maintain uncompressed length integrity. The IPv6 loopback address is designated as ::1/128.
RFC 4291 specifies rules for shortening IPv6 addresses and designates ::1/128 for node loopback testing.

Key Concept

IPv6 Address Scopes and Zero Compression Rules
Question 20Question

Match each IPv6 address or prefix on the left with its corresponding functional characteristic or property on the right.

Click a left item, then click its matching right item

Items

2001:db8:abc:1200::/562001:\text{db8}:\text{abc}:1200::/56
fd00:db8:abc:1200::/64fd00:\text{db8}:\text{abc}:1200::/64
fe80::200:5eff:fe00:5301
ff02::1:ff00:5301

Matches

Show answer & explanation

Answer

The correct pairings are: 2001:db8:abc:1200::/56 matches the global unicast prefix providing 256 subnets of /64 length; fd00:db8:abc:1200::/64 matches the unique local address prefix; fe80::200:5eff:fe00:5301 matches the link-local address created using EUI-64 from MAC 00:00:5e:00:53:01; and ff02::1:ff00:5301 matches the solicited-node multicast address.
Each IPv6 address and prefix matches its exact functional specification: 2001:db8:abc:1200::/56 yields 256 subnets of /64 size; fd00::/8 addresses are Unique Local Addresses; fe80::200:5eff:fe00:5301 correctly applies the 7th-bit flip and FFFE insertion to MAC 00:00:5e:00:53:01; and ff02::1:ff00:5301 uses the exact low 24 bits of the interface ID appended to the solicited-node multicast prefix.

Step-by-Step Solution

1
Analyze the prefix length calculation for 2001:db8:abc:1200::/56
Difference between /64 and /56 is 8 bits (6456=864 - 56 = 8). 28=2562^8 = 256 subnets.
Standard IPv6 subnets are designated at the /64 boundary.
2
Identify the IPv6 scope for fd00:db8:abc:1200::/64
Prefix starting with fd00::/8 is within fc00::/7.
fc00::/7 defines Unique Local Addresses (ULA), equivalent to IPv4 private addresses.
3
Perform Modified EUI-64 conversion on MAC 00:00:5e:00:53:01
First byte 0x00 binary (00000000) flipped 7th bit becomes 0x02 (00000010). Insert FFFE in center (0000:5E -> 0000:5EFF:FE00:5301). Prepend fe80:: prefix -> fe80::200:5eff:fe00:5301.
Modified EUI-64 flips the 7th bit (Universal/Local) and inserts FFFE between OUI and NIC specific bytes.
4
Derive the solicited-node multicast address for interface ID 0200:5eff:fe00:5301
Extract last 24 bits (00:5301) and append to prefix ff02::1:ff00:0/104 -> ff02::1:ff00:5301.
Solicited-node multicast addresses always start with ff02::1:ff00:0/104 and take the lowest 24 bits of the unicast address.

Key Concept

IPv6 Address Representation, Subnetting, Scopes, and EUI-64 / Solicited-Node Multicast Generation
Page 1 / 20Next