This statement is false because the receiver is one of the fundamental elements of communication. In basic communication theory, a complete communication process requires at least four essential elements: the sender, the information or message content, the transmission medium or channel, and the receiver. If the receiver is missing, communication cannot be completed because there is no endpoint to accept, interpret, or respond to the transmitted information.
In datacom networks, this concept maps directly to real networking scenarios. A source host generates data, the data is carried over some medium such as copper, fiber, or wireless, and a destination host receives the data. Network devices such as switches and routers assist the forwarding process, but the fundamental communication model still includes both communicating endpoints. HCIA-Datacom emphasizes the complete sender-to-receiver process when introducing network communication basics, protocol encapsulation, and forwarding. Therefore, excluding the receiver from the communication elements is conceptually incorrect. The correct understanding is that sender, receiver, information content, and channel together form the essential basis of communication.

According to the original topology and service-planning question, the required VLANs are VLAN
100, VLAN 101, and VLAN 102, so options A, B, and C are correct. In HCIA-Datacom campus design questions, VLAN planning is usually based on service separation, such as user services, voice services, wireless services, management services, or specific departmental segmentation.
Each service type is assigned an appropriate VLAN so that broadcast domains are separated and policies can be applied more effectively.

Duplicate Address Detection (DAD) is an IPv6 mechanism used to verify that a unicast address is not already in use before the address is assigned to an interface. DAD is implemented using Neighbor Solicitation (NS) and Neighbor Advertisement (NA) messages, which are part of the ICMPv6 Neighbor Discovery protocol. Therefore, options A and D are correct.
When a host wants to verify a tentative IPv6 address, it sends an NS message for that address. If another node on the link is already using that address, that node responds with an NA message, indicating the address is duplicated and cannot be assigned. If no NA is received within the required period, the host assumes the address is unique and can use it.

In STP, the root bridge is elected based on the lowest bridge ID (BID). A BID is composed of the bridge priority and the MAC address of the switch. The device with the smallest BID becomes the root bridge. Therefore, if an administrator wants SW2 to become the root bridge, the most direct and correct method is to configure a lower system priority on SW2, making option C correct.

This statement is false . In classic STP, when a non-root switch detects a topology change, it does not continuously send configuration BPDUs upstream to notify the root bridge. Instead, it sends a Topology Change Notification (TCN) BPDU toward the root bridge through its root port. Each upstream switch acknowledges the TCN and forwards it further until it reaches the root bridge.
After the root bridge receives the topology change notification, the root bridge sets the Topology Change (TC) flag in its configuration BPDUs, and those configuration BPDUs are then propagated throughout the network. Therefore, topology-change notification and normal configuration BPDU transmission are different functions. The statement is wrong because it confuses TCN BPDUs with configuration BPDUs , and also inaccurately describes the notification behavior. HCIA-Datacom requires learners to distinguish between these BPDU types and understand how STP reacts to topology changes by accelerating MAC address aging and informing the network through the root bridge. This process helps the Layer 2 topology converge and reduces long-lasting forwarding inconsistencies after a link or port-state change.