H12-811_V2.0 Exam Dumps - HCIA-Datacom V2.0

On Huawei switches, a physical Ethernet interface usually works as a Layer 2 switch port by default. A Layer 2 interface cannot be assigned an IP address directly. If an administrator wants to configure an IP address on such an interface, the interface must first be converted into a Layer 3 interface . The command used for this is undo portswitch , so option B is correct.

After this command is executed, the interface no longer behaves as a Layer 2 switching port and can then support Layer 3 features such as direct IP address configuration. Options A , C , and D are all Layer 2 port-type commands used to configure the interface as a trunk, access, or hybrid port. These commands do not solve the problem because they keep the interface operating at Layer 2. HCIA-Datacom emphasizes the difference between Layer 2 switching interfaces and Layer 3 routed interfaces on switches. Understanding when to use undo portswitch is important in campus network deployment, especially when configuring routed uplinks, management interfaces, or inter-device Layer 3 links on switches.

The protocol that cannot directly modify device configurations such as interface IP addresses or device names is SFTP , so option C is correct. SFTP is a secure file transfer protocol that runs over SSH and is mainly used to upload, download, and manage files between a client and a network device. It is commonly used for tasks such as transferring configuration files, system software, patches, or log files, but it does not itself provide an interactive or structured configuration modification mechanism.

By contrast, STelnet allows secure remote CLI login, through which an administrator can directly enter commands to change device settings. NETCONF is specifically designed for network configuration management and can modify configurations in a structured manner. SNMP can also modify certain managed object values through write operations when permissions and MIB support allow it, although in practice it is used more often for monitoring. HCIA-Datacom distinguishes between management-plane protocols based on their roles: interactive access, structured configuration, monitoring, and file transfer. This question checks whether the learner can identify SFTP as a file transfer tool rather than a direct configuration protocol.

Several upper-layer management and file transfer protocols use SSH as their secure transport foundation. SFTP is the SSH File Transfer Protocol and operates over SSH, making option C correct. STelnet is secure Telnet implemented over SSH, so option D is also correct. NETCONF commonly uses SSH as its transport protocol for secure configuration management and device orchestration, making option B correct as well.

Option A, DNS, does not use SSH as its normal transport protocol. Traditional DNS operates over UDP or TCP port 53, depending on the query or transfer type. Although DNS security extensions and encrypted DNS variants exist, they are not based on SSH. HCIA-Datacom emphasizes the role of SSH in secure network management because it replaces insecure plaintext protocols and provides confidentiality, integrity, and authentication. In practical Huawei enterprise deployments, SSH-based protocols are widely used for interactive device login, automated configuration delivery, and secure file operations. This question tests recognition of management protocols that inherit SSH’s secure channel rather than protocols that operate independently at the application layer.

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.

An ARP Request is carried in an Ethernet broadcast frame whose destination MAC address is FF-FF-FF-FF-FF-FF. When SW1 receives the ARP Request from PC2, it does not look up a single destination MAC entry and send the frame only toward PC3. Instead, the switch floods the broadcast frame through all other eligible ports in the same VLAN, excluding the ingress port. The 300-second MAC aging time reinforces why the earlier PC1 entry is not relevant after 30 minutes: a dynamic entry that is not refreshed will age out long before PC2 is connected. PC4 ' s continued communication with PC3 may refresh MAC entries associated with that traffic, but it does not transform PC2 ' s ARP Request into a known unicast frame. ARP relies on broadcast precisely because the sender does not yet know the target ' s Layer 2 address. Therefore, the claim that SW1 forwards the request only through GE1/0/3 is incorrect. The verified answer is FALSE, option B.

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 C is false. In this configuration, the NAT address group test contains the public address range 100.1.23.1 to 100.1.23.254 , and the address group works in PAT mode . Port Address Translation allows multiple different intranet users to share the same public IP address while being distinguished by different transport-layer port numbers. Therefore, intranet users with different private IP addresses do not have to use different post-NAT public IP addresses.

Option A is true because 100.1.23.254 is included in the configured public address pool and can be used for source NAT. Option B is also true because NAT is enabled on GE0/0/2 , so if user traffic does not leave through that interface, the NAT policy may not be applied and public access may fail. Option D is true because the configured source address range includes 192.168.1.100, which falls within 192.168.0.0 to 192.168.255.255. HCIA-Datacom teaches that NAT behavior depends on matching traffic, address pools, PAT or no-PAT mode, and the interface where NAT is enabled. This question mainly tests understanding of source NAT and PAT address-sharing behavior.

This statement is true . In SNMP, both Trap and Inform messages are used by managed devices to proactively report alarms or events to the Network Management System (NMS) . However, their reliability behavior is different. A Trap is sent without requiring an acknowledgment from the NMS. Once it is transmitted, the sender does not confirm whether the manager actually received it.

By contrast, an Inform Request requires the NMS to send a response confirming receipt. If the managed device does not receive the acknowledgment within the expected time, it can retransmit the Inform message. Because of this, Inform is considered more reliable than Trap, although it also introduces slightly more overhead. HCIA-Datacom highlights this difference when explaining SNMP-based monitoring and alarm reporting. In real network O & M scenarios, the choice between Trap and Inform depends on the required balance between reliability and simplicity. This question tests a very standard SNMP knowledge point: Trap is unacknowledged , while Inform is acknowledged . Understanding this distinction helps network engineers choose suitable alarm reporting mechanisms in enterprise monitoring platforms.