The exhibit assigns SW1 GE1/0/1 to VLAN 10 and GE1/0/2 to VLAN 20, while the trunk between SW1 and SW2 carries the required VLANs. When PC1 is connected to GE1/0/1, its untagged frames are classified into VLAN 10. PC2 is also in VLAN 10, so PC1 can communicate with PC2 at Layer 2, whereas PC3 is in VLAN 20 and is separated by the VLAN boundary. SW1 learns PC1 ' s source MAC address together with VLAN 10 and ingress interface GE1/0/1. When PC1 is moved to GE1/0/2, its untagged frames are now placed in VLAN 20. After MAC relearning occurs, PC1 can communicate with PC3, which is also in VLAN 20, but not directly with PC2 in VLAN 10 unless Layer 3 inter-VLAN routing is provided. Consequently, statement A is false because PC1 is not isolated from both hosts after the move; it can communicate with PC3.

In IPv6, link-local addresses use the prefix FE80::/10 . These addresses are automatically generated or configured for communication on the local link only and are not routed across Layer 3 boundaries. Therefore, among the given options, FE80::FA63:DBFF:FE9E:10 is the correct link-local address, making option C correct.

Options A and B belong to the Unique Local Address (ULA) space, which uses the prefix FC00::/7 . These addresses are intended for private internal IPv6 networks, somewhat similar in purpose to private IPv4 address ranges, but they are not link-local addresses. Option D , which starts with 2001::, is a global unicast address , used for routable communication across IPv6 networks. HCIA-Datacom teaches that link-local addresses are essential in IPv6 because they are used for functions such as neighbor discovery, router discovery, and routing protocol communication on the local segment. Even when a device has global unicast addresses, the link-local address still plays an important role in normal IPv6 operation and protocol adjacency establishment.

The statement describes the broader evolution of enterprise data centers from isolated, hardware-centric facilities toward cloud-based resource pools and multi-site service architectures. Virtualization and cloud platforms decouple many applications from individual physical servers and allow compute, storage, and network resources to be centrally orchestrated and delivered to internal or external consumers. As service scale and continuity requirements increase, organizations may deploy multiple data centers across sites for disaster recovery, geographic access, capacity expansion, active-active services, or regulatory separation. Network technologies such as VXLAN-based fabrics and data center interconnect mechanisms support this transition by extending or interconnecting services while maintaining segmentation and reachability policies. The exact architecture depends on business requirements, but the direction described in the question—from a single data center toward multi-site, multi-data-center construction as services evolve—is consistent with Huawei Datacom data center design concepts. Therefore, the statement is TRUE and option A is the correct answer.

The source key marks this statement TRUE, but the topology makes that answer technically incorrect. R1 is shown with interface address 10.0.12.1/24, which automatically installs a directly connected route to 10.0.12.0/24. On Huawei VRP, a direct route has preference 0, whereas a static route has preference 60 unless another value is configured. The two commands do configure two static routes with the same preference, and equal-preference static routes can support load balancing when they are the best routes to a destination. Here, however, both static routes are for the same prefix that R1 already owns as a connected network. The direct route has a higher priority because its preference value is smaller, so it is selected in the active IP routing table instead of the two preference-60 static routes. Therefore the assertion that R1 has two active equal-cost routes to 10.0.12.0/24 is FALSE as the question and exhibit are written. The verified answer is B, and the original source key A should be corrected.

According to the topology and the original question scenario, the correct answer is 10.2.1.1, so option B is selected. In HCIA-Datacom troubleshooting questions of this type, the goal is usually to identify the correct management address, next-hop interface address, or testing destination based on the addressing design shown in the figure.

The answer depends on the role of the device and the direction of the connectivity verification. In such topologies, each interface belongs to a specific network segment, and the selected address must match the intended test target on that segment. If the test is being performed toward the neighboring device or a specific reachable interface, using the correct IP on the proper subnet is essential. An incorrect address may still look familiar from the topology but would not represent the right test endpoint. HCIA-Datacom places strong emphasis on reading topology labels carefully, matching interface addresses to subnet assignments, and choosing the correct destination when using tools such as ping, tracert, or service-specific connectivity tests. This question mainly checks address recognition accuracy in a troubleshooting context.

The command output in the exhibit shows that both AP radios are enabled, so a disabled radio is not supported by the evidence. The 5 GHz radio has relatively low channel utilization, while the 2.4 GHz radio reports channel utilization of approximately 90 percent. Such a high utilization value indicates that the air interface is heavily occupied by transmissions or interference. Huawei WLAN troubleshooting guidance identifies a busy air interface and a heavily loaded AP as possible causes of STA association failures because management and authentication frames may be delayed or lost when contention is severe. The displayed radio information alone does not prove that the affected STAs are in a blacklist or absent from a whitelist; those conditions require separate STA or VAP access-control information. Therefore, option A is the only choice directly supported by the command output. The correct troubleshooting interpretation is that excessive channel utilization on the radio can make the air interface busy and prevent some STAs from completing association successfully. The verified answer is A.

This statement is true . When a device has multiple routes to the same destination prefix, route selection is based first on the longest prefix match , and when prefix length is the same, the device compares the route preference or administrative priority associated with each routing source. On Huawei devices, a direct route has a better preference than a static route , so the direct route is selected first when both routes have the same destination and mask.

A direct route is generated automatically when an IP address is configured on an interface and that interface is Up. Because the destination network is directly connected, this route is considered more trustworthy and efficient than a manually configured static route pointing to the same prefix. HCIA-Datacom uses this principle to explain route selection, routing-table generation, and troubleshooting cases where a configured static route does not appear as the active route because a direct or dynamic route has higher priority. This is a basic but important concept in IP forwarding and helps engineers correctly interpret routing tables on Huawei routers and Layer 3 switches.

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. Options B and C are incorrect because Router Solicitation (RS) and Router Advertisement (RA) are used for router discovery, prefix advertisement, and stateless address autoconfiguration, not for DAD itself. HCIA-Datacom emphasizes the distinction between Neighbor Discovery functions, including address resolution, next-hop reachability, router discovery, and duplicate address detection in IPv6 networks.

All four configured static routes have the same destination prefix, 20.0.0.0/30, and the question states that every next hop is reachable. Huawei route selection first considers route preference when choosing among routes from the same or different route sources. For static routes, a smaller preference value means a higher priority. The four preferences shown are 60 for next hop 10.1.1.2, 70 for 10.1.2.2, 100 for 10.1.3.2, and 50 for 10.1.4.2. Because 50 is the smallest preference, the route through 10.1.4.2 is selected as the active route in the IP routing table. The other configured static routes can remain as lower-priority alternatives and may become active if the preferred route becomes invalid, depending on reachability and configuration. Equal-cost load balancing would require routes with the same relevant preference and cost after route selection. That is not the case here. Therefore, the next hop of the selected route to 20.0.0.0/30 is 10.1.4.2, making option A correct.

To check OSPF-learned routes in the global IP routing table , the correct command is display ip routing-table protocol ospf , so option A is correct. This command filters the routing table and shows only the routes whose source protocol is OSPF. It is especially useful when verifying whether OSPF-learned routes have been successfully installed into the forwarding table after neighbor establishment and LSDB calculation.

Option B , display ospf peer, is used to check OSPF neighbor information and adjacency states, not the routing table. Option C , display ospf interface, shows OSPF-related parameters on interfaces such as timers, network type, and cost. Option D , display ospf routing, displays OSPF route information maintained by the OSPF process itself, but the question specifically asks about routes in the global routing table , which is the RIB used for actual forwarding decisions. HCIA-Datacom distinguishes between protocol-specific route information and the final routing table seen by the device. Understanding this distinction helps engineers verify whether a protocol has only learned topology information or has actually produced usable forwarding entries.