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 32

Question 310

At fictional Zenith Cloudworks, a network engineer supporting data center interconnects is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-078). The observed network issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. Which next engineering action best addresses the reported problem?

  1. Compare interface IP addresses with enabled OSPF network ranges and area bindings.
  2. Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs.
  3. Configure appropriate ASBR external route summarization while preserving necessary exceptions.
  4. Restore an appropriate area 0 connection or review a supported planned virtual-link design.

Explanation

Correct Answer

B:

The directly responsive action is: Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs. The specific reported fault is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. Confirmation should show: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected. The supporting technical principle is: OSPF detects neighbor failure using liveness Hellos that can be impacted by packet loss.

Incorrect Answers

A:

“Compare interface IP addresses with enabled OSPF network ranges and area bindings” responds to another technical or business failure: OSPF adjacency is stable but a route to a target subnet is absent due to network-statement matching mistakes. That source case depends on: OSPF process activation on interfaces depends on matching enabled prefixes and area configuration. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs” because OSPF detects neighbor failure using liveness Hellos that can be impacted by packet loss.

C:

“Configure appropriate ASBR external route summarization while preserving necessary exceptions” responds to another technical or business failure: An ASBR advertising multiple external subnets floods excessive details because external route aggregation was never applied. That source case depends on: OSPF external aggregation occurs at the appropriate redistribution boundary. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs” because OSPF detects neighbor failure using liveness Hellos that can be impacted by packet loss.

D:

“Restore an appropriate area 0 connection or review a supported planned virtual-link design” responds to another technical or business failure: A branch area has no direct backbone connectivity and operators try to exchange routes between nonbackbone areas directly. That source case depends on: OSPF inter-area routing depends on a contiguous logical backbone architecture. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs” because OSPF detects neighbor failure using liveness Hellos that can be impacted by packet loss.

Question 311

At fictional Zenith Cloudworks, a network engineer supporting data center interconnects is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-078). The observed network issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. Which ongoing preventive or detective control would best reduce recurrence?

  1. Monitor neighbor resets and interface congestion together during incident triage.
  2. Include interface participation checks in subnet migration procedures.
  3. Compare area IDs in both directions during OSPF adjacency acceptance.
  4. Verify neighbor roles before escalating stable 2-Way observations.

Explanation

Correct Answer

A:

The preventive or detective safeguard is: Monitor neighbor resets and interface congestion together during incident triage. This directly addresses the recurring fault: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The corrective action would be: Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs. Success is demonstrated when: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected.

Incorrect Answers

B:

“Include interface participation checks in subnet migration procedures” addresses recurrence of another problem: OSPF adjacency is stable but a route to a target subnet is absent due to network-statement matching mistakes. That problem depends on: The preventive or detective safeguard is: Include interface participation checks in subnet migration procedures. The recurring risk here is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more targeted safeguard is “Monitor neighbor resets and interface congestion together during incident triage” because the preventive or detective safeguard is: Monitor neighbor resets and interface congestion together during incident triage.

C:

“Compare area IDs in both directions during OSPF adjacency acceptance” addresses recurrence of another problem: Two neighboring Huawei routers exchange Hello packets but never become OSPF neighbors because their area identifiers differ. That problem depends on: The preventive or detective safeguard is: Compare area IDs in both directions during OSPF adjacency acceptance. The recurring risk here is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more targeted safeguard is “Monitor neighbor resets and interface congestion together during incident triage” because the preventive or detective safeguard is: Monitor neighbor resets and interface congestion together during incident triage.

D:

“Verify neighbor roles before escalating stable 2-Way observations” addresses recurrence of another problem: Two OSPF routers on a broadcast VLAN stay at 2-Way and an engineer wrongly treats every such neighbor as failed. That problem depends on: The preventive or detective safeguard is: Verify neighbor roles before escalating stable 2-Way observations. The recurring risk here is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more targeted safeguard is “Monitor neighbor resets and interface congestion together during incident triage” because the preventive or detective safeguard is: Monitor neighbor resets and interface congestion together during incident triage.

Question 312

At fictional Zenith Cloudworks, a network engineer supporting data center interconnects is reviewing OSPF area design and link-state convergence during a lab-to-production acceptance (HCIP-H12-821-OSPF-078). The observed network issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. Which observation most directly verifies that the corrective change succeeded?

  1. Adjacency stays stable after underlying packet loss or timer sensitivity is corrected.
  2. Competing ASBR paths select according to the defined external metric type and tie-breaking cost.
  3. Eligible equal-cost next hops appear in the forwarding table and traffic distributes as intended.
  4. The backbone receives the intended external aggregate and required exceptions.

Explanation

Correct Answer

A:

The best verification observation is: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected. It demonstrates the corrective action: Analyze Hello loss, Dead timers, interfaces errors and broadcast congestion rather than changing router IDs. This fits the principle: OSPF detects neighbor failure using liveness Hellos that can be impacted by packet loss. Verify on the actual Huawei platform and network release.

Incorrect Answers

B:

“Competing ASBR paths select according to the defined external metric type and tie-breaking cost” 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: The best verification observation is: Competing ASBR paths select according to the defined external metric type and tie-breaking cost. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Adjacency stays stable after underlying packet loss or timer sensitivity is corrected” because the best verification observation is: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected.

C:

“Eligible equal-cost next hops appear in the forwarding table and traffic distributes as intended” responds to another technical or business failure: Two equal-cost OSPF paths exist but traffic uses only one because the forwarding configuration limits ECMP. That source case depends on: The best verification observation is: Eligible equal-cost next hops appear in the forwarding table and traffic distributes as intended. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Adjacency stays stable after underlying packet loss or timer sensitivity is corrected” because the best verification observation is: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected.

D:

“The backbone receives the intended external aggregate and required exceptions” responds to another technical or business failure: An ASBR advertising multiple external subnets floods excessive details because external route aggregation was never applied. That source case depends on: The best verification observation is: The backbone receives the intended external aggregate and required exceptions. The present issue is: An OSPF neighbor oscillates between Full and Down on a congested shared segment despite correct area IDs. The more direct action is “Adjacency stays stable after underlying packet loss or timer sensitivity is corrected” because the best verification observation is: Adjacency stays stable after underlying packet loss or timer sensitivity is corrected.

Question 313

At fictional Cedar Retail, a network engineer supporting store connectivity is reviewing RSTP, MSTP and switching interconnects during an initial deployment test (HCIP-H12-821-SWITCH-079). The observed network issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. Which observation most directly verifies that the corrective change succeeded?

  1. The trunk participates in correct RSTP convergence and risky edge behavior is blocked.
  2. Correct MST port roles and predictable alternate paths appear after convergence.
  3. One redundant path is blocked as intended and connectivity survives an approved link failure.
  4. MAC learning stabilizes and aggregated uplinks provide the intended redundancy.

Explanation

Correct Answer

A:

The best verification observation is: The trunk participates in correct RSTP convergence and risky edge behavior is blocked. It demonstrates the corrective action: Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy. This fits the principle: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks. Verify on the actual Huawei platform and network release.

Incorrect Answers

B:

“Correct MST port roles and predictable alternate paths appear after convergence” 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: The best verification observation is: Correct MST port roles and predictable alternate paths appear after convergence. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “The trunk participates in correct RSTP convergence and risky edge behavior is blocked” because the best verification observation is: The trunk participates in correct RSTP convergence and risky edge behavior is blocked.

C:

“One redundant path is blocked as intended and connectivity survives an approved link failure” responds to another technical or business failure: An Ethernet campus has a physical loop but engineers disable spanning tree to reduce convergence delay. That source case depends on: The best verification observation is: One redundant path is blocked as intended and connectivity survives an approved link failure. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “The trunk participates in correct RSTP convergence and risky edge behavior is blocked” because the best verification observation is: The trunk participates in correct RSTP convergence and risky edge behavior is blocked.

D:

“MAC learning stabilizes and aggregated uplinks provide the intended redundancy” responds to another technical or business failure: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. That source case depends on: The best verification observation is: MAC learning stabilizes and aggregated uplinks provide the intended redundancy. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “The trunk participates in correct RSTP convergence and risky edge behavior is blocked” because the best verification observation is: The trunk participates in correct RSTP convergence and risky edge behavior is blocked.

Question 314

At fictional Cedar Retail, a network engineer supporting store connectivity is reviewing RSTP, MSTP and switching interconnects during an initial deployment test (HCIP-H12-821-SWITCH-079). The observed network issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. Which ongoing preventive or detective control would best reduce recurrence?

  1. Audit edge-port classification and BPDU protection after topology changes.
  2. Audit access-port PVID assignments after desk and switch moves.
  3. Model port cost and root priorities before production link reweighting.
  4. Check spanning-tree topology and loop guards before adding dual uplinks.

Explanation

Correct Answer

A:

The preventive or detective safeguard is: Audit edge-port classification and BPDU protection after topology changes. This directly addresses the recurring fault: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The corrective action would be: Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy. Success is demonstrated when: The trunk participates in correct RSTP convergence and risky edge behavior is blocked.

Incorrect Answers

B:

“Audit access-port PVID assignments after desk and switch moves” addresses recurrence of another problem: Users from two access VLANs unexpectedly communicate at layer 2 because the same port VLAN was configured on both groups. That problem depends on: The preventive or detective safeguard is: Audit access-port PVID assignments after desk and switch moves. The recurring risk here is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more targeted safeguard is “Audit edge-port classification and BPDU protection after topology changes” because the preventive or detective safeguard is: Audit edge-port classification and BPDU protection after topology changes.

C:

“Model port cost and root priorities before production link reweighting” addresses recurrence of another problem: A switch link that should be an MST root port instead alternates forwarding because path costs differ from the planned design. That problem depends on: The preventive or detective safeguard is: Model port cost and root priorities before production link reweighting. The recurring risk here is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more targeted safeguard is “Audit edge-port classification and BPDU protection after topology changes” because the preventive or detective safeguard is: Audit edge-port classification and BPDU protection after topology changes.

D:

“Check spanning-tree topology and loop guards before adding dual uplinks” addresses recurrence of another problem: An Ethernet campus has a physical loop but engineers disable spanning tree to reduce convergence delay. That problem depends on: The preventive or detective safeguard is: Check spanning-tree topology and loop guards before adding dual uplinks. The recurring risk here is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more targeted safeguard is “Audit edge-port classification and BPDU protection after topology changes” because the preventive or detective safeguard is: Audit edge-port classification and BPDU protection after topology changes.

Question 315

At fictional Cedar Retail, a network engineer supporting store connectivity is reviewing RSTP, MSTP and switching interconnects during an initial deployment test (HCIP-H12-821-SWITCH-079). The observed network issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. Which routing, switching, or network principle best explains the appropriate solution?

  1. Multiple physical switching paths must have coherent loop and aggregation control.
  2. Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.
  3. Stack resiliency requires deliberate master election and partition handling.
  4. MST region membership depends on a consistent configuration digest, not merely a label.

Explanation

Correct Answer

B:

The governing principle is: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks. In this scenario, the appropriate action is: Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy. Valid evidence would show: The trunk participates in correct RSTP convergence and risky edge behavior is blocked.

Incorrect Answers

A:

“Multiple physical switching paths must have coherent loop and aggregation control” responds to another technical or business failure: A downstream aggregation switch sees duplicate MAC flaps after a switch cluster is formed without consistent cross-device link aggregation. That source case depends on: Multiple physical switching paths must have coherent loop and aggregation control. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

C:

“Stack resiliency requires deliberate master election and partition handling” 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: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

D:

“MST region membership depends on a consistent configuration digest, not merely a label” 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: MST region membership depends on a consistent configuration digest, not merely a label. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

Question 316

At fictional Cedar Retail, a network engineer supporting store connectivity is reviewing RSTP, MSTP and switching interconnects during an initial deployment test (HCIP-H12-821-SWITCH-079). The observed network issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. Which next engineering action best addresses the reported problem?

  1. Check split-brain prevention mechanisms and stack topology supported by the platform.
  2. Align region name, revision level and VLAN-instance mappings across the intended domain.
  3. Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy.
  4. Permit the intended tagged VLAN on both sides of the trunk without broadening unrelated VLAN access.

Explanation

Correct Answer

C:

The directly responsive action is: Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy. The specific reported fault is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. Confirmation should show: The trunk participates in correct RSTP convergence and risky edge behavior is blocked. The supporting technical principle is: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

Incorrect Answers

A:

“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: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

B:

“Align region name, revision level and VLAN-instance mappings across the intended domain” 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: MST region membership depends on a consistent configuration digest, not merely a label. The present issue is: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

D:

“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: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. The more direct action is “Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” because Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks.

Question 317

At fictional Northgate Services, a network engineer supporting head-office connectivity is reviewing OSPF area design and link-state convergence during a network troubleshooting drill (HCIP-H12-821-OSPF-080). The observed network issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. Which next engineering action best addresses the reported problem?

  1. Inspect ABR summarization ranges and ensure constituent routes and discard behavior match the design.
  2. Verify equal SPF costs and the route count installed in the FIB before adjusting ECMP support.
  3. Inspect the external LSA forwarding address and the routing table's ability to resolve it.
  4. Inspect external redistribution configuration, LSA Type 5 generation and area restrictions.

Explanation

Correct Answer

C:

The directly responsive action is: Inspect the external LSA forwarding address and the routing table's ability to resolve it. The specific reported fault is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. Confirmation should show: Traffic to the external prefix follows a resolvable advertised forwarding address. The supporting technical principle is: OSPF external route next-hop selection can use the LSA forwarding address when present.

Incorrect Answers

A:

“Inspect ABR summarization ranges and ensure constituent routes and discard behavior match the design” responds to another technical or business failure: An OSPF summary aggregate covers a disconnected subnet and an engineer assumes all summarized addresses have valid next hops. That source case depends on: Route summarization reduces advertisements but can conceal specific reachability failures. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Inspect the external LSA forwarding address and the routing table's ability to resolve it” because OSPF external route next-hop selection can use the LSA forwarding address when present.

B:

“Verify equal SPF costs and the route count installed in the FIB before adjusting ECMP support” responds to another technical or business failure: Two equal-cost OSPF paths exist but traffic uses only one because the forwarding configuration limits ECMP. That source case depends on: Equal-cost shortest paths must also be installed under platform ECMP constraints. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Inspect the external LSA forwarding address and the routing table's ability to resolve it” because OSPF external route next-hop selection can use the LSA forwarding address when present.

D:

“Inspect external redistribution configuration, LSA Type 5 generation and area restrictions” responds to another technical or business failure: An ASBR redistributes a static service subnet but other areas never see its external OSPF destination. That source case depends on: OSPF external routing requires correctly originated and flooded AS-external LSAs. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Inspect the external LSA forwarding address and the routing table's ability to resolve it” because OSPF external route next-hop selection can use the LSA forwarding address when present.

Question 318

At fictional Northgate Services, a network engineer supporting head-office connectivity is reviewing OSPF area design and link-state convergence during a network troubleshooting drill (HCIP-H12-821-OSPF-080). The observed network issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. Which observation most directly verifies that the corrective change succeeded?

  1. The intended default route is available and detailed inter-area summaries are suppressed as designed.
  2. The backbone receives the intended external aggregate and required exceptions.
  3. Traffic to the external prefix follows a resolvable advertised forwarding address.
  4. The local routing decision matches policy without falsely asserting LSDB isolation.

Explanation

Correct Answer

C:

The best verification observation is: Traffic to the external prefix follows a resolvable advertised forwarding address. It demonstrates the corrective action: Inspect the external LSA forwarding address and the routing table's ability to resolve it. This fits the principle: OSPF external route next-hop selection can use the LSA forwarding address when present. Verify on the actual Huawei platform and network release.

Incorrect Answers

A:

“The intended default route is available and detailed inter-area summaries are suppressed as designed” 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: The best verification observation is: The intended default route is available and detailed inter-area summaries are suppressed as designed. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Traffic to the external prefix follows a resolvable advertised forwarding address” because the best verification observation is: Traffic to the external prefix follows a resolvable advertised forwarding address.

B:

“The backbone receives the intended external aggregate and required exceptions” responds to another technical or business failure: An ASBR advertising multiple external subnets floods excessive details because external route aggregation was never applied. That source case depends on: The best verification observation is: The backbone receives the intended external aggregate and required exceptions. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Traffic to the external prefix follows a resolvable advertised forwarding address” because the best verification observation is: Traffic to the external prefix follows a resolvable advertised forwarding address.

D:

“The local routing decision matches policy without falsely asserting LSDB isolation” responds to another technical or business failure: An engineer uses a prefix-filter on one OSPF router expecting to prevent every other router from receiving the LSA. That source case depends on: The best verification observation is: The local routing decision matches policy without falsely asserting LSDB isolation. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “Traffic to the external prefix follows a resolvable advertised forwarding address” because the best verification observation is: Traffic to the external prefix follows a resolvable advertised forwarding address.

Question 319

At fictional Northgate Services, a network engineer supporting head-office connectivity is reviewing OSPF area design and link-state convergence during a network troubleshooting drill (HCIP-H12-821-OSPF-080). The observed network issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. Which routing, switching, or network principle best explains the appropriate solution?

  1. OSPF two-way communication is established only after reciprocal Hello discovery.
  2. OSPF area border routers convey inter-area network reachability using summary information.
  3. OSPF external route next-hop selection can use the LSA forwarding address when present.
  4. OSPF neighbor liveness requires compatible timer parameters on the shared network.

Explanation

Correct Answer

C:

The governing principle is: OSPF external route next-hop selection can use the LSA forwarding address when present. In this scenario, the appropriate action is: Inspect the external LSA forwarding address and the routing table's ability to resolve it. Valid evidence would show: Traffic to the external prefix follows a resolvable advertised forwarding address.

Incorrect Answers

A:

“OSPF two-way communication is established only after reciprocal Hello discovery” responds to another technical or business failure: A transit OSPF link remains in Init because one router never sees its own router ID listed in neighbor Hellos. That source case depends on: OSPF two-way communication is established only after reciprocal Hello discovery. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “OSPF external route next-hop selection can use the LSA forwarding address when present” because OSPF external route next-hop selection can use the LSA forwarding address when present.

B:

“OSPF area border routers convey inter-area network reachability using summary information” responds to another technical or business failure: A backbone-connected router receives intra-area LSAs but remote area destinations never appear in its routing table. That source case depends on: OSPF area border routers convey inter-area network reachability using summary information. The present issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “OSPF external route next-hop selection can use the LSA forwarding address when present” because OSPF external route next-hop selection can use the LSA forwarding address when present.

D:

“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: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more direct action is “OSPF external route next-hop selection can use the LSA forwarding address when present” because OSPF external route next-hop selection can use the LSA forwarding address when present.

Question 320

At fictional Northgate Services, a network engineer supporting head-office connectivity is reviewing OSPF area design and link-state convergence during a network troubleshooting drill (HCIP-H12-821-OSPF-080). The observed network issue is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. Which ongoing preventive or detective control would best reduce recurrence?

  1. Verify external LSA attributes and forwarding resolution on every ASBR redesign.
  2. Capture Hellos from both devices when link-state adjacencies stall.
  3. Test FIB next-hop count and path usage after ECMP policy changes.
  4. Include priority and election expectations in campus VLAN rollout plans.

Explanation

Correct Answer

A:

The preventive or detective safeguard is: Verify external LSA attributes and forwarding resolution on every ASBR redesign. This directly addresses the recurring fault: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The corrective action would be: Inspect the external LSA forwarding address and the routing table's ability to resolve it. Success is demonstrated when: Traffic to the external prefix follows a resolvable advertised forwarding address.

Incorrect Answers

B:

“Capture Hellos from both devices when link-state adjacencies stall” addresses recurrence of another problem: A transit OSPF link remains in Init because one router never sees its own router ID listed in neighbor Hellos. That problem depends on: The preventive or detective safeguard is: Capture Hellos from both devices when link-state adjacencies stall. The recurring risk here is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more targeted safeguard is “Verify external LSA attributes and forwarding resolution on every ASBR redesign” because the preventive or detective safeguard is: Verify external LSA attributes and forwarding resolution on every ASBR redesign.

C:

“Test FIB next-hop count and path usage after ECMP policy changes” addresses recurrence of another problem: Two equal-cost OSPF paths exist but traffic uses only one because the forwarding configuration limits ECMP. That problem depends on: The preventive or detective safeguard is: Test FIB next-hop count and path usage after ECMP policy changes. The recurring risk here is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more targeted safeguard is “Verify external LSA attributes and forwarding resolution on every ASBR redesign” because the preventive or detective safeguard is: Verify external LSA attributes and forwarding resolution on every ASBR redesign.

D:

“Include priority and election expectations in campus VLAN rollout plans” addresses recurrence of another problem: A new router with OSPF priority zero fails to become the designated router even after repeated interface bounces. That problem depends on: The preventive or detective safeguard is: Include priority and election expectations in campus VLAN rollout plans. The recurring risk here is: An external OSPF route prefers the wrong exit because its forwarding address is unreachable or unexpected. The more targeted safeguard is “Verify external LSA attributes and forwarding resolution on every ASBR redesign” because the preventive or detective safeguard is: Verify external LSA attributes and forwarding resolution on every ASBR redesign.

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