McAfee Secure

Exam Code: H12-821

Exam Name: HCIP-Datacom-Core Technology V1.0

Certification Provider: Huawei

Huawei H12-821 Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

471 Questions & Answers with Testing Engine

"HCIP-Datacom-Core Technology V1.0 Exam", also known as H12-821 exam, is a Huawei certification exam.

Pass your tests with the always up-to-date H12-821 Exam Engine. Your H12-821 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Huawei H12-821 Practice Test 56

Question 550

At fictional Lakeshore Finance, a network engineer supporting transaction systems is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-138). The observed network issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. Which routing, switching, or network principle best explains the appropriate solution?

  1. OSPF E1 and E2 external cost calculations treat internal path costs differently.
  2. OSPF neighbor liveness requires compatible timer parameters on the shared network.
  3. OSPF interface network type affects neighbor handling and designated router behavior.
  4. Totally stubby area behavior reduces inter-area summary visibility beyond ordinary stub restrictions.

Explanation

Correct Answer

C:

The governing principle is: OSPF interface network type affects neighbor handling and designated router behavior. In this scenario, the appropriate action is: Align compatible OSPF network types and validate hello and DR behavior for the actual media. Valid evidence would show: Neighbors form a stable adjacency without an unintended DR election on the point-to-point link.

Incorrect Answers

A:

“OSPF E1 and E2 external cost calculations treat internal path costs differently” responds to another technical or business failure: An engineer mistakes an OSPF external Type 2 metric for a path whose internal costs are always added to its advertised value. That source case depends on: OSPF E1 and E2 external cost calculations treat internal path costs differently. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.

B:

“OSPF neighbor liveness requires compatible timer parameters on the shared network” responds to another technical or business failure: Routers have the same network prefix but one side uses a different OSPF Hello interval on an Ethernet segment. That source case depends on: OSPF neighbor liveness requires compatible timer parameters on the shared network. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.

D:

“Totally stubby area behavior reduces inter-area summary visibility beyond ordinary stub restrictions” responds to another technical or business failure: An OSPF totally stubby area receives unwanted detailed inter-area routes after only one router's configuration changes. That source case depends on: Totally stubby area behavior reduces inter-area summary visibility beyond ordinary stub restrictions. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “OSPF interface network type affects neighbor handling and designated router behavior” because OSPF interface network type affects neighbor handling and designated router behavior.

Question 551

At fictional Lakeshore Finance, a network engineer supporting transaction systems is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-138). The observed network issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. Which next engineering action best addresses the reported problem?

  1. Plan a controlled maintenance event and understand the nonpreemptive DR election behavior.
  2. Align interface OSPF area assignment on both ends without changing unrelated adjacencies.
  3. Check NSSA Type 7 origination and the ABR's permitted Type 7 to Type 5 translation.
  4. Align compatible OSPF network types and validate hello and DR behavior for the actual media.

Explanation

Correct Answer

D:

The directly responsive action is: Align compatible OSPF network types and validate hello and DR behavior for the actual media. The specific reported fault is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. Confirmation should show: Neighbors form a stable adjacency without an unintended DR election on the point-to-point link. The supporting technical principle is: OSPF interface network type affects neighbor handling and designated router behavior.

Incorrect Answers

A:

“Plan a controlled maintenance event and understand the nonpreemptive DR election behavior” responds to another technical or business failure: An OSPF DR election change unexpectedly disrupts traffic because an engineer assumes elections are always preemptive. That source case depends on: Existing OSPF designated-router elections generally do not preempt solely because a higher priority joins. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “Align compatible OSPF network types and validate hello and DR behavior for the actual media” because OSPF interface network type affects neighbor handling and designated router behavior.

B:

“Align interface OSPF area assignment on both ends without changing unrelated adjacencies” responds to another technical or business failure: Two neighboring Huawei routers exchange Hello packets but never become OSPF neighbors because their area identifiers differ. That source case depends on: OSPF neighbor formation requires matching area configuration on shared links. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “Align compatible OSPF network types and validate hello and DR behavior for the actual media” because OSPF interface network type affects neighbor handling and designated router behavior.

C:

“Check NSSA Type 7 origination and the ABR's permitted Type 7 to Type 5 translation” responds to another technical or business failure: An NSSA branch redistributes a local service prefix but the backbone never receives the route. That source case depends on: NSSA external routes use Type 7 LSAs internally and can be translated at an ABR. The present issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more direct action is “Align compatible OSPF network types and validate hello and DR behavior for the actual media” because OSPF interface network type affects neighbor handling and designated router behavior.

Question 552

At fictional Lakeshore Finance, a network engineer supporting transaction systems is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-138). The observed network issue is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. Which ongoing preventive or detective control would best reduce recurrence?

  1. Record and compare OSPF interface authentication settings before key rotation.
  2. Document interface network types and verify after link-layer changes.
  3. Verify external LSA attributes and forwarding resolution on every ASBR redesign.
  4. Test cost changes with an explicit before-and-after route and path table.

Explanation

Correct Answer

B:

The preventive or detective safeguard is: Document interface network types and verify after link-layer changes. This directly addresses the recurring fault: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The corrective action would be: Align compatible OSPF network types and validate hello and DR behavior for the actual media. Success is demonstrated when: Neighbors form a stable adjacency without an unintended DR election on the point-to-point link.

Incorrect Answers

A:

“Record and compare OSPF interface authentication settings before key rotation” addresses recurrence of another problem: An OSPF adjacency repeatedly fails due to mismatched authentication algorithms after a maintenance window. That problem depends on: The preventive or detective safeguard is: Record and compare OSPF interface authentication settings before key rotation. The recurring risk here is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more targeted safeguard is “Document interface network types and verify after link-layer changes” because the preventive or detective safeguard is: Document interface network types and verify after link-layer changes.

C:

“Verify external LSA attributes and forwarding resolution on every ASBR redesign” addresses recurrence of another problem: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. That problem depends on: The preventive or detective safeguard is: Verify external LSA attributes and forwarding resolution on every ASBR redesign. The recurring risk here is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more targeted safeguard is “Document interface network types and verify after link-layer changes” because the preventive or detective safeguard is: Document interface network types and verify after link-layer changes.

D:

“Test cost changes with an explicit before-and-after route and path table” addresses recurrence of another problem: An operator raises OSPF interface cost expecting every transit path to become more attractive. That problem depends on: The preventive or detective safeguard is: Test cost changes with an explicit before-and-after route and path table. The recurring risk here is: Two OSPF devices on a point-to-point fiber cannot build an adjacency because their interface network types differ. The more targeted safeguard is “Document interface network types and verify after link-layer changes” because the preventive or detective safeguard is: Document interface network types and verify after link-layer changes.

Question 553

At fictional Elmstone Transit, a network engineer supporting operations terminals is reviewing BGP routing, path attributes and EVPN exchange during a planned network scaling change (HCIP-H12-821-BGP-139). The observed network issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. Which observation most directly verifies that the corrective change succeeded?

  1. Both routers reach Established using the planned loopback source and destination.
  2. Session state advances through connection and OPEN exchange before prefix import is analyzed.
  3. Correct tenant MAC routes appear only in the intended bridge domain.
  4. The aggregate is advertised with working forwarding paths to all intended destinations.

Explanation

Correct Answer

B:

The best verification observation is: Session state advances through connection and OPEN exchange before prefix import is analyzed. It demonstrates the corrective action: Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first. This fits the principle: BGP FSM states distinguish session formation failures from routing-update processing. Verify on the actual Huawei platform and network release.

Incorrect Answers

A:

“Both routers reach Established using the planned loopback source and destination” responds to another technical or business failure: An iBGP adjacency to peer loopbacks fails because one side sends TCP from the physical interface address. That source case depends on: The best verification observation is: Both routers reach Established using the planned loopback source and destination. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Session state advances through connection and OPEN exchange before prefix import is analyzed” because the best verification observation is: Session state advances through connection and OPEN exchange before prefix import is analyzed.

C:

“Correct tenant MAC routes appear only in the intended bridge domain” responds to another technical or business failure: A fabric advertises a host MAC under the wrong VNI and an engineer changes the global underlay OSPF cost to compensate. That source case depends on: The best verification observation is: Correct tenant MAC routes appear only in the intended bridge domain. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Session state advances through connection and OPEN exchange before prefix import is analyzed” because the best verification observation is: Session state advances through connection and OPEN exchange before prefix import is analyzed.

D:

“The aggregate is advertised with working forwarding paths to all intended destinations” responds to another technical or business failure: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. That source case depends on: The best verification observation is: The aggregate is advertised with working forwarding paths to all intended destinations. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Session state advances through connection and OPEN exchange before prefix import is analyzed” because the best verification observation is: Session state advances through connection and OPEN exchange before prefix import is analyzed.

Question 554

At fictional Elmstone Transit, a network engineer supporting operations terminals is reviewing BGP routing, path attributes and EVPN exchange during a planned network scaling change (HCIP-H12-821-BGP-139). The observed network issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. Which ongoing preventive or detective control would best reduce recurrence?

  1. Verify BGP best-route and FIB installation separately after enabling multipath.
  2. Record BGP state transitions and transport errors in new-neighbor tests.
  3. Confirm which BGP attributes the upstream provider honors before changing announcements.
  4. Review match ordering with representative permitted and denied prefixes.

Explanation

Correct Answer

B:

The preventive or detective safeguard is: Record BGP state transitions and transport errors in new-neighbor tests. This directly addresses the recurring fault: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The corrective action would be: Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first. Success is demonstrated when: Session state advances through connection and OPEN exchange before prefix import is analyzed.

Incorrect Answers

A:

“Verify BGP best-route and FIB installation separately after enabling multipath” addresses recurrence of another problem: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. That problem depends on: The preventive or detective safeguard is: Verify BGP best-route and FIB installation separately after enabling multipath. The recurring risk here is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more targeted safeguard is “Record BGP state transitions and transport errors in new-neighbor tests” because the preventive or detective safeguard is: Record BGP state transitions and transport errors in new-neighbor tests.

C:

“Confirm which BGP attributes the upstream provider honors before changing announcements” addresses recurrence of another problem: An edge router tries to influence its upstream provider's path selection by assigning LOCAL_PREF on an eBGP announcement. That problem depends on: The preventive or detective safeguard is: Confirm which BGP attributes the upstream provider honors before changing announcements. The recurring risk here is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more targeted safeguard is “Record BGP state transitions and transport errors in new-neighbor tests” because the preventive or detective safeguard is: Record BGP state transitions and transport errors in new-neighbor tests.

D:

“Review match ordering with representative permitted and denied prefixes” addresses recurrence of another problem: A route-policy applies an import deny clause before the intended permit and unexpectedly drops every received route. That problem depends on: The preventive or detective safeguard is: Review match ordering with representative permitted and denied prefixes. The recurring risk here is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more targeted safeguard is “Record BGP state transitions and transport errors in new-neighbor tests” because the preventive or detective safeguard is: Record BGP state transitions and transport errors in new-neighbor tests.

Question 555

At fictional Elmstone Transit, a network engineer supporting operations terminals is reviewing BGP routing, path attributes and EVPN exchange during a planned network scaling change (HCIP-H12-821-BGP-139). The observed network issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. Which next engineering action best addresses the reported problem?

  1. Choose the correct EVPN route type for IP prefix routing versus bridged endpoint MAC reachability.
  2. Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first.
  3. Narrow permitted prefix filters to the approved route set and confirm the aggregate's precise prefix length.
  4. Repair reflection topology rather than disabling safety controls for the problematic route.

Explanation

Correct Answer

B:

The directly responsive action is: Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first. The specific reported fault is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. Confirmation should show: Session state advances through connection and OPEN exchange before prefix import is analyzed. The supporting technical principle is: BGP FSM states distinguish session formation failures from routing-update processing.

Incorrect Answers

A:

“Choose the correct EVPN route type for IP prefix routing versus bridged endpoint MAC reachability” responds to another technical or business failure: An engineer expects BGP EVPN Type 5 IP prefixes to replace all MAC learning requirements for a layer-2 stretch. That source case depends on: EVPN route types distinguish IP-prefix advertisement from MAC/IP advertisement. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first” because BGP FSM states distinguish session formation failures from routing-update processing.

C:

“Narrow permitted prefix filters to the approved route set and confirm the aggregate's precise prefix length” responds to another technical or business failure: An administrator applies an export prefix list at the BGP border but mistakenly filters all networks including a critical aggregate. That source case depends on: BGP outbound prefix filtering controls which NLRI are advertised to external peers. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first” because BGP FSM states distinguish session formation failures from routing-update processing.

D:

“Repair reflection topology rather than disabling safety controls for the problematic route” responds to another technical or business failure: A route reflector receives an update whose ORIGINATOR_ID equals its own router identifier and a technician wants to override the loop check. That source case depends on: BGP ORIGINATOR_ID is a loop-prevention mechanism in reflected routing. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first” because BGP FSM states distinguish session formation failures from routing-update processing.

Question 556

At fictional Elmstone Transit, a network engineer supporting operations terminals is reviewing BGP routing, path attributes and EVPN exchange during a planned network scaling change (HCIP-H12-821-BGP-139). The observed network issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. Which routing, switching, or network principle best explains the appropriate solution?

  1. BGP can retain multiple paths while installing selected forwarding entries under platform rules.
  2. BGP route viability depends on recursive reachability of the next-hop attribute.
  3. BGP aggregation must be consistent with actual routed component reachability.
  4. BGP FSM states distinguish session formation failures from routing-update processing.

Explanation

Correct Answer

D:

The governing principle is: BGP FSM states distinguish session formation failures from routing-update processing. In this scenario, the appropriate action is: Follow BGP finite-state-machine stages and establish routing, TCP and neighbor prerequisites first. Valid evidence would show: Session state advances through connection and OPEN exchange before prefix import is analyzed.

Incorrect Answers

A:

“BGP can retain multiple paths while installing selected forwarding entries under platform rules” responds to another technical or business failure: A BGP router receives multiple paths and engineering assumes all alternate paths must be installed for forwarding regardless of BGP capability. That source case depends on: BGP can retain multiple paths while installing selected forwarding entries under platform rules. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “BGP FSM states distinguish session formation failures from routing-update processing” because BGP FSM states distinguish session formation failures from routing-update processing.

B:

“BGP route viability depends on recursive reachability of the next-hop attribute” responds to another technical or business failure: A received BGP prefix has a NEXT_HOP attribute unreachable inside the receiving autonomous system. That source case depends on: BGP route viability depends on recursive reachability of the next-hop attribute. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “BGP FSM states distinguish session formation failures from routing-update processing” because BGP FSM states distinguish session formation failures from routing-update processing.

C:

“BGP aggregation must be consistent with actual routed component reachability” responds to another technical or business failure: An operator creates a BGP aggregate but traffic is black-holed because no specific reachable next hop supports it. That source case depends on: BGP aggregation must be consistent with actual routed component reachability. The present issue is: BGP stays in Idle after a new neighbor is configured and operators troubleshoot route policies instead of local interface reachability. The more direct action is “BGP FSM states distinguish session formation failures from routing-update processing” because BGP FSM states distinguish session formation failures from routing-update processing.

Question 557

At fictional Vista Research, a network engineer supporting lab network slices is reviewing RSTP, MSTP and switching interconnects during a network troubleshooting drill (HCIP-H12-821-SWITCH-140). The observed network issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Which observation most directly verifies that the corrective change succeeded?

  1. Layer-2 forwarding and the layer-3 active gateway each follow their own intended owner.
  2. MST configuration digests agree and switches join the intended common region.
  3. MAC learning stabilizes and aggregated uplinks provide the intended redundancy.
  4. Frames from the new VLAN reach its authorized gateway and other VLANs remain isolated.

Explanation

Correct Answer

C:

The best verification observation is: MAC learning stabilizes and aggregated uplinks provide the intended redundancy. It demonstrates the corrective action: Use a supported cluster and link aggregation design instead of uncontrolled duplicate links. This fits the principle: Multiple physical switching paths must have coherent loop and aggregation control. Verify on the actual Huawei platform and network release.

Incorrect Answers

A:

“Layer-2 forwarding and the layer-3 active gateway each follow their own intended owner” responds to another technical or business failure: A team expects MSTP instance root selection to affect layer-3 inter-VLAN gateway ownership automatically. That source case depends on: The best verification observation is: Layer-2 forwarding and the layer-3 active gateway each follow their own intended owner. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “MAC learning stabilizes and aggregated uplinks provide the intended redundancy” because the best verification observation is: MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

B:

“MST configuration digests agree and switches join the intended common region” responds to another technical or business failure: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. That source case depends on: The best verification observation is: MST configuration digests agree and switches join the intended common region. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “MAC learning stabilizes and aggregated uplinks provide the intended redundancy” because the best verification observation is: MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

D:

“Frames from the new VLAN reach its authorized gateway and other VLANs remain isolated” responds to another technical or business failure: A technician adds a new VLAN but leaves it out of the allowed trunk list between access and aggregation switches. That source case depends on: The best verification observation is: Frames from the new VLAN reach its authorized gateway and other VLANs remain isolated. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “MAC learning stabilizes and aggregated uplinks provide the intended redundancy” because the best verification observation is: MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

Question 558

At fictional Vista Research, a network engineer supporting lab network slices is reviewing RSTP, MSTP and switching interconnects during a network troubleshooting drill (HCIP-H12-821-SWITCH-140). The observed network issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Which ongoing preventive or detective control would best reduce recurrence?

  1. Verify cross-member link aggregation and MAC movement under failover.
  2. Check trunk VLAN allowlists during new segment deployment.
  3. Run region consistency checks after any VLAN migration.
  4. Document root-primary and backup priorities for all switching domains.

Explanation

Correct Answer

A:

The preventive or detective safeguard is: Verify cross-member link aggregation and MAC movement under failover. This directly addresses the recurring fault: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The corrective action would be: Use a supported cluster and link aggregation design instead of uncontrolled duplicate links. Success is demonstrated when: MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

Incorrect Answers

B:

“Check trunk VLAN allowlists during new segment deployment” addresses recurrence of another problem: A technician adds a new VLAN but leaves it out of the allowed trunk list between access and aggregation switches. That problem depends on: The preventive or detective safeguard is: Check trunk VLAN allowlists during new segment deployment. The recurring risk here is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more targeted safeguard is “Verify cross-member link aggregation and MAC movement under failover” because the preventive or detective safeguard is: Verify cross-member link aggregation and MAC movement under failover.

C:

“Run region consistency checks after any VLAN migration” addresses recurrence of another problem: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. That problem depends on: The preventive or detective safeguard is: Run region consistency checks after any VLAN migration. The recurring risk here is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more targeted safeguard is “Verify cross-member link aggregation and MAC movement under failover” because the preventive or detective safeguard is: Verify cross-member link aggregation and MAC movement under failover.

D:

“Document root-primary and backup priorities for all switching domains” addresses recurrence of another problem: Two switches disagree about the RSTP root bridge and forwarding follows a low-capacity distribution switch. That problem depends on: The preventive or detective safeguard is: Document root-primary and backup priorities for all switching domains. The recurring risk here is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more targeted safeguard is “Verify cross-member link aggregation and MAC movement under failover” because the preventive or detective safeguard is: Verify cross-member link aggregation and MAC movement under failover.

Question 559

At fictional Vista Research, a network engineer supporting lab network slices is reviewing RSTP, MSTP and switching interconnects during a network troubleshooting drill (HCIP-H12-821-SWITCH-140). The observed network issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Which routing, switching, or network principle best explains the appropriate solution?

  1. Spanning-tree selected paths depend on cumulative root cost and bridge identifiers.
  2. Multiple physical switching paths must have coherent loop and aggregation control.
  3. Spanning tree and default-gateway failover are independent control mechanisms.
  4. Switch stacking creates a logical control relationship from compatible physical members.

Explanation

Correct Answer

B:

The governing principle is: Multiple physical switching paths must have coherent loop and aggregation control. In this scenario, the appropriate action is: Use a supported cluster and link aggregation design instead of uncontrolled duplicate links. Valid evidence would show: MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

Incorrect Answers

A:

“Spanning-tree selected paths depend on cumulative root cost and bridge identifiers” responds to another technical or business failure: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. That source case depends on: Spanning-tree selected paths depend on cumulative root cost and bridge identifiers. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Multiple physical switching paths must have coherent loop and aggregation control” because Multiple physical switching paths must have coherent loop and aggregation control.

C:

“Spanning tree and default-gateway failover are independent control mechanisms” responds to another technical or business failure: A team expects MSTP instance root selection to affect layer-3 inter-VLAN gateway ownership automatically. That source case depends on: Spanning tree and default-gateway failover are independent control mechanisms. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Multiple physical switching paths must have coherent loop and aggregation control” because Multiple physical switching paths must have coherent loop and aggregation control.

D:

“Switch stacking creates a logical control relationship from compatible physical members” responds to another technical or business failure: Two switches are configured for stacking but fail to form one logical unit due to incompatible member identifiers. That source case depends on: Switch stacking creates a logical control relationship from compatible physical members. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Multiple physical switching paths must have coherent loop and aggregation control” because Multiple physical switching paths must have coherent loop and aggregation control.

Question 560

At fictional Vista Research, a network engineer supporting lab network slices is reviewing RSTP, MSTP and switching interconnects during a network troubleshooting drill (HCIP-H12-821-SWITCH-140). The observed network issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Which next engineering action best addresses the reported problem?

  1. Permit the intended tagged VLAN on both sides of the trunk without broadening unrelated VLAN access.
  2. Use a supported cluster and link aggregation design instead of uncontrolled duplicate links.
  3. Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links.
  4. Check split-brain prevention mechanisms and stack topology supported by the platform.

Explanation

Correct Answer

B:

The directly responsive action is: Use a supported cluster and link aggregation design instead of uncontrolled duplicate links. The specific reported fault is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. Confirmation should show: MAC learning stabilizes and aggregated uplinks provide the intended redundancy. The supporting technical principle is: Multiple physical switching paths must have coherent loop and aggregation control.

Incorrect Answers

A:

“Permit the intended tagged VLAN on both sides of the trunk without broadening unrelated VLAN access” responds to another technical or business failure: A technician adds a new VLAN but leaves it out of the allowed trunk list between access and aggregation switches. That source case depends on: VLAN trunking requires explicit compatible tagging and allowed membership. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.

C:

“Inspect effective port costs, bridge IDs and region boundaries before adjusting designated links” responds to another technical or business failure: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. That source case depends on: Spanning-tree selected paths depend on cumulative root cost and bridge identifiers. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.

D:

“Check split-brain prevention mechanisms and stack topology supported by the platform” responds to another technical or business failure: An iStack link fails and an engineer assumes the remaining members will always preserve a single partition-free control plane. That source case depends on: Stack resiliency requires deliberate master election and partition handling. The present issue is: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. The more direct action is “Use a supported cluster and link aggregation design instead of uncontrolled duplicate links” because Multiple physical switching paths must have coherent loop and aggregation control.

HCIP-Datacom-Core Technology V1.0 (H12-821) Practice Tests