CCNA Networking Concepts Questions

UDP is a connectionless protocol that does not provide guaranteed delivery; it offers no acknowledgments or retransmissions, unlike TCP which ensures reliable data transfer.

UDP is a connectionless protocol that does not use sequence numbers; sequence numbers are a feature of TCP for ordered delivery.

UDP is a connectionless protocol that does not establish a session, so it does not support a three-way handshake, which is a TCP mechanism.

The hub creates a single collision domain for its 4 ports, not 4 separate ones. The switch has 8 collision domains (one per port), but the hub's segment adds only 1, totaling 9, not 11. The correct count is 8 collision domains (7 switch ports + 1 hub segment) and 1 broadcast domain.

In a Layer 2 broadcast domain, devices communicate using MAC addresses, but this is not a defining characteristic of the domain itself; it's true for any Ethernet network. The question asks for a characteristic of the broadcast domain, which is that broadcast frames are forwarded to all ports.

A Layer 2 broadcast domain is defined by the reach of broadcast frames, not by IP subnetting. Devices on the same broadcast domain can be on different IP subnets; IP subnetting is a Layer 3 concept.

Routers operate at Layer 3 and are not required for communication within the same Layer 2 broadcast domain; switches or bridges handle Layer 2 forwarding.

Switches operate at Layer 2 (data link layer), not Layer 3. While some switches can perform Layer 3 routing, the primary difference between a hub and a switch is not speed based on OSI layer; hubs operate at Layer 1 and switches at Layer 2.

A hub does not segment collision domains; it actually extends them. A switch segments collision domains by creating a separate collision domain per port.

Both hubs and switches operate at Layer 2 (Data Link layer) and use the same Ethernet frame types; the statement is factually incorrect.

When comparing routes from different routing protocols, the router uses administrative distance (AD) first, not metric. OSPF has AD 110, EIGRP has AD 90, so EIGRP is preferred regardless of metric values.

Routers install only the route with the lowest administrative distance (AD) when multiple routes to the same destination exist from different routing protocols. Here, EIGRP has AD 90 vs OSPF's 110, so only the EIGRP route is installed; load balancing requires equal AD and equal metric.

OSPF being a link-state protocol does not automatically make its route preferred; route selection is based on administrative distance, not protocol type. Here, EIGRP has a lower AD (90 vs 110), so it wins regardless of OSPF's link-state nature.

The prefix 2001:db8::/32 includes addresses where the first 32 bits are 2001:0db8. Option B, 2001:db9::1, has the third quartet as 0db9, which differs in the 33rd bit, so it is not within the /32 prefix.

The prefix 2001:db8::/32 includes addresses where the first 32 bits are 2001:0db8. Option C (2001:db7::1) has the third hextet as db7, which differs from db8 in the 33rd bit, so it does not match the /32 prefix.

The prefix 2001:db8::/32 specifies that the first 32 bits must be 2001:0db8. Option D (fe80::1) starts with fe80, which is a link-local address prefix, not matching the required prefix.

DNS resolves domain names to IP addresses, not MAC addresses. The question asks for the protocol that maps IP addresses (Layer 3) to MAC addresses (Layer 2), which is ARP.

DHCP is used for dynamically assigning IP addresses and other network configuration parameters to hosts, not for resolving Layer 2 MAC addresses from Layer 3 IP addresses.

ICMP is used for error reporting and diagnostics (e.g., ping), not for resolving Layer 2 addresses from Layer 3 addresses.

The Physical layer (Layer 1) handles raw bit transmission over a physical medium and does not perform any sequencing or reassembly of data segments.

The Data Link layer handles node-to-node delivery and framing, not end-to-end segment sequencing. Sequencing of segments is a Transport layer function (e.g., TCP sequence numbers).

The Network layer (Layer 3) handles routing and logical addressing, but not segmentation or sequencing of data segments. Sequencing is a function of the Transport layer (Layer 4), which manages end-to-end communication and reassembly.

AS_PATH is used for loop prevention and path selection, but it primarily influences outbound traffic by affecting how routes are advertised, not inbound traffic to a particular AS.

The Next Hop attribute specifies the IP address of the next router to reach a destination, but it does not influence inbound traffic decisions; it is used for routing path selection, not traffic engineering into an AS.

Local Preference is used to influence outbound traffic from an AS, not inbound traffic. It is a well-known discretionary attribute that is exchanged within an AS to affect the exit path for routes learned from EBGP peers.

The subnet mask 255.255.255.240 (/28) provides 16 total addresses per subnet, but the network address and broadcast address are reserved, leaving only 14 usable host addresses.

A /28 subnet (255.255.255.240) provides 16 total addresses, but the network and broadcast addresses are reserved, leaving 14 usable hosts. Option C (30) corresponds to a /27 subnet (255.255.255.224), not /28.

A /28 subnet (255.255.255.240) provides 16 total addresses, but 2 are reserved for network and broadcast, leaving 14 usable. Option D (62) corresponds to a /26 subnet (255.255.255.192), which is not the mask in this question.

Switches operate at Layer 2 and forward frames based on MAC addresses, not IP addresses. IP address-based forwarding is the function of a router (Layer 3).

A switch operates at Layer 2 and forwards frames based on MAC addresses, not IP addresses. Connecting different networks and performing routing is the function of a router, not a switch.

A switch does not amplify and repeat signals to all ports; that describes a hub. Switches forward frames only to the specific port based on MAC addresses.

A star topology uses a central switch or hub; if that central device fails, the entire network goes down, so it does not provide the highest level of redundancy and fault tolerance compared to a mesh topology.

A bus topology uses a single backbone cable; if the cable fails, the entire network goes down, offering no redundancy or fault tolerance.

In a ring topology, each device is connected to exactly two neighbors, forming a single path for data. A break in the ring or a device failure disrupts the entire network, offering minimal fault tolerance compared to mesh.

Frames and MAC addresses are data link layer (Layer 2) concepts; Layer 1 handles raw bit transmission without framing or addressing.

Layer 3 (Network) handles logical addressing (e.g., IP addresses) and routing, not frame encapsulation or MAC addresses. Frames and MAC addresses are specific to Layer 2 (Data Link).

Layer 4 (Transport) handles end-to-end communication, segmentation, and reassembly, not frame encapsulation or MAC addressing. Frames and MAC addresses are specific to Layer 2 (Data Link).

DNS resolves domain names to IP addresses, but does not automate IP address assignment for client devices.

ARP (Address Resolution Protocol) is used to map IP addresses to MAC addresses on a local network, not to automate IP address assignment for client devices.

ICMP is used for network diagnostics and error reporting (e.g., ping, traceroute), not for automating IP address assignment. DHCP is the correct protocol for dynamic IP allocation.

Hubs operate at Layer 1 (physical layer) and do not process MAC addresses, while switches operate at Layer 2 (data link layer) and use MAC addresses for forwarding. This option reverses the OSI layers for hubs and switches.

Hubs operate at Layer 1 and do not use MAC addresses; switches use MAC addresses at Layer 2. This option reverses the roles: hubs do not use MAC addresses, and switches do not use IP addresses for forwarding.

A hub creates a single collision domain for all ports, while a switch creates a separate collision domain per port. The statement reverses these facts.

A /52 prefix provides 16 subnets (2^(52-48)=16), which is insufficient for the requirement of up to 250 subnets.

A /64 subnet provides 2^64 addresses per subnet, which is far more than needed for 250 subnets. Using /64 would waste a huge number of addresses and does not minimize waste given the /48 prefix.

A /60 subnet provides only 2^(60-48)=4096 subnets, which is far more than the required 250, but it wastes more addresses than a /56 (which gives 256 subnets). The question asks to minimize waste, so /56 is optimal.

TCP is a connection-oriented protocol at the transport layer, meaning it establishes a reliable connection before data transfer, which is the opposite of connectionless.

ICMP operates at the network layer (Layer 3), not the transport layer. The question specifically asks for a connectionless protocol at the transport layer, which is UDP.

ARP operates at the Data Link layer (Layer 2) and resolves IP addresses to MAC addresses; it is not a transport layer protocol and does not provide connectionless transport services.

Logical addressing (IP addresses) and routing are functions of the Network layer (Layer 3), not the Data Link layer (Layer 2), which handles physical addressing (MAC addresses) and frame forwarding within a local network.

The Transport layer (Layer 4) is responsible for end-to-end communication, segmentation, and flow control, not logical addressing or routing. IP addresses and routing are functions of the Network layer (Layer 3).

The Physical layer (Layer 1) is responsible for the transmission and reception of raw bit streams over a physical medium, not for logical addressing or routing.

The client can ping external IP addresses successfully, which indicates that the subnet mask is correct; otherwise, routing to external IPs would fail.

The client can ping the default gateway and external IP addresses, which indicates the default gateway is correctly configured. The issue is name resolution, not routing.

The client can ping external IP addresses successfully, indicating that traffic to external networks is not blocked. A firewall blocking DNS would prevent DNS queries but not ICMP pings to external IPs; however, the ability to ping external IPs suggests no general firewall blocking of outbound traffic. The issue is specifically name resolution, not packet filtering.

The Transport layer handles end-to-end communication, segmentation, and flow control, but not session establishment, management, termination, checkpoints, or recovery.

The Network layer (Layer 3) is responsible for routing and forwarding packets across networks, not for session management, checkpoints, or recovery.

The data link layer (Layer 2) handles node-to-node data transfer, error detection, and framing, not session management, checkpoints, or recovery.

The Data Link layer (Layer 2) handles node-to-node data transfer, error detection, and MAC addressing, not logical addressing or routing between networks, which are functions of the Network layer (Layer 3).

The Transport layer (Layer 4) is responsible for end-to-end communication, segmentation, and flow control, not for logical addressing or routing between networks.

The Application layer (Layer 7) provides network services to end-user applications, such as HTTP, FTP, and SMTP. It does not handle logical addressing or routing, which are functions of the Network layer.

TCP provides reliable, connection-oriented delivery with retransmission of lost packets, which increases latency and is unsuitable for real-time applications like VoIP and streaming video that prioritize low latency over reliability.

ICMP is a network layer protocol used for error reporting and diagnostics (e.g., ping), not for transporting VoIP or streaming video data. It does not provide the low-latency, connectionless transport required for real-time media.

IGMP (Internet Group Management Protocol) is used for managing multicast group memberships, not for transporting VoIP or streaming video data. It operates at the network layer, not the transport layer, and does not handle low-latency data delivery or retransmission.

The Network layer (Layer 3) handles routing and logical addressing, but flow control, error detection, and recovery for end-to-end communication are functions of the Transport layer (Layer 4).

The Data Link layer provides flow control, error detection, and recovery only for direct node-to-node links, not for end-to-end communication across multiple network segments.

The Session layer (Layer 5) manages sessions, dialog control, and synchronization, but does not provide flow control, error detection, or recovery for end-to-end communication; those functions belong to the Transport layer.

Hubs operate at Layer 1 (Physical layer) and simply repeat electrical signals to all ports; they do not use MAC addresses to forward frames.

Routers operate at Layer 3 (Network layer) and use IP addresses to forward packets, not MAC addresses to forward frames.

A firewall operates at Layers 3 and 4 (and sometimes higher) of the OSI model, using IP addresses and ports to filter traffic, not MAC addresses to forward frames.

The TCP three-way handshake is used to establish a connection, not to terminate one. Termination uses a four-way handshake with FIN flags.

The TCP three-way handshake is used to establish a connection, not to resolve IP addresses to MAC addresses; that is the function of ARP (Address Resolution Protocol).

The TCP three-way handshake is used to establish a connection, not to encrypt data. Encryption is handled by protocols like TLS or IPsec, not by TCP itself.

Option A is not a valid answer choice in this question; the actual options are not provided, but assuming 'A' refers to a common distractor like 'MTU mismatch', that would be incorrect because both switches are configured for jumbo frames with MTU 9000, so MTU mismatch is not the issue.

Option B is not specified, but assuming it refers to a common incorrect cause like 'CRC errors' or 'fiber attenuation', these would not selectively affect large transfers while allowing small ones; jumbo frame issues typically stem from MTU mismatch or switch configuration.

Option D is not provided in the question, so it cannot be analyzed. The correct answer is C, which likely refers to a mismatch in MTU settings or jumbo frame configuration across the path, causing large frames to be dropped.

Anycast is used for one-to-nearest communication, where multiple hosts share the same address but only the closest one responds, not for one-to-many communication like multicast.

Unicast is used for one-to-one communication, not one-to-many. The question specifically asks for an address type similar to IPv4 multicast, which is one-to-many.

IPv6 does not have a broadcast address; broadcast functionality is replaced by multicast. The question asks for an IPv6 address type similar to IPv4 multicast, which is multicast in IPv6.

A switch operates at Layer 2 (Data Link) and uses MAC addresses to forward frames, not at Layer 1. It does not simply regenerate electrical signals; it makes forwarding decisions based on addressing.

Routers operate at Layer 3 (Network) and make forwarding decisions based on IP addresses, not by regenerating electrical signals at the physical layer.

A bridge operates at Layer 2 (Data Link) and uses MAC addresses to forward frames, not Layer 1 signal regeneration. It does not simply regenerate electrical signals to extend distance.

A collision domain is defined by the possibility of frame collisions when multiple devices transmit simultaneously, not by IP subnet membership. Devices on different IP subnets can still be in the same collision domain if connected via a hub or repeater.

A collision domain is defined by the possibility of data collisions when multiple devices transmit simultaneously; broadcast confinement describes a broadcast domain, not a collision domain.

In a collision domain, the key issue is data collisions from simultaneous transmissions, not MAC-to-IP resolution. MAC-to-IP resolution is performed by ARP, which is unrelated to collision domains.

An IP address identifies a device on a network layer, not the hardware interface itself, and can change dynamically or be reassigned.

A subnet mask defines the network and host portions of an IP address, but it does not uniquely identify a hardware network interface; it is a logical parameter used for routing.

A default gateway is a router's IP address used for traffic outside the local subnet, not a unique identifier for a hardware network interface.

In a mesh topology, each device connects to multiple other devices, not to a single central device. The question specifically asks for a topology where all devices connect to a central device, which is the star topology.

In a bus topology, all devices are connected to a single central cable (the bus), not to a central device like a switch or hub. The question specifies a central device, which is characteristic of a star topology.

In a ring topology, each device is connected to exactly two other devices, forming a circular data path, not to a central device.

The router is directly connected to both subnets (10.0.1.0/24 and 10.0.2.0/24), so it automatically has routes to these networks. A routing protocol is only needed to learn routes to non-directly connected networks, which is not the case here.

The hosts can ping the router's interface in their subnet, indicating the default gateway is correctly configured. The issue is inter-subnet routing, not the gateway address.

The switch in subnet A is a Layer 2 device and does not block ICMP traffic between subnets; inter-subnet communication requires a router, and the issue is that the router is not forwarding packets because IP routing is disabled.

Each VLAN creates a separate broadcast domain. With three VLANs (10, 20, 30) and a router with three subinterfaces, there are three distinct broadcast domains, not one.

Each VLAN creates its own broadcast domain, and with three VLANs (10, 20, 30) there are exactly three broadcast domains. Option C (4) is incorrect because there is no fourth broadcast domain; the router subinterfaces do not add additional broadcast domains beyond the VLANs.

DNS resolves domain names to IP addresses, but does not assign IP addresses or provide subnet masks and default gateways.

ARP (Address Resolution Protocol) is used to resolve IP addresses to MAC addresses on a local network, not to assign IP addresses or provide subnet masks and default gateways.

ICMP is used for network diagnostics and error reporting (e.g., ping, traceroute), not for automatic IP address assignment or providing subnet mask and default gateway.

A switch forwards frames based on MAC addresses, not IP addresses, and operates within a single network segment, not between different network segments.

A hub operates at Layer 1 (physical) and simply repeats electrical signals to all ports, making no forwarding decisions based on IP addresses.

A bridge connects two network segments but makes forwarding decisions based on MAC addresses, not IP addresses, and operates at Layer 2 of the OSI model.

Each VLAN is a separate Layer 3 broadcast domain. With VLANs 10, 20, 30, and 99, there are four broadcast domains, not one.

Each VLAN is a separate Layer 3 broadcast domain. VLANs 10, 20, and 30 each have a router subinterface, and VLAN 99 is a native VLAN without a subinterface, but it still constitutes its own broadcast domain because it is a distinct VLAN. Thus, there are 4 broadcast domains, not 2.

The session layer manages sessions (establish, maintain, terminate) but does not handle end-to-end communication or data segmentation; those are transport layer functions.

The Network layer (Layer 3) handles routing and logical addressing, not end-to-end communication and data segmentation, which are functions of the Transport layer.

The data link layer handles node-to-node communication and framing, not end-to-end communication or data segmentation, which are functions of the transport layer.

A switch examines the destination MAC address to forward frames only to the appropriate port, not to all ports, unlike the device described.

Bridges examine destination MAC addresses to decide whether to forward or filter frames, and they do not flood frames out all ports unless the address is unknown. This question describes a device that forwards all frames out all ports without examining MAC addresses, which is a hub, not a bridge.

Routers operate at Layer 3 and examine destination IP addresses to make forwarding decisions, not MAC addresses. They do not forward frames out all ports without inspection.

A hub operates at Layer 1 and does not segment collision domains; all ports share a single collision domain, so it does not increase the number of collision domains.

A router increases both collision domains and broadcast domains because it separates broadcast domains by default, which is not what the question asks.

A repeater operates at Layer 1 and simply regenerates signals, extending the physical reach of a network. It does not segment collision domains; all devices connected via repeaters share the same collision domain, and it does not affect broadcast domains.

IP operates at the Network layer (Layer 3), not the Transport layer. It handles routing and addressing, not end-to-end communication and data segmentation.

Ethernet operates at the Data Link layer (Layer 2) and the Physical layer (Layer 1), not the Transport layer (Layer 4). It handles local network framing and media access, not end-to-end communication or segmentation.

HTTP operates at the Application layer (Layer 7) of the OSI model, not the Transport layer. The Transport layer is responsible for end-to-end communication and segmentation, which is handled by protocols like TCP and UDP.

HTTP operates at the Application layer (Layer 7), but the TCP segment header is added at the Transport layer (Layer 4) during encapsulation. The question specifically asks where the HTTP data gets encapsulated with a TCP segment header, which occurs at the Transport layer, not the Application layer.

The Presentation layer (Layer 6) handles data translation, encryption, and compression, not encapsulation with TCP segment headers. TCP segment headers are added at the Transport layer (Layer 4).

The Session layer (Layer 5) manages sessions, not encapsulation of data into segments; TCP segment headers are added at the Transport layer (Layer 4).

A default gateway forwards traffic to other networks, not translates domain names to IP addresses; that is the function of DNS.

A default gateway forwards traffic to other networks, not assign IP addresses. IP address assignment is typically done by a DHCP server, not a default gateway.

A default gateway forwards traffic to other networks, not filters it. Traffic filtering to prevent unauthorized access is the function of a firewall, not a default gateway.

In a TCP three-way handshake, after the server sends SYN-ACK, the client must send an ACK to complete the connection. RST is used to reset a connection, not to continue the handshake.

The TCP three-way handshake requires an ACK from the client after receiving SYN-ACK; FIN is used to terminate a connection, not to establish it.

In the TCP three-way handshake, after the server sends SYN-ACK, the client must send an ACK to complete the connection. Sending a SYN again would be redundant and violate the handshake sequence.

Unicast transmission is defined as one-to-one communication, not one-to-many. One-to-many communication is multicast, where data is sent from one source to a specific group of recipients.

Unicast transmission is defined as one-to-one communication, not one-to-all. One-to-all communication is broadcast, where a single sender transmits to all devices on the network.

Unicast transmission is defined as one-to-one communication, not many-to-many. Many-to-many communication describes multicast or anycast in some contexts, but not unicast.

A /26 subnet provides 2^(32-26) = 64 total addresses, with 2 reserved for network and broadcast, leaving 62 usable. Option A (30) corresponds to a /27 subnet, not /26.

A /26 subnet mask provides 64 total addresses, with 62 usable host addresses (2^6 - 2 = 62). Option C (126) corresponds to a /25 subnet mask, which is not used in this question.

A /26 subnet mask provides 64 total addresses, with 62 usable host addresses (64 - 2 for network and broadcast). Option D (254) corresponds to a /24 subnet mask, not /26.

Global unicast addresses require either manual configuration or DHCPv6 (stateful or stateless) to be assigned; they are not automatically generated upon interface initialization without a configuration server.

Unique local addresses (ULAs) are not automatically assigned upon interface initialization; they require manual configuration or DHCPv6. IPv6 nodes automatically generate a link-local address (fe80::/10) without any server.

A multicast address is not automatically assigned to an interface upon initialization; it is typically joined for specific protocols (e.g., all-nodes multicast FF02::1) but not generated as a unicast address for the interface itself.

The 172.16.0.1 address is part of the Class B private range (172.16.0.0/12), not Class A. The question specifically asks for a Class A private address, which is 10.0.0.0/8.

The question asks for a Class A private address per RFC 1918. 192.168.1.1 is a Class C private address (192.168.0.0/16), not Class A.

172.32.0.1 is not within the RFC 1918 private address ranges; the Class B private range is 172.16.0.0/12 (172.16.0.0 to 172.31.255.255), and 172.32.0.1 falls outside that range.

Subnetting segments a network into multiple IP subnets, but it requires a router to forward traffic between subnets, and it does not create separate broadcast domains without additional hardware (the router). VLANs achieve broadcast domain segmentation at Layer 2 without extra hardware.

VPNs create encrypted tunnels over public networks for secure remote access, but they do not segment a LAN into multiple broadcast domains; they operate at Layer 3 and above, not at Layer 2 where broadcast domains are defined.

NAT (Network Address Translation) translates private IP addresses to public ones for internet access, but it does not segment a LAN into multiple broadcast domains. Broadcast domains are separated by Layer 2 or Layer 3 boundaries, not by address translation.

The conversion of data frames into electrical signals occurs at Layer 1 (Physical), not Layer 2. Layer 2 (Data Link) handles framing, MAC addressing, and error detection, but does not perform signal conversion.

Layer 3 (Network) handles logical addressing and routing, not the conversion of data frames into electrical signals. That conversion occurs at Layer 1 (Physical).

Layer 4 (Transport) handles end-to-end communication, segmentation, and reassembly, not the conversion of data frames into electrical signals. That conversion occurs at Layer 1 (Physical).

Layer 2 switches operate at the data link layer and use MAC addresses, not IP addresses, for forwarding decisions. IP addresses are used by Layer 3 devices like routers.

A Layer 2 switch operates at the data link layer and cannot route traffic between VLANs; inter-VLAN routing requires a Layer 3 device such as a router or a multilayer switch.

Network Address Translation (NAT) is a function typically performed by routers or firewalls, not by Layer 2 switches. Layer 2 switches operate at the data link layer and do not modify IP addresses.

The device forwards based on MAC addresses and floods unknown unicasts, which are Layer 2 functions. Layer 1 devices (e.g., repeaters, hubs) do not examine MAC addresses and simply regenerate signals.

Layer 3 devices (routers) forward based on destination IP address, not MAC address, and they modify the frame by decrementing TTL and recalculating checksums. This device forwards by MAC address and does not modify frames, which is Layer 2 switching.

Layer 4 (Transport) handles end-to-end communication, segmentation, and flow control using ports, not MAC address forwarding. The device described operates at Layer 2 (Data Link) because it forwards based on MAC addresses and floods unknown unicasts.

MAC addresses operate at Layer 2 (Data Link) and are used for local network delivery, not for routing across different networks. IPv4 uses IP addresses as logical addresses to identify hosts on different networks.

Port numbers identify specific processes or services on a host (transport layer), not the destination network or host itself. The question asks for the logical address used to reach a different network, which is the IP address (network layer).

The default gateway is a router's IP address used to forward traffic to other networks, but it is not the logical address of the destination host. The question asks for the logical address that identifies the destination host on a different network, which is the IP address.

Layer 2 (Data Link layer) uses MAC addresses for local network delivery, not IP addresses. Encapsulation with source and destination IP addresses occurs at Layer 3 (Network layer).

Layer 4 (Transport) uses port numbers and manages end-to-end communication, not IP addressing. IP addresses are added at Layer 3 (Network).

Layer 1 (Physical) deals with raw bit transmission over physical media, not with IP addresses. Encapsulation with IP addresses occurs at Layer 3 (Network).

2001:db8::1 is a global unicast address (used for documentation), not a link-local address. Link-local addresses always start with fe80::/10.

ff02::1 is a multicast address (all-nodes link-local multicast), not a unicast link-local address. Link-local unicast addresses start with fe80::/10.

2000::/3 is the prefix for global unicast addresses, not link-local addresses. Link-local addresses are in the fe80::/10 range.

A Layer 2 switch forwards frames based on MAC addresses and cannot perform routing between VLANs because it lacks Layer 3 IP routing capabilities.

A bridge operates at Layer 2 and cannot perform routing between VLANs; it only forwards frames based on MAC addresses within the same broadcast domain.

A hub operates at Layer 1 and cannot perform VLAN segmentation or routing; it simply repeats electrical signals to all ports, so it cannot route traffic between VLANs.

UDP does not use sequence numbers for ordering; that is a feature of TCP, which uses sequence numbers to ensure ordered delivery of data segments.

UDP does not provide reliable data delivery; it is connectionless and offers no guarantees regarding packet delivery, ordering, or error recovery, unlike TCP which ensures reliability through acknowledgments and retransmissions.

UDP does not require a three-way handshake; it is connectionless and sends data without establishing a connection. The three-way handshake is a TCP mechanism for connection establishment.

A router operates at Layer 3 (Network layer) and makes forwarding decisions based on IP addresses, not by blindly forwarding electrical signals to all ports.

A switch operates at Layer 2 (Data Link) and uses MAC addresses to selectively forward frames only to the destination port, not to all ports like a hub.

A bridge operates at Layer 2, not Layer 1, and it forwards frames based on MAC addresses, not all electrical signals to all ports.

Switches that forward frames based on MAC addresses operate at Layer 2 (Data Link layer), not Layer 1 (Physical layer). Layer 1 deals with raw bit transmission over physical media, not frame forwarding.

A switch that uses MAC addresses to forward frames operates at Layer 2 (Data Link layer), not Layer 3 (Network layer). Layer 3 involves IP addresses and routing, not MAC-based forwarding.

Layer 4 (Transport) handles end-to-end communication, segmentation, and flow control using port numbers, not MAC addresses. A switch forwarding frames based on MAC addresses operates at Layer 2 (Data Link).

The default gateway does not perform NAT; its primary role is to forward packets from a local subnet to other networks. NAT is typically handled by a router or firewall, not the default gateway itself.

The default gateway is a router that forwards traffic from a local subnet to other networks, not a DHCP server. DHCP services are provided by a DHCP server, which may be a separate device or integrated into a router, but that is not the function of a default gateway.

DNS resolution translates domain names to IP addresses, but it does not route packets or serve as a gateway for traffic leaving the local subnet.

Hubs operate at Layer 1 and simply repeat electrical signals out all ports, so they do not segment broadcast domains; all devices connected to a hub share the same broadcast domain.

Bridges operate at Layer 2 and forward frames based on MAC addresses, but they do not filter broadcast traffic; broadcasts are flooded to all ports within the same broadcast domain.

A switch operates at Layer 2 and forwards frames based on MAC addresses, but it does not filter broadcast traffic; all ports in the same VLAN belong to the same broadcast domain. Therefore, a switch alone cannot separate broadcast domains.

169.254.1.1 is an APIPA address, not a private IP per RFC 1918. RFC 1918 defines private ranges as 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16.

172.32.1.1 falls within the 172.16.0.0/12 range (172.16.0.0 to 172.31.255.255) only if the second octet is between 16 and 31. Since 32 is outside that range, it is not a private IP per RFC 1918.

172.15.1.1 falls within the 172.16.0.0/12 range (172.16.0.0 to 172.31.255.255) defined by RFC 1918 for private IP addresses, but 172.15.1.1 is actually in the 172.8.0.0/13 range, which is not private; it is a public IP address.

In a star topology, each node connects to a central hub, not to exactly two other nodes, so it does not form a closed loop.

In a bus topology, all nodes connect to a single central cable, not to exactly two other nodes, and it does not form a closed loop.

In a mesh topology, each node connects to multiple other nodes, not exactly two, and it does not form a closed loop; it provides redundancy through multiple paths.

The IPv6 address :: (all zeros) is the unspecified address, used to indicate the absence of an address, not for loopback. Loopback in IPv6 is ::1.

127.0.0.1 is an IPv4 loopback address, not an IPv6 address. The question specifically asks for an IPv6 reserved loopback address.

2000::/3 is the prefix for global unicast addresses, not loopback. The IPv6 loopback address is ::1.

The workstation's IP (10.0.1.5/24) and server's IP (10.0.2.10/24) are on different subnets (10.0.1.0/24 vs 10.0.2.0/24). The workstation must send packets to its default gateway (10.0.1.1) for routing, not directly to the server via ARP.

DNS resolution is used to translate domain names to IP addresses, but the workstation already knows the server's IP address (10.0.2.10). The question does not involve name resolution, so sending packets to the DNS server is irrelevant.

The workstation will not drop the packets because it can send them to the default gateway (10.0.1.1), which will route them to the server on the different subnet (10.0.2.0/24).

A default gateway is not specifically for connecting VLANs; that is the role of a router or Layer 3 switch with inter-VLAN routing configured.

The default gateway does not provide DHCP services; DHCP is handled by a dedicated DHCP server or a router configured with DHCP services, not the default gateway itself.

The default gateway routes traffic between networks, but it does not perform NAT or IP address translation; that is typically the function of a router or firewall with NAT capabilities.

A hub operates at Layer 1 (physical layer) and simply repeats electrical signals to all ports; it does not use MAC addresses to forward data.

A router operates primarily at Layer 3 (Network layer) and uses IP addresses for forwarding decisions, not MAC addresses. It does not forward based on MAC addresses as a Layer 2 switch does.

A firewall operates at Layer 3 (or higher) of the OSI model, using IP addresses and port numbers to filter traffic, not MAC addresses for forwarding decisions.

DNS resolves domain names to IP addresses, but does not automatically assign IP addresses to devices.

ARP (Address Resolution Protocol) is used to resolve IP addresses to MAC addresses on a local network, not to automatically assign IP addresses.

ICMP is used for error reporting and diagnostic functions (e.g., ping, traceroute), not for automatic IP address assignment.

A Layer 2 switch forwards frames based on MAC addresses and does not perform routing; it cannot route between VLANs without a Layer 3 device.

A bridge operates at Layer 2 and forwards frames based on MAC addresses, but it does not perform routing between VLANs. It cannot forward traffic between different VLANs because it lacks the ability to make Layer 3 routing decisions.

A firewall can route between VLANs if configured with routing capabilities, but it is not the primary device required for routing between VLANs; a router or Layer 3 switch is typically used. The question specifically asks for the device required to route between VLANs, and a router is the standard answer.

STP prevents loops in a network topology but does not segment a switch into multiple broadcast domains; it operates at Layer 2 to manage redundant paths, not to create separate logical networks.

Subnetting is a logical division of an IP network at Layer 3, not a method to segment a single physical switch into multiple broadcast domains at Layer 2. VLANs operate at Layer 2 to create separate broadcast domains on the same switch.

QoS prioritizes network traffic but does not segment a switch into separate broadcast domains; it manages bandwidth allocation, not logical separation.

A Layer 3 switch performs routing based on IP addresses, but the question requires forwarding based on MAC addresses without routing. It also does not inherently connect different physical media like copper and fiber.

A media converter only changes the physical medium (e.g., copper to fiber) but does not forward frames based on MAC addresses; it operates at Layer 1, not Layer 2.

A router operates at Layer 3 (network layer) and makes forwarding decisions based on IP addresses, not MAC addresses. The question specifies that the device must forward frames based on MAC addresses and must not perform routing, which is the function of a Layer 2 bridge, not a router.

Excessive cable length causes attenuation and signal degradation, not collisions. Collisions are a Layer 2 issue related to duplex mismatch, not physical layer cabling limits.

Incorrect VLAN assignment does not cause collisions; it prevents communication between devices in different VLANs or causes connectivity issues, but collisions are a layer 1/physical layer issue related to duplex mismatch or cabling.

A /25 subnet provides 126 host addresses, which is more than the 50 needed per department, but it only allows for 2 subnets, not the required 4 departments.

A /27 subnet provides only 30 usable host addresses per subnet (2^(32-27)-2 = 30), which is insufficient for the requirement of at least 50 hosts per department.

A /24 subnet provides 256 total addresses, which is far more than the 200 needed (4×50), and it cannot be subdivided into four separate subnets without using a different mask.

The address 2001:db8::1 is a global unicast address (2001:db8::/32 is reserved for documentation), not a link-local address. Link-local addresses must start with fe80::/10.

ff02::1 is an IPv6 multicast address (all-nodes link-local multicast), not a link-local unicast address. Link-local addresses start with fe80::/10.

This is an IPv4 address, not an IPv6 address. The question specifically asks for a valid IPv6 link-local address, and 10.0.0.1 is in the private IPv4 range.

TCP is connection-oriented, not connectionless; UDP provides connectionless communication with minimal overhead, so this describes UDP, not TCP.

UDP supports multicast and broadcast transmissions, but TCP does not. The question asks for a characteristic of TCP that is NOT of UDP, so this option describes a feature of UDP, not TCP.

UDP is commonly used for real-time applications like VoIP and video streaming, not TCP. The question asks for a characteristic of TCP but NOT UDP, so this option describes a UDP characteristic.