The HCIA-Datacom V2.0 (H12-811_V2.0)

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.

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.

All four options are possible causes of FTP login failure, so the correct answer is A, B, C, and D.

Option A is correct because if the FTP server function is not enabled on the Huawei device, the device cannot provide FTP services and the client cannot log in. Option B is also correct because if the authorized directory is not specified for the FTP user, the user may not be able to complete login or access file services properly, depending on the FTP user configuration requirements. Option C is correct because an FTP user account must be configured with the required username and password; otherwise, authentication cannot succeed. Option D is also correct because if the network between the FTP client and the device is unreachable, the client cannot establish the FTP connection at all.

In HCIA-Datacom troubleshooting, FTP login failure is usually checked from four aspects: service enablement, user configuration, permission or directory authorization, and network connectivity. This question tests standard remote maintenance troubleshooting logic for file transfer services on Huawei network devices.

The IPv6 basic header has a fixed length of 40 bytes and contains eight fields: Version, Traffic Class, Flow Label, Payload Length, Next Header, Hop Limit, Source Address, and Destination Address. The Source IPv6 Address is therefore part of the IPv6 header. Hop Limit is also present and serves a function comparable to the IPv4 TTL field by limiting how many Layer 3 forwarding hops a packet can traverse. Next Header identifies the type of extension header or upper-layer protocol that follows the IPv6 basic header. A source MAC address is not part of the IPv6 header. MAC addresses belong to the data-link-layer frame header, such as an Ethernet header, and are relevant only to the current Layer 2 segment. As an IPv6 packet is routed, Ethernet source and destination MAC addresses can change from hop to hop while the IPv6 source and destination addresses normally remain unchanged end to end. Therefore A, B, and C are IPv6 header fields, while D is not. The correct answer is A, B, and C.

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.

STP selects one root port on each non-root bridge based on the lowest accumulated path cost toward the root bridge.

SW1 is the root bridge, so SW3 selects GE1/0/2 as its root port because the direct path to SW1 has a cost of 10. Therefore, GE1/0/3 on SW3 is not a root port.

SW2 can reach the root through SW3 with a total cost of 30, which is lower than its direct path cost of 50. Consequently, GE1/0/3 on SW2 becomes its root port, while GE1/0/1 and GE1/0/2 do not.

SW4 selects GE1/0/1 toward SW3 because that path provides a total root cost of 40.

Therefore, option C identifies a root port, whereas A, B, and D identify ports that are not root ports.

================

This statement is true. From the routing table, the entry 10.0.12.0/24 Direct ... NextHop 10.0.12.1 Interface Vlanif2 indicates that the network 10.0.12.0/24 is directly connected through Vlanif2, and the local interface address associated with that directly connected network is 10.0.12.1.

This conclusion is further supported by the host route 10.0.12.1/32 Direct ... 127.0.0.1 Vlanif2, which represents the local IP address of the interface itself. On Huawei devices, when an IP address is configured on an interface, the routing table commonly generates a direct route to the connected network, a host route to the interface IP itself, and sometimes a host route to the broadcast address where applicable in IPv4. Therefore, from the displayed entries, it can indeed be inferred that VLANIF 2 has the IP address 10.0.12.1/24. HCIA-Datacom uses these routing-table characteristics to help learners identify connected interfaces, local addresses, and route origins during troubleshooting and route analysis on routers and Layer 3 switches.

DHCP automatically assigns IP configuration parameters to network clients. During initial address acquisition, a DHCP client broadcasts a DHCPDISCOVER message to locate available DHCP servers.

Ethernet switches normally forward these broadcasts only within the originating VLAN.

In this scenario, PC1 belongs to VLAN 2, while PC2 and the DHCP server belong to VLAN 3. The trunk connection permits traffic from both VLANs but maintains their Layer 2 isolation.

Therefore, DHCP broadcasts generated by PC1 in VLAN 2 cannot directly reach the DHCP server in VLAN 3.

PC2 can obtain an address because it shares the DHCP server ' s broadcast domain.

Communication between these VLANs would require Layer 3 forwarding, and DHCP relay functionality would normally be required to forward DHCP requests across the VLAN boundary.

Consequently, the administrator ' s explanation is correct.

================

The switch configuration places GE1/0/1 in VLAN 10 and GE1/0/2 in VLAN 20. The inter-switch trunk carries both VLANs.

Initially, PC1 connects through GE1/0/1, placing its traffic in VLAN 10. It can therefore communicate with PC2, which belongs to the same VLAN.

After PC1 moves to GE1/0/2, its traffic belongs to VLAN 20. Consequently, PC1 can communicate with PC3 rather than PC2.

Statement B is false because PC1 can still reach PC3 after the interface change.

Statement D is also false because dynamic MAC address learning associates the source MAC address, VLAN ID, and ingress interface identifier. It does not create the stated mapping using the interface ' s own MAC address.

Statements A and C correctly describe the expected Layer 2 communication.

================