Static MAC address entries are manually configured and stored in the switch's configuration file, making them persistent across reboots. These entries remain in the MAC address table after a restart, unlike dynamic entries, which are lost.

This statement is false. In Layer 3 in-path WLAN networking, the WAC and Fit APs communicate over Layer 3, which means the APs must discover the WAC through methods that are valid across Layer 3 boundaries. Broadcast is a Layer 2 mechanism and cannot normally be used for WAC discovery across Layer 3 networks. Therefore, saying that APs can obtain the WAC address through broadcast or DHCP in this scenario is incorrect.
In Huawei WLAN deployments, Fit APs can commonly discover the WAC address through methods such as DHCP option-based discovery, DNS, or preconfigured controller information, depending on the deployment model and product features. Because the WAC and AP are not in the same Layer 2 broadcast domain in Layer 3 in-path networking, broadcast discovery is not the standard mechanism here. HCIA-Datacom stresses the difference between Layer 2 direct discovery and Layer 3 discovery methods because this affects initial AP registration, CAPWAP establishment, and troubleshooting when APs fail to go online. Understanding the discovery mechanism is essential when planning IP addressing, DHCP options, and controller placement in enterprise WLAN designs.

Option D is correct. The AAA configuration binds the domain huawei.com to the authentication scheme auth1, which uses RADIUS as the authentication mode, and to the accounting scheme acc1, which also uses RADIUS. Therefore, when a user logs in with a user name in the format [email protected], the device parses the suffix @huawei.com, matches the domain, and applies the configured RADIUS authentication method.

Layer 2 switches operate at the data link layer, handling frames based on MAC addresses. They maintain a MAC address table to record mappings between MAC addresses and interfaces, allowing efficient frame forwarding within the local network.

This statement is true. Traditional VLANs use a 12-bit VLAN ID, which means that only about
4094 usable VLANs are available. In modern data centers, especially in cloud and virtualization environments, that scale is often insufficient because a very large number of tenants, services, and virtual machines need isolated network segments.
VXLAN addresses this limitation by introducing the VNI (VXLAN Network Identifier), which is 24 bits long. This allows support for up to about 16 million logical segments, greatly expanding the number of isolated Layer 2 networks that can be created across an IP underlay. Because of this, VXLAN is widely used in modern data centers to provide scalable tenant isolation, flexible service deployment, and large Layer 2 extension across physical boundaries. HCIA-Datacom highlights VXLAN as a key overlay technology that solves the VLAN scale problem in virtualized data center environments. It allows a much larger number of VMs and tenants to be isolated than traditional VLAN-based solutions can support, making it essential for modern cloud-oriented and large-scale data center networking.