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 69

Question 680

At fictional Pinewell Electronics, a network engineer supporting engineering labs is reviewing RSTP, MSTP and switching interconnects during a controlled failover exercise (HCIP-H12-821-SWITCH-170). The observed network issue is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. 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. Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy.
  3. Correct interface PVID or VLAN membership and validate separation with source MAC observations.
  4. Align region name, revision level and VLAN-instance mappings across the intended domain.

Explanation

Correct Answer

D:

The directly responsive action is: Align region name, revision level and VLAN-instance mappings across the intended domain. The specific reported fault is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. Confirmation should show: MST configuration digests agree and switches join the intended common region. The supporting technical principle is: MST region membership depends on a consistent configuration digest, not merely a label.

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: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.

B:

“Remove inappropriate edge-port assumptions and enforce supported BPDU protection policy” responds to another technical or business failure: An engineer places an edge-port setting on a trunk toward another switch and an unexpected BPDU enters the network. That source case depends on: Edge-port optimizations are intended for endpoint-facing links rather than switch-to-switch trunks. The present issue is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.

C:

“Correct interface PVID or VLAN membership and validate separation with source MAC observations” responds to another technical or business failure: Users from two access VLANs unexpectedly communicate at layer 2 because the same port VLAN was configured on both groups. That source case depends on: A switch forwarding domain is determined by VLAN tagging and port membership. The present issue is: MSTP neighbors appear in different regions despite using the same region name because their VLAN mappings differ. The more direct action is “Align region name, revision level and VLAN-instance mappings across the intended domain” because MST region membership depends on a consistent configuration digest, not merely a label.

Question 681

At fictional Riverstone Travel, a network engineer supporting booking offices is reviewing route-policy and traffic-control behavior during a post-maintenance incident review (HCIP-H12-821-POLICY-171). The observed network issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. Which ongoing preventive or detective control would best reduce recurrence?

  1. Validate ACL references and classifier hit counters during service rollout.
  2. Load-test all QoS queues and starvation behavior before enabling strict priority.
  3. Test route-policy node hit outcomes using explicit positive and negative prefixes.
  4. Test both directions and protocol states after changing edge ACLs.

Explanation

Correct Answer

A:

The preventive or detective safeguard is: Validate ACL references and classifier hit counters during service rollout. This directly addresses the recurring fault: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The corrective action would be: Create or fix the supported traffic classifier and verify its attachment in the intended policy. Success is demonstrated when: Test packets hit the defined classifier and intended path decision.

Incorrect Answers

B:

“Load-test all QoS queues and starvation behavior before enabling strict priority” addresses recurrence of another problem: A campus egress port uses weighted scheduling but latency-sensitive voice sits behind large bulk transfers. That problem depends on: The preventive or detective safeguard is: Load-test all QoS queues and starvation behavior before enabling strict priority. The recurring risk here is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more targeted safeguard is “Validate ACL references and classifier hit counters during service rollout” because the preventive or detective safeguard is: Validate ACL references and classifier hit counters during service rollout.

C:

“Test route-policy node hit outcomes using explicit positive and negative prefixes” addresses recurrence of another problem: A Huawei route-policy matches a prefix but the engineer expects every route passing the first node to continue through later nodes. That problem depends on: The preventive or detective safeguard is: Test route-policy node hit outcomes using explicit positive and negative prefixes. The recurring risk here is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more targeted safeguard is “Validate ACL references and classifier hit counters during service rollout” because the preventive or detective safeguard is: Validate ACL references and classifier hit counters during service rollout.

D:

“Test both directions and protocol states after changing edge ACLs” addresses recurrence of another problem: An ACL only denies one direction of a TCP conversation and the security team assumes return packets are automatically blocked. That problem depends on: The preventive or detective safeguard is: Test both directions and protocol states after changing edge ACLs. The recurring risk here is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more targeted safeguard is “Validate ACL references and classifier hit counters during service rollout” because the preventive or detective safeguard is: Validate ACL references and classifier hit counters during service rollout.

Question 682

At fictional Riverstone Travel, a network engineer supporting booking offices is reviewing route-policy and traffic-control behavior during a post-maintenance incident review (HCIP-H12-821-POLICY-171). The observed network issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. Which observation most directly verifies that the corrective change succeeded?

  1. Voice packets hit the intended class and maintain lower delay during controlled congestion.
  2. Traffic tests confirm the authorized request and response directions are treated as designed.
  3. Test packets hit the defined classifier and intended path decision.
  4. Controlled traffic shows desired throughput and measured color actions without unexpected loss.

Explanation

Correct Answer

C:

The best verification observation is: Test packets hit the defined classifier and intended path decision. It demonstrates the corrective action: Create or fix the supported traffic classifier and verify its attachment in the intended policy. This fits the principle: Traffic classification must identify real packets before forwarding or QoS behavior is applied. Verify on the actual Huawei platform and network release.

Incorrect Answers

A:

“Voice packets hit the intended class and maintain lower delay during controlled congestion” responds to another technical or business failure: A classifier matches the wrong VLAN priority bits and high-priority voice is treated as bulk data. That source case depends on: The best verification observation is: Voice packets hit the intended class and maintain lower delay during controlled congestion. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Test packets hit the defined classifier and intended path decision” because the best verification observation is: Test packets hit the defined classifier and intended path decision.

B:

“Traffic tests confirm the authorized request and response directions are treated as designed” responds to another technical or business failure: An ACL only denies one direction of a TCP conversation and the security team assumes return packets are automatically blocked. That source case depends on: The best verification observation is: Traffic tests confirm the authorized request and response directions are treated as designed. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Test packets hit the defined classifier and intended path decision” because the best verification observation is: Test packets hit the defined classifier and intended path decision.

D:

“Controlled traffic shows desired throughput and measured color actions without unexpected loss” responds to another technical or business failure: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. That source case depends on: The best verification observation is: Controlled traffic shows desired throughput and measured color actions without unexpected loss. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Test packets hit the defined classifier and intended path decision” because the best verification observation is: Test packets hit the defined classifier and intended path decision.

Question 683

At fictional Riverstone Travel, a network engineer supporting booking offices is reviewing route-policy and traffic-control behavior during a post-maintenance incident review (HCIP-H12-821-POLICY-171). The observed network issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. Which routing, switching, or network principle best explains the appropriate solution?

  1. Policy routing can override ordinary destination lookup but still requires valid forwarding resolution.
  2. Traffic classification must identify real packets before forwarding or QoS behavior is applied.
  3. Community marking and route-policy enforcement are separate configured stages.
  4. Ordered route policies evaluate match conditions and actions rather than combining all nodes indiscriminately.

Explanation

Correct Answer

B:

The governing principle is: Traffic classification must identify real packets before forwarding or QoS behavior is applied. In this scenario, the appropriate action is: Create or fix the supported traffic classifier and verify its attachment in the intended policy. Valid evidence would show: Test packets hit the defined classifier and intended path decision.

Incorrect Answers

A:

“Policy routing can override ordinary destination lookup but still requires valid forwarding resolution” responds to another technical or business failure: A policy-based routing rule sends traffic toward a next hop that cannot be resolved in the correct VRF. That source case depends on: Policy routing can override ordinary destination lookup but still requires valid forwarding resolution. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Traffic classification must identify real packets before forwarding or QoS behavior is applied” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

C:

“Community marking and route-policy enforcement are separate configured stages” responds to another technical or business failure: An engineer sets a BGP route community but forgets the matching export policy and upstream advertisements are unchanged. That source case depends on: Community marking and route-policy enforcement are separate configured stages. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Traffic classification must identify real packets before forwarding or QoS behavior is applied” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

D:

“Ordered route policies evaluate match conditions and actions rather than combining all nodes indiscriminately” responds to another technical or business failure: A Huawei route-policy matches a prefix but the engineer expects every route passing the first node to continue through later nodes. That source case depends on: Ordered route policies evaluate match conditions and actions rather than combining all nodes indiscriminately. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Traffic classification must identify real packets before forwarding or QoS behavior is applied” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

Question 684

At fictional Riverstone Travel, a network engineer supporting booking offices is reviewing route-policy and traffic-control behavior during a post-maintenance incident review (HCIP-H12-821-POLICY-171). The observed network issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. Which next engineering action best addresses the reported problem?

  1. Apply a scoped redistribution route policy and permit only selected service networks.
  2. Distinguish policing drop or remark actions from shaping that buffers traffic over time.
  3. Analyze bidirectional stateless ACL placement and session-state enforcement differences.
  4. Create or fix the supported traffic classifier and verify its attachment in the intended policy.

Explanation

Correct Answer

D:

The directly responsive action is: Create or fix the supported traffic classifier and verify its attachment in the intended policy. The specific reported fault is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. Confirmation should show: Test packets hit the defined classifier and intended path decision. The supporting technical principle is: Traffic classification must identify real packets before forwarding or QoS behavior is applied.

Incorrect Answers

A:

“Apply a scoped redistribution route policy and permit only selected service networks” responds to another technical or business failure: A site redistributes static routes into OSPF and accidentally advertises a management-only address to every area. That source case depends on: Route redistribution crosses protocol boundaries and needs controlled prefix filtering. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Create or fix the supported traffic classifier and verify its attachment in the intended policy” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

B:

“Distinguish policing drop or remark actions from shaping that buffers traffic over time” responds to another technical or business failure: A Huawei MQC behavior applies policing at an uplink but the operator expects it to buffer all excess traffic. That source case depends on: Traffic policing and traffic shaping handle excess rates differently. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Create or fix the supported traffic classifier and verify its attachment in the intended policy” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

C:

“Analyze bidirectional stateless ACL placement and session-state enforcement differences” responds to another technical or business failure: An ACL only denies one direction of a TCP conversation and the security team assumes return packets are automatically blocked. That source case depends on: Stateless packet filters do not intrinsically track an entire transport session. The present issue is: A routing policy references a nonexistent ACL and traffic is still sent down the default path. The more direct action is “Create or fix the supported traffic classifier and verify its attachment in the intended policy” because Traffic classification must identify real packets before forwarding or QoS behavior is applied.

Question 685

At fictional Oakridge Energy, a network engineer supporting field substations is reviewing IS-IS level-aware topology and database synchronization during an initial deployment test (HCIP-H12-821-ISIS-172). The observed network issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. Which ongoing preventive or detective control would best reduce recurrence?

  1. Check NET area fields before deploying local IS-IS peering.
  2. Verify reachability TLVs and routing policy after interface activation.
  3. Inventory interface and process authentication before planned key rotation.
  4. Test IS-IS PDU forwarding over new Ethernet interconnects.

Explanation

Correct Answer

C:

The preventive or detective safeguard is: Inventory interface and process authentication before planned key rotation. This directly addresses the recurring fault: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The corrective action would be: Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope. Success is demonstrated when: The intended neighbors establish and databases synchronize without authentication errors.

Incorrect Answers

A:

“Check NET area fields before deploying local IS-IS peering” addresses recurrence of another problem: Two Huawei routers share a link but their IS-IS NET addresses use different area identifiers while both are configured as Level 1. That problem depends on: The preventive or detective safeguard is: Check NET area fields before deploying local IS-IS peering. The recurring risk here is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more targeted safeguard is “Inventory interface and process authentication before planned key rotation” because the preventive or detective safeguard is: Inventory interface and process authentication before planned key rotation.

B:

“Verify reachability TLVs and routing policy after interface activation” addresses recurrence of another problem: An IS-IS neighbor forms correctly but the expected IPv4 destination never appears in downstream route tables. That problem depends on: The preventive or detective safeguard is: Verify reachability TLVs and routing policy after interface activation. The recurring risk here is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more targeted safeguard is “Inventory interface and process authentication before planned key rotation” because the preventive or detective safeguard is: Inventory interface and process authentication before planned key rotation.

D:

“Test IS-IS PDU forwarding over new Ethernet interconnects” addresses recurrence of another problem: IS-IS adjacency remains Down when Hello frames are filtered by an intermediate layer-2 device. That problem depends on: The preventive or detective safeguard is: Test IS-IS PDU forwarding over new Ethernet interconnects. The recurring risk here is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more targeted safeguard is “Inventory interface and process authentication before planned key rotation” because the preventive or detective safeguard is: Inventory interface and process authentication before planned key rotation.

Question 686

At fictional Oakridge Energy, a network engineer supporting field substations is reviewing IS-IS level-aware topology and database synchronization during an initial deployment test (HCIP-H12-821-ISIS-172). The observed network issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. Which next engineering action best addresses the reported problem?

  1. Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope.
  2. Examine the L1/L2 router's attached-state behavior and desired inter-area default routing.
  3. Align the intended IS-IS area identifiers or establish a deliberate Level 2 relationship.
  4. Configure the actual point-to-point circuit type and validate neighbor behavior without DIS assumptions.

Explanation

Correct Answer

A:

The directly responsive action is: Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope. The specific reported fault is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. Confirmation should show: The intended neighbors establish and databases synchronize without authentication errors. The supporting technical principle is: IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

Incorrect Answers

B:

“Examine the L1/L2 router's attached-state behavior and desired inter-area default routing” responds to another technical or business failure: An IS-IS Level 1 router gets an unwanted default path after an L1/L2 node reports reachability to other areas. That source case depends on: IS-IS attached-bit behavior can influence Level 1 routing toward other areas. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

C:

“Align the intended IS-IS area identifiers or establish a deliberate Level 2 relationship” responds to another technical or business failure: Two Huawei routers share a link but their IS-IS NET addresses use different area identifiers while both are configured as Level 1. That source case depends on: IS-IS Level 1 adjacency requires compatible area membership. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

D:

“Configure the actual point-to-point circuit type and validate neighbor behavior without DIS assumptions” responds to another technical or business failure: An engineer expects every IS-IS point-to-point interface to elect a LAN designated intermediate system. That source case depends on: IS-IS DIS elections are a broadcast-LAN behavior, not a point-to-point requirement. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

Question 687

At fictional Oakridge Energy, a network engineer supporting field substations is reviewing IS-IS level-aware topology and database synchronization during an initial deployment test (HCIP-H12-821-ISIS-172). The observed network issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. Which observation most directly verifies that the corrective change succeeded?

  1. The intended neighbors establish and databases synchronize without authentication errors.
  2. Neighbor databases show distinct system IDs and consistent LSP origins.
  3. Link-state packets carry supported larger metrics and computed paths match design.
  4. The required IPv4 prefix appears through the intended IS-IS route in the RIB and FIB.

Explanation

Correct Answer

A:

The best verification observation is: The intended neighbors establish and databases synchronize without authentication errors. It demonstrates the corrective action: Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope. This fits the principle: IS-IS routing integrity can require compatible authentication at the relevant PDU scope. Verify on the actual Huawei platform and network release.

Incorrect Answers

B:

“Neighbor databases show distinct system IDs and consistent LSP origins” responds to another technical or business failure: An IS-IS configuration reuses one system ID on two distinct routers and link-state advertisements become ambiguous. That source case depends on: The best verification observation is: Neighbor databases show distinct system IDs and consistent LSP origins. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “The intended neighbors establish and databases synchronize without authentication errors” because the best verification observation is: The intended neighbors establish and databases synchronize without authentication errors.

C:

“Link-state packets carry supported larger metrics and computed paths match design” responds to another technical or business failure: A large IS-IS deployment uses narrow metrics until a new path cost exceeds the legacy representable range. That source case depends on: The best verification observation is: Link-state packets carry supported larger metrics and computed paths match design. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “The intended neighbors establish and databases synchronize without authentication errors” because the best verification observation is: The intended neighbors establish and databases synchronize without authentication errors.

D:

“The required IPv4 prefix appears through the intended IS-IS route in the RIB and FIB” responds to another technical or business failure: An IS-IS neighbor forms correctly but the expected IPv4 destination never appears in downstream route tables. That source case depends on: The best verification observation is: The required IPv4 prefix appears through the intended IS-IS route in the RIB and FIB. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “The intended neighbors establish and databases synchronize without authentication errors” because the best verification observation is: The intended neighbors establish and databases synchronize without authentication errors.

Question 688

At fictional Oakridge Energy, a network engineer supporting field substations is reviewing IS-IS level-aware topology and database synchronization during an initial deployment test (HCIP-H12-821-ISIS-172). The observed network issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. Which routing, switching, or network principle best explains the appropriate solution?

  1. IS-IS identifies routing systems using unique system IDs.
  2. IS-IS LAN DIS behavior differs from OSPF designated-router adjacency handling.
  3. IS-IS exchanges routing PDUs directly over the link rather than using ordinary IP multicast transport.
  4. IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

Explanation

Correct Answer

D:

The governing principle is: IS-IS routing integrity can require compatible authentication at the relevant PDU scope. In this scenario, the appropriate action is: Configure matching supported IS-IS Hello or LSP authentication parameters for the peering scope. Valid evidence would show: The intended neighbors establish and databases synchronize without authentication errors.

Incorrect Answers

A:

“IS-IS identifies routing systems using unique system IDs” responds to another technical or business failure: An IS-IS configuration reuses one system ID on two distinct routers and link-state advertisements become ambiguous. That source case depends on: IS-IS identifies routing systems using unique system IDs. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “IS-IS routing integrity can require compatible authentication at the relevant PDU scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

B:

“IS-IS LAN DIS behavior differs from OSPF designated-router adjacency handling” responds to another technical or business failure: An IS-IS router is elected designated intermediate system on an Ethernet segment but an engineer calls it an OSPF DR. That source case depends on: IS-IS LAN DIS behavior differs from OSPF designated-router adjacency handling. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “IS-IS routing integrity can require compatible authentication at the relevant PDU scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

C:

“IS-IS exchanges routing PDUs directly over the link rather than using ordinary IP multicast transport” responds to another technical or business failure: IS-IS adjacency remains Down when Hello frames are filtered by an intermediate layer-2 device. That source case depends on: IS-IS exchanges routing PDUs directly over the link rather than using ordinary IP multicast transport. The present issue is: An IS-IS adjacency repeatedly resets because neighboring devices use incompatible authentication settings. The more direct action is “IS-IS routing integrity can require compatible authentication at the relevant PDU scope” because IS-IS routing integrity can require compatible authentication at the relevant PDU scope.

Question 689

At fictional Ironbridge Utilities, a network engineer supporting branch services is reviewing VRRP, BFD and redundancy design during an intersite service activation (HCIP-H12-821-RELIABILITY-173). The observed network issue is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. Which ongoing preventive or detective control would best reduce recurrence?

  1. Record preemption and delay values for each redundant gateway group.
  2. Check host ARP or ND observations before and after gateway takeover.
  3. Test BFD-down consequences under a controlled far-end path outage.
  4. Simulate uplink failures instead of only shutting down the client-facing VLAN.

Explanation

Correct Answer

C:

The preventive or detective safeguard is: Test BFD-down consequences under a controlled far-end path outage. This directly addresses the recurring fault: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The corrective action would be: Establish BFD monitoring over the intended adjacency and link its state to routing as supported. Success is demonstrated when: The routing session or route promptly reacts when BFD detects forwarding failure.

Incorrect Answers

A:

“Record preemption and delay values for each redundant gateway group” addresses recurrence of another problem: A maintenance engineer expects a higher-priority VRRP router to take back Master instantly although preemption is disabled. That problem depends on: The preventive or detective safeguard is: Record preemption and delay values for each redundant gateway group. The recurring risk here is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more targeted safeguard is “Test BFD-down consequences under a controlled far-end path outage” because the preventive or detective safeguard is: Test BFD-down consequences under a controlled far-end path outage.

B:

“Check host ARP or ND observations before and after gateway takeover” addresses recurrence of another problem: Two edge routers use independent VRRP groups with conflicting virtual MAC expectations and clients intermittently lose connectivity. That problem depends on: The preventive or detective safeguard is: Check host ARP or ND observations before and after gateway takeover. The recurring risk here is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more targeted safeguard is “Test BFD-down consequences under a controlled far-end path outage” because the preventive or detective safeguard is: Test BFD-down consequences under a controlled far-end path outage.

D:

“Simulate uplink failures instead of only shutting down the client-facing VLAN” addresses recurrence of another problem: A VRRP standby router never becomes master after the preferred uplink fails because only the physical LAN interface remains Up. That problem depends on: The preventive or detective safeguard is: Simulate uplink failures instead of only shutting down the client-facing VLAN. The recurring risk here is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more targeted safeguard is “Test BFD-down consequences under a controlled far-end path outage” because the preventive or detective safeguard is: Test BFD-down consequences under a controlled far-end path outage.

Question 690

At fictional Ironbridge Utilities, a network engineer supporting branch services is reviewing VRRP, BFD and redundancy design during an intersite service activation (HCIP-H12-821-RELIABILITY-173). The observed network issue is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. Which routing, switching, or network principle best explains the appropriate solution?

  1. Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers.
  2. Network reliability depends on eliminating shared risks, not only duplicating network devices.
  3. Fast fault detection is ineffective without a genuinely independent recovery path.
  4. Hardware redundancy only improves availability when dependent paths are also redundant.

Explanation

Correct Answer

A:

The governing principle is: Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers. In this scenario, the appropriate action is: Establish BFD monitoring over the intended adjacency and link its state to routing as supported. Valid evidence would show: The routing session or route promptly reacts when BFD detects forwarding failure.

Incorrect Answers

B:

“Network reliability depends on eliminating shared risks, not only duplicating network devices” responds to another technical or business failure: A campus design has redundant routers and switches but both power feeds terminate on one supply circuit. That source case depends on: Network reliability depends on eliminating shared risks, not only duplicating network devices. The present issue is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more direct action is “Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers” because Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers.

C:

“Fast fault detection is ineffective without a genuinely independent recovery path” responds to another technical or business failure: An interface failure is detected rapidly by BFD but the backup route points to the same failed upstream dependency. That source case depends on: Fast fault detection is ineffective without a genuinely independent recovery path. The present issue is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more direct action is “Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers” because Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers.

D:

“Hardware redundancy only improves availability when dependent paths are also redundant” responds to another technical or business failure: A switch stack offers redundant members but its sole uplink attaches to one device and remains a failure point. That source case depends on: Hardware redundancy only improves availability when dependent paths are also redundant. The present issue is: A router forwards to a remote next hop even after its BGP peer's far-end forwarding path is lost, causing slow detection. The more direct action is “Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers” because Bidirectional Forwarding Detection provides fast failure detection independent of routing protocol timers.

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