H12-811_V2.0 Practice Questions

This question contains a contradiction: it states PC1 belongs to VLAN 10, but its connecting port GE1/0/1 is a trunk with the default PVID, which is 1. For the provided answers to be correct, we must assume the intended configuration is that the PVID of GE1/0/1 is set to 10 to place PC1 in VLAN 10.

A. After receiving the data frame sent from PC1 to PC2, SW1 adds the VLAN 10 tag to the data frame and then accepts the data frame.

PC1 sends an untagged Ethernet frame. When this frame arrives at the trunk port GE1/0/1, the switch tags it with the Port VLAN ID (PVID). Assuming the PVID is 10 (to match the requirement that PC1 is in VLAN 10), the switch adds a VLAN 10 tag to the frame for internal processing. This statement is correct under this assumption.

D. SW1 removes the VLAN 10 tag from the data frame before forwarding it from GE1/0/2 to PC2.

The frame, now tagged with VLAN 10, is forwarded towards PC2. The egress port, GE1/0/2, is an access port assigned to VLAN 10. A standard function of an access port is to remove the VLAN tag before sending the frame to the end device (which expects untagged frames). This statement correctly describes the behavior of an access port.

B. SW1 accepts the data frame sent from PC1 to PC2, but discards the data frame returned from PC2 to PC1. This is incorrect. If the PVID of GE1/0/1 is correctly set to 10, communication would be successful in both directions. A frame from PC2 would enter the access port GE1/0/2, be tagged with VLAN 10, and then forwarded out of the trunk port GE1/0/1. Since the PVID of GE1/0/1 is 10, the tag would be removed before sending to PC1, completing the communication.

C. The data frame processed inside SW1 does not carry any VLAN tag. This is incorrect. Once a frame enters a VLAN-aware switch from an access port or as an untagged frame on a trunk port, it is tagged internally to ensure it is switched only within its designated VLAN.

1. Huawei HedEx Documentation

S Series Switches Configuration Guide - VLAN Configuration. The section "VLAN Tagging" details port behavior: "When a trunk port receives untagged frames

it adds its PVID to the frames... When an access port sends frames

it removes the VLAN tags from the frames." This directly supports the logic for answers A and D.

2. Huawei HedEx Documentation

CloudEngine S12700E Series Switches Product Documentation - Feature Description - Ethernet Switching. The section "Fundamentals of VLAN" explains: "A switch identifies VLANs based on VLAN tags. After a frame enters a switch

the switch adds a VLAN tag to the frame to identify the VLAN to which the frame belongs." This refutes option C.

The status of a logical Eth-Trunk interface is determined by the number of its active member interfaces. By default, an Eth-Trunk interface is considered 'Up' as long as the number of active member links is greater than or equal to the configured minimum threshold. The default value for this minimum threshold is 1. In this scenario, one member interface (GE1/0/1) is Up. Since the number of active links (1) is not less than the default minimum (1), the Eth-Trunk 1 logical interface will be in the Up state.

B. The states of member interfaces do not need to be the same. The logical state depends on the number of active links.

C. This is incorrect because the default minimum number of active links is 1. The minimum is reached, so the Eth-Trunk is Up.

D. This is incorrect. A key purpose of Eth-Trunk is to provide redundancy, allowing the logical link to function even if some member links fail.

1. Huawei VRP V800R021C00 Product Documentation

"Eth-Trunk Configuration" section

"Fundamentals". It specifies that the Eth-Trunk interface remains Up if the number of active member interfaces is not less than the configured lower threshold.

2. Huawei HCIA-Datacom V1.0 Training Material (2020)

Chapter 3: Link Aggregation

pp. 3-45. "An Eth-Trunk interface goes down only when the number of active member interfaces is less than the configured lower threshold for the number of active interfaces. By default

this threshold is 1."

3. Huawei Command Reference for S Series Switches

display eth-trunk command description. The output and description confirm that the Eth-Trunk status is determined by the number of Up member ports relative to the minimum

The command display ip routing-table protocol ospf is used to view the global IP routing table and filter the output to show only the routes that were learned through the OSPF protocol and have been successfully installed. This command directly shows the active OSPF routes used for packet forwarding.

B. display ospf peer shows the status of OSPF neighbor adjacencies, not the routes in the routing table.

C. display ospf interface provides OSPF-related details for each interface, such as cost and state, not routes.

D. display ospf routing displays the OSPF routing database (LSDB), which contains raw LSA information before the SPF algorithm calculation.

1. Huawei VRP V800R019C00 Command Reference

"IP Routing Commands > Routing Table Commands > display ip routing-table". The documentation details the usage of the protocol keyword to filter the routing table display based on the route's origin protocol

such as OSPF.

2. Huawei HCIA-Datacom V1.0 Training Material

"Section 5.3.4 OSPF Troubleshooting". This material distinguishes between checking the routing table (display ip routing-table)

the LSDB (display ospf lsdb)

and neighbor states (display ospf peer).

When multiple static routes are configured for the same destination network prefix, the router selects the route with the lowest preference value to install in its routing table. In this configuration, the preferences are 60 (default for 10.1.1.2), 70, 50, and 100. The route with the next hop 10.1.3.2 has the lowest preference value of 50, making it the optimal and active route.

A. The route via 10.1.4.2 has a preference of 100, which is higher than 50 and therefore not preferred.

B. The route via 10.1.1.2 uses the default preference of 60, which is higher than 50 and not preferred.

C. The route via 10.1.2.2 has a preference of 70, which is higher than 50 and therefore not preferred.

1. Huawei VRP V800R019C00 Command Reference

"IP Routing Commands > Static Route Commands > ip route-static". This document states

"If multiple static routes to the same destination are configured

the one with the highest preference (smallest preference value) is selected." It also confirms the default preference value is 60.

The IP address 224.0.0.1 belongs to the Class D address range (224.0.0.0 to 239.255.255.255), which is reserved for IP multicast traffic. These addresses are used to identify a group of destination hosts, not a single host interface. Therefore, a Class D address cannot be configured as a unicast IP address for a host. The address 224.0.0.1 is specifically assigned to the "All Hosts" multicast group on the local network segment.

A. 172.16.1.1/16 is a valid private Class B IP address that can be assigned to a host.

B. 192.168.1.1/24 is a valid private Class C IP address that can be assigned to a host.

C. 10.0.0.1/8 is a valid private Class A IP address that can be assigned to a host.

1. Huawei. (2020). HCIA-Datacom V1.0 Training Material (Version 1.0). Section: IP Addressing Basics

Subsection: IP Address Classification. "Class D addresses are multicast addresses

ranging from 224.0.0.0 to 239.255.255.255." (Page 2-15).

2. Postel

J. (1981). RFC 791: Internet Protocol. The Internet Society. Section 3.1

"Class D addresses are used for multicasting".

3. Deering

S. (1989). RFC 1112: Host Extensions for IP Multicasting. The Internet Society. Section 4

"Class D addresses are used as destination addresses for multicast datagrams... They are not to be used as source addresses."

While it is a common and recommended best practice to plan VLANs in a structured and logical manner, the statement that VLAN IDs must be allocated consecutively is incorrect. There is no technical protocol or hardware requirement that mandates consecutive numbering. The primary goals of VLAN planning are to achieve logical network segmentation, contain broadcast traffic, enhance security, and ensure scalability. These goals can be met with non-consecutive numbering schemes (e.g., VLANs 10, 20, 30 for different departments). Insisting on a strictly consecutive allocation can even be detrimental to future scalability if a service group outgrows its initial block of numbers. Therefore, the use of the absolute term "must" makes the statement false.

This is a True/False question. The alternative, "True," is incorrect because it presents a flexible design guideline as a rigid, mandatory rule. Network design principles emphasize logical grouping and planning for future growth, which does not strictly equate to consecutive numbering.

1. Huawei. Campus Network Design Guide. Section: "Network Design". This type of guide typically discusses VLAN planning best practices

emphasizing logical grouping of services (e.g.

by department

service type) and planning for future expansion

rather than mandating a specific numbering scheme like consecutive allocation.

2. Kurose

J. F.

& Ross

K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. While not a Huawei-specific source

this foundational university-level textbook explains VLANs as a tool for creating logical broadcast domains. It describes their function and configuration without imposing a rule of consecutive ID allocation

reinforcing that this is a local administrative policy choice

not a protocol requirement.

The statement accurately describes a key difference between SNMP Trap and Inform Request messages. Both are used by an SNMP agent (managed device) to asynchronously notify an NMS of an event. However, a Trap is an unconfirmed notification; the agent sends the message and does not expect a reply. An Inform Request is a confirmed notification; the agent sends the message and waits for an acknowledgment from the NMS. If no acknowledgment is received, the agent may resend the Inform Request. This confirmation mechanism makes Inform more reliable than Trap for critical notifications.

This is a True/False question. The statement is factually correct, so option A (True) is the only correct choice.

1. Huawei. (2020). HCIA-Datacom V1.0 Training Material (Model H12-811). Section: Network Management and O&M

Subsection: SNMP Protocol Basics

Chapter: SNMP Operations. (This chapter explicitly contrasts Trap and Inform

stating that Inform messages require acknowledgment from the NMS

unlike Trap messages).

2. Case

J.

Fedor

M.

Schoffstall

M.

& Davin

J. (1990). RFC 1157: A Simple Network Management Protocol (SNMP). Section 4.1.3

"The Trap-PDU." (Describes the unconfirmed nature of Traps).

3. Levi

D.

Meyer

P.

& Stewart

B. (2002). RFC 3416: Version 2 of the Protocol Operations for the Simple Network Management Protocol (SNMP). Section 4.2.7

"The InformRequest-PDU." (Defines the InformRequest and its requirement for a response PDU as acknowledgment).

The statement is false. A basic communication model fundamentally consists of at least four essential elements: a source (sender), a message (content), a transmission medium (channel), and a destination (receiver). Communication is the process of conveying information from a sender to a receiver. Without a receiver to interpret the message, the process is incomplete and cannot be considered communication. Therefore, the receiver is a mandatory element.

A. This option is not provided, but if it were "True," it would be incorrect because a receiver is a non-negotiable component of any complete communication model, including the Shannon-Weaver model.

1. Shannon

C. E. (1948). A Mathematical Theory of Communication. Bell System Technical Journal

27(3)

379-423. https://doi.org/10.1002/j.1538-7305.1948.tb01338.x. The foundational model explicitly includes a "destination" (receiver).

2. Kurose

J. F.

& Ross

K. W. (2017). Computer Networking: A Top-Down Approach (7th ed.). Pearson. Chapter 1

Section 1.1 "What Is the Internet?"

implicitly defines communication as occurring between end systems (which act as senders and receivers).

The statement is incorrect. When a downstream device on an STP-enabled network detects a topology change, it does not send configuration BPDUs. Instead, it sends a special type of BPDU called a Topology Change Notification (TCN) BPDU out of its root port. This TCN BPDU is sent repeatedly until the upstream switch acknowledges it by setting the Topology Change Acknowledgment (TCA) bit in its next configuration BPDU. The process is designed to inform the root bridge of the change, which then instructs all switches to shorten their MAC address aging time.

The statement is presented as a factual claim. It is false because the type of BPDU sent by the downstream device to signal a topology change is a TCN BPDU, not a standard configuration BPDU.

1. Huawei HCIA-Datacom V1.0 Training Material

"STP Topology Change

" Section: STP Other Concepts. This section details the TCN process

specifying that TCN BPDUs

not configuration BPDUs

are sent upstream to notify the network of a topology change.

2. IEEE Std 802.1D-2004

"IEEE Standard for Local and metropolitan area networks--Media Access Control (MAC) Bridges

" Clause 17.5

"Topology change." This standard defines the protocol behavior

stating that a bridge detecting a topology change shall transmit TCN messages on its root port.

The statement is correct. The 12-bit VLAN ID field in the 802.1Q standard limits the number of unique VLANs to 4094. This is insufficient for large-scale, multi-tenant cloud data centers where tens of thousands of isolated tenant networks may be required. VXLAN addresses this limitation by using a 24-bit VXLAN Network Identifier (VNI), which supports up to 16 million unique logical networks, providing the necessary scale for modern virtualized environments.

Note: The question format is a single statement to be evaluated as true or false. "A" is interpreted as "True" or "Correct".

This question is a true/false evaluation of a single statement. There are no other options to evaluate as incorrect.

1. Huawei

"HCIA-Datacom V1.0 Training Material"

Module "VXLAN Technology". This courseware explicitly states

"The 12-bit VLAN ID defined in IEEE 802.1Q can identify only a maximum of 4094 VLANs... VXLAN uses a 24-bit VNI to identify up to 16 million tenants."

2. IETF RFC 7348

"Virtual eXtensible Local Area Network (VXLAN): A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks"

Section 1. Introduction. The RFC states

"The VLAN ID is 12 bits long

which limits the number of VLANs to 4096. This is a small number for a service provider that may be supporting thousands of customers." It then introduces the 24-bit VNI as the solution.