HCIA-Datacom V2.0 온라인 연습
최종 업데이트 시간: 2026년04월21일
당신은 온라인 연습 문제를 통해 Huawei H12-811_V2.0-ENU 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 H12-811_V2.0-ENU 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 60개의 시험 문제와 답을 포함하십시오.

정답:
Explanation:
This scenario describes the classic router-on-a-stick inter-VLAN routing design. A single physical interface on R1 connects to switch S1, and multiple sub-interfaces are created on that physical interface to serve as gateways for multiple VLANs. Therefore, if R1 provides Layer 3 gateway functions for VLAN 2 and VLAN 3, sub-interfaces such as GE0/0/1.2 and GE0/0/1.3 must be configured, so option A is correct.
Because PC2 and PC3 are connected to switch S1, S1 learns their source MAC addresses dynamically and stores them in its MAC address table, making option B correct. R1 receives tagged frames from different VLANs on the trunk link and, through its sub-interfaces, can identify and terminate frames for VLAN 2 and VLAN 3, so option C is also correct.
Option D is incorrect because hosts in different VLANs do not need to be connected to different physical switches; VLAN separation is logical, not necessarily physical. HCIA-Datacom uses this deployment to explain inter-VLAN communication, 802.1Q trunking, and flexible campus gateway design using limited router interfaces.
정답:
Explanation:
When two OSPF routers reach the Full state, it means that adjacency establishment has been successfully completed and the routers have synchronized the necessary link-state information for that area. For this to happen, the two routers must have different router IDs, so option A is correct. They must also belong to the same OSPF area on the interfaces used to form the adjacency, making option B correct. Once adjacency reaches Full state, the routers have synchronized their link-state databases for that area, so option D is also correct.
Option C is incorrect because the OSPF process ID is only locally significant on a device. Two neighboring routers do not need to use the same process ID to establish adjacency. HCIA-Datacom teaches that OSPF neighbor formation depends on matching parameters such as area ID, network type, hello/dead timers, authentication settings, and subnet consistency, but not on the locally configured process number. This question is important because many learners mistakenly believe the process ID must match between devices, while in fact OSPF uses protocol parameters exchanged in packets rather than local process labels to form neighbor relationships.

정답:
Explanation:
After STP convergence, only ports in the forwarding state participate in active traffic forwarding, while redundant ports may be placed into the blocking or discarding state to eliminate loops. According to the topology and STP role election shown in the question, the valid forwarding path from SW1 to SW4 is SW1 → SW3 → SW4, so option B is correct.
This means that the direct alternative path or the path through SW2 is not the active spanning-tree forwarding path after election and state transition. STP selects paths based on the root bridge, path cost, bridge ID, and port ID. Once the root bridge and port roles are determined, some links remain active and others are blocked to ensure a loop-free Layer 2 topology. HCIA-Datacom emphasizes that the resulting forwarding topology is a tree, not a mesh, even if the physical topology contains redundant links. Understanding the actual forwarding path after STP convergence is important for troubleshooting connectivity, predicting traffic behavior, and verifying whether bridge priority and path-cost settings have produced the intended design outcome in campus switching networks.

정답:
Explanation:
An Ethernet switch learns MAC address entries dynamically by examining the source MAC address of incoming frames. When SW1 first receives frames from PC1 on GE1/0/1, it creates a MAC address table entry mapping PC1’s MAC address to that port. If PC1 later sends frames that arrive on GE1/0/2, SW1 updates the learned entry to reflect the new incoming interface. Therefore, option B is correct: SW1 saves the mapping between PC1’s MAC address and GE1/0/2 and removes or overwrites the old mapping associated with GE1/0/1.
Option A is incorrect because a single dynamic MAC address is not normally maintained on two different ports within the same VLAN at the same time; that would cause forwarding ambiguity.
Option C is incorrect because a normal move of one MAC address does not require clearing the entire MAC table.
Option D is also incorrect because switches update MAC learning dynamically upon receiving new source traffic and do not have to wait for the previous entry to age out. HCIA-Datacom uses this principle to explain MAC address learning, migration, and troubleshooting of loops or host movement in switched Ethernet networks.

정답:
Explanation:
In STP, the root bridge is elected based on the lowest bridge ID (BID). A BID is composed of the bridge priority and the MAC address of the switch. The device with the smallest BID becomes the root bridge. Therefore, if an administrator wants SW2 to become the root bridge, the most direct and correct method is to configure a lower system priority on SW2, making option C correct.
Option A is incorrect because port priority affects port-role selection in some tie-breaking scenarios, but it does not determine root-bridge election.
Option B is the opposite of what is required, because a higher system priority makes the BID larger and reduces the chance of being elected as root.
Option D is also incorrect because root path cost is used by non-root bridges to select the best path to the existing root bridge; it does not determine which switch becomes the root bridge in the first place. HCIA-Datacom stresses that bridge priority tuning is the standard administrative method used to control root bridge placement in campus networks for stable and predictable Layer 2 topology design.
정답:
Explanation:
On a non-root bridge, the root port is the port that receives the best BPDU toward the root bridge. STP selects the root port by comparing several parameters in order. The first important parameter is the root path cost (RPC), so option B is correct. If multiple ports have the same RPC, the switch then compares the bridge ID (BID) of the upstream device sending the BPDU, making option C correct. If those are still equal, the switch compares the port ID (PID) of the upstream sending port, so option D is also correct.
If all of those values remain identical from the switch’s perspective, the device can finally compare the local port ID to determine which local interface becomes the root port, so option A is also correct. HCIA-Datacom teaches this comparison logic as part of STP election rules. The process ensures deterministic selection of a single root port on every non-root switch. Understanding the comparison sequence is essential for predicting STP topology behavior and for influencing port roles through path cost tuning or bridge-priority adjustments during campus network design and troubleshooting.
정답:
Explanation:
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.
정답:
Explanation:
The root path cost (RPC) of a switch is the total path cost from that switch to the root bridge along the selected spanning-tree path. Since SW1 is given as the root bridge, its RPC is 0. Each link in the topology has a path cost of 20. To determine SW4’s RPC, you identify the shortest active STP path from SW4 to SW1.
Based on the topology used in the question, SW4 reaches SW1 through a path containing two links. Therefore, the total root path cost is 20 + 20 = 40, which makes option B correct. This is a standard STP calculation. HCIA-Datacom uses RPC as one of the main comparison parameters in root-port election on non-root switches. A lower RPC means a better path toward the root bridge. If multiple candidate ports have the same RPC, the switch then compares the sender’s bridge ID and port ID. This question checks whether the learner understands that RPC is cumulative across the spanning-tree forwarding path and is not simply the cost of a single directly connected link unless the switch is directly attached to the root bridge.

정답:
Explanation:
In STP, the root bridge has all its active ports elected as designated ports on each connected segment. On non-root switches, one port is selected as the root port, and on each LAN segment, one designated port is elected based on the best BPDU. Since SW1 is the root bridge and all links have equal cost, the election depends first on the path cost to the root, then on bridge ID, and then on port ID if needed.
According to the topology, the ports that become designated are GE1/0/2 of SW2, GE1/0/1 of SW2, and GE1/0/3 of SW3, which correspond to option A, B, and C.
Option D is not a designated port in this topology because that segment has another port with a superior BPDU and therefore SW4’s port does not win the designated-port election. HCIA-Datacom emphasizes that designated ports are elected per segment, not per switch, and that every non-root switch must compare received BPDUs to determine root and designated roles. This question tests the ability to apply STP election logic rather than simply memorizing port-role definitions.

정답:
Explanation:
When a switch receives an untagged frame from a user host on an access interface, it associates that frame with the VLAN configured on the interface. In this scenario, PC1 and PC2 are in VLAN 10, and GE1/0/2 is an access interface in VLAN 10. After SW1 receives the frame from PC1, it internally associates the frame with VLAN 10, so option A is correct in the practical VLAN-processing sense used in HCIA-Datacom questions.
When the frame is forwarded out an access interface toward PC2, the switch sends it without a VLAN tag, because end hosts normally do not process 802.1Q tags. Therefore, option D is correct.
Option B is incorrect because both hosts are in the same VLAN and can communicate normally; SW1 does not discard the return traffic for that reason.
Option C is not correct in the standard VLAN switching model used by Huawei training, because the switch performs forwarding based on VLAN membership and internally processes the frame as belonging to VLAN 10. This question mainly checks understanding of access/trunk behavior and tag handling on ingress and egress.
정답:
Explanation:
This statement is false. In an Eth-Trunk operating in LACP mode, if the administrator sets the maximum number of active links to 3 and there is 1 standby link, then when one active member fails, LACP can automatically promote the standby member to active status. The purpose of the standby member is to maintain the configured active-link capacity whenever possible.
Therefore, after one active link fails, the normal expectation is not that the active-link count is reduced from 3 to 2 while the standby link remains idle. Instead, the standby link should participate and replace the failed member, so that the Eth-Trunk continues operating with 3 active links if the standby link and negotiation conditions are normal. This reflects the redundancy and fast recovery capabilities of LACP-based aggregation. HCIA-Datacom highlights that compared with manual mode, LACP provides more intelligent link selection, active/standby management, and fault adaptation. The statement is wrong because it ignores the intended behavior of the standby link in maintaining the number of active forwarding links after a failure.

정답:
Explanation:
For an Eth-Trunk operating in manual load-balancing mode, the logical Eth-Trunk interface can remain Up as long as at least one member link is operational and properly added to the trunk. Therefore, if GE1/0/1 is Up and GE1/0/2 is Down, Eth-Trunk 1 can still stay Up, making option A correct.
Option B is incorrect because member interfaces in a manual Eth-Trunk do not need to be in identical physical states for the trunk itself to remain operational.
Option C is also incorrect because there is no inherent rule here that two-member trunks must have both links active unless a separate minimum-links mechanism has been explicitly configured. No such condition is stated in the question.
Option D is false because one of the key purposes of Eth-Trunk is redundancy; requiring all member interfaces to be Up would defeat that design advantage. HCIA-Datacom teaches that Eth-Trunk enhances link reliability by allowing continued forwarding when part of the bundle fails, provided the trunk still has an active forwarding member.
정답:
Explanation:
In an Eth-Trunk working in manual mode, multiple physical member links are bundled into one logical interface to provide higher bandwidth and link redundancy. If one of four 1 Gbit/s member links fails, the Eth-Trunk does not go down as long as at least one valid member link remains active. Therefore, statement A is correct. Since one link has failed and three member links remain available, the total available bandwidth becomes 3 Gbit/s, so statement B is also correct.
Statement C is incorrect because the traffic originally hashed to the failed link is not permanently stopped. Instead, after the link failure is detected, traffic is redistributed across the remaining active member links according to the trunk load-balancing mechanism.
Statement D is also incorrect because Eth-Trunk provides link-level redundancy. Existing upper-layer sessions such as TCP are not necessarily interrupted and re-established simply because one member link fails. HCIA-Datacom emphasizes that Eth-Trunk improves reliability and bandwidth utilization by allowing traffic to continue across surviving links when a single member fails. This is one of the main advantages of link aggregation in campus and data center switching networks.

정답:
Explanation:
PC1 and PC2 are in different VLANs on SW1, while PC3 is in VLAN 4 on SW2. To allow traffic from VLAN 2 and VLAN 3 users to reach PC3 through the inter-switch link, SW1 must be able to send frames from PC1 and PC2 toward SW2 in a form that SW2 can place into VLAN 4.
Option B is valid because a hybrid interface on SW1 can send frames from VLAN 2 and VLAN 3 untagged, and setting the PVID to VLAN 4 allows untagged inbound frames on the peer side to be associated appropriately when matched with the SW2 configuration.
Option C is also valid because configuring SW2’s GE1/0/3 as a trunk allowing VLAN 4 and setting its PVID to VLAN 4 means untagged frames arriving from SW1 are treated as belonging to VLAN 4 and can then be forwarded to PC3 through its access interface.
Option A is incomplete because only configuring SW2 does not solve the VLAN handling on SW1.
Option D is incorrect because a trunk on SW1 would send VLAN 2 and VLAN 3 frames tagged, which would not match the VLAN 4-only expectation on SW2 in this scenario.

정답:
Explanation:
In TCP, the acknowledgment number indicates the next byte that the receiver expects to receive. In the figure, PC1 sends a TCP segment to PC2 with sequence number = a+22 and payload length = 22 bytes. Since TCP sequence numbers count bytes, the last byte carried in this segment corresponds to sequence number a+43. Therefore, after PC2 successfully receives this data, it sends back an ACK indicating that the next expected byte is a+44.
That is why option B is correct. This is a standard TCP reliability mechanism. TCP does not acknowledge “packets” as units; it acknowledges the byte stream. The ACK number always points to the next byte expected from the peer. The source and destination port numbers identify the session, but the sequence and acknowledgment numbers track ordered delivery. HCIA-Datacom uses this mechanism to explain connection-oriented transport, reliable delivery, retransmission, and traffic control. Understanding how the payload length affects sequence progression is essential when analyzing packet captures and troubleshooting TCP communication problems in enterprise networks.