McAfee Secure

Huawei H12-811 Bundle

Exam Code: H12-811

Exam Name HCIA-Datacom V1.0

Certification Provider: Huawei

Corresponding Certification: HCIA-Datacom

Huawei H12-811 Bundle $25.00

100% Huawei H12-811 Guaranteed Success With Testking Training Materials

Get Real H12-811 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    H12-811 Questions & Answers

    445 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual H12-811 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • H12-811 Video Course

    H12-811 Training Course

    40 Video Lectures

    H12-811 Video Course is developed by Huawei Professionals to help you pass the H12-811 exam.

    Description

    This course will improve your knowledge and skills required to pass HCIA-Datacom V1.0 exam.

HCIA-Datacom V1.0 (H12-811) Practice Tests

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
Total Cost: $164.98
Bundle Price: $139.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    445 Questions

    $124.99
  • H12-811 Video Course

    Training Course

    40 Video Lectures

    $39.99

Huawei H12-811 Practice Test 28

Question 270

During an independent network handover at the Canyon Village branch of Granite Bioinformatics, the monitored service is campus identity services for clients in 10.63.28.0/24; incident reference is DC-8552. The on-duty analyst documents this symptom before proposing any configuration: Traffic to a single data-center subnet follows a VPN route even though a general default route points to the internet. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at Canyon Village: Track retransmission spikes, MTU-related ICMP messages and tunnel overhead changes.
  2. For a monitoring check at Canyon Village: Monitor route insertion/deletion and path selection for important destination prefixes.
  3. For a monitoring check at Canyon Village: Track active route source, preference and backup transition evidence.
  4. For a monitoring check at Canyon Village: Monitor ND failures, duplicate address detection and blocked critical ICMPv6 types.

Answer and explanations

A.

Track retransmission spikes, MTU-related ICMP messages and tunnel overhead changes. This alternative addresses a different issue (ipv4 mtu and fragmentation symptoms). The reported case is: During an independent network handover at the Canyon Village branch of Granite Bioinformatics, the monitored service is campus identity services for clients in 10.63.28.0/24; incident reference is DC-8552. The decisive distinction is: Monitor route insertion/deletion and path selection for important destination prefixes.

B.

The decisive evidence is: During an independent network handover at the Canyon Village branch of Granite Bioinformatics, the monitored service is campus identity services for clients in 10.63.28.0/24; incident reference is DC-8552. Monitor route insertion/deletion and path selection for important destination prefixes.

C.

Track active route source, preference and backup transition evidence. The observed condition is: During an independent network handover at the Canyon Village branch of Granite Bioinformatics, the monitored service is campus identity services for clients in 10.63.28.0/24; incident reference is DC-8552. This alternative addresses a different issue (administrative route preference). The decisive distinction is: Monitor route insertion/deletion and path selection for important destination prefixes.

D.

This alternative addresses a different issue (ipv6 neighbor discovery). The option would address: Monitor ND failures, duplicate address detection and blocked critical ICMPv6 types. The scenario instead reports: During an independent network handover at the Canyon Village branch of Granite Bioinformatics, the monitored service is campus identity services for clients in 10.63.28.0/24; incident reference is DC-8552.

Question 271

At Mosaic Postal Union in Sage Point, engineers maintain a small Huawei VRP-based wired/WLAN campus for retail billing, with client segment 10.41.16.0/24. An approved maintenance window follows change DC-8564. The change team records this observable condition: A static route is installed with a next hop that does not resolve on the intended egress segment. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. What explanation best fits the observed network failure, rather than a merely possible separate fault?

  1. For DC-8564 at Sage Point, the technical interpretation is: The connected prefix is not being originated into the intended OSPF area or route filters suppress it.
  2. For DC-8564 at Sage Point, the technical interpretation is: Forward and return routes are asymmetric across stateful inspection points.
  3. For DC-8564 at Sage Point, the technical interpretation is: The configured static next hop is not reachable through its expected local forwarding adjacency.
  4. For DC-8564 at Sage Point, the technical interpretation is: IPv6 hosts commonly use the router's link-local address as the default next hop learned from Router Advertisements.

Answer and explanations

A.

This alternative addresses a different issue (ospf advertisement missing). The connected prefix is not being originated into the intended OSPF area or route filters suppress it. In the reported case: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The configured static next hop is not reachable through its expected local forwarding adjacency.

B.

Forward and return routes are asymmetric across stateful inspection points. The observed condition is: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (return path symmetry). The decisive distinction is: The configured static next hop is not reachable through its expected local forwarding adjacency.

C.

The configured static next hop is not reachable through its expected local forwarding adjacency. The reported evidence is: A static route is installed with a next hop that does not resolve on the intended egress segment. Confirm the affected layer or service before applying a configuration change.

D.

IPv6 hosts commonly use the router's link-local address as the default next hop learned from Router Advertisements. This alternative addresses a different issue (ipv6 link-local gateway). The reported case is: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The configured static next hop is not reachable through its expected local forwarding adjacency.

Question 272

At Mosaic Postal Union in Sage Point, engineers maintain a small Huawei VRP-based wired/WLAN campus for retail billing, with client segment 10.41.16.0/24. An approved maintenance window follows change DC-8564. The change team records this observable condition: A static route is installed with a next hop that does not resolve on the intended egress segment. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which precise corrective change addresses the demonstrated failure with minimal unrelated disruption?

  1. For a controlled repair of retail billing in Sage Point: Examine both directions of routing and session policy and align the required return path through the authorized stateful boundary.
  2. For a controlled repair of retail billing in Sage Point: Permit required ICMPv6 Neighbor Solicitation and Advertisement messages within the intended local segment.
  3. For a controlled repair of retail billing in Sage Point: Validate hello/dead detection or supported fast failure sensing against the change standard, then verify alternate next-hop availability.
  4. For a controlled repair of retail billing in Sage Point: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability.

Answer and explanations

A.

For a controlled repair of retail billing in Sage Point: Examine both directions of routing and session policy and align the required return path through the authorized stateful boundary. The observed condition is: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (return path symmetry). The decisive distinction is: For a controlled repair of retail billing in Sage Point: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability.

B.

This alternative addresses a different issue (ipv6 neighbor discovery). The option would address: For a controlled repair of retail billing in Sage Point: Permit required ICMPv6 Neighbor Solicitation and Advertisement messages within the intended local segment. The scenario instead reports: A static route is installed with a next hop that does not resolve on the intended egress segment.

C.

For a controlled repair of retail billing in Sage Point: Validate hello/dead detection or supported fast failure sensing against the change standard, then verify alternate next-hop availability. This alternative addresses a different issue (ospf route withdrawal after failure). The reported case is: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: For a controlled repair of retail billing in Sage Point: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability.

D.

A static route is installed with a next hop that does not resolve on the intended egress segment. That points to this explanation: For a controlled repair of retail billing in Sage Point: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability. Validate it through the controlled case because A configured route line is not proof that a forwarding adjacency or remote return route exists.

Question 273

At Mosaic Postal Union in Sage Point, engineers maintain a small Huawei VRP-based wired/WLAN campus for retail billing, with client segment 10.41.16.0/24. An approved maintenance window follows change DC-8564. The change team records this observable condition: A static route is installed with a next hop that does not resolve on the intended egress segment. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which acceptance evidence most directly demonstrates that the proposed targeted correction works?

  1. For acceptance review of Sage Point change DC-8564: The static route resolves to the intended egress and a remote test succeeds with return routing verified.
  2. For acceptance review of Sage Point change DC-8564: The host has an IPv6 default route using the router's link-local next hop and reaches an allowed remote prefix.
  3. For acceptance review of Sage Point change DC-8564: Large controlled application transfers complete without repeated black-hole retransmissions at the tested path size.
  4. For acceptance review of Sage Point change DC-8564: The chosen route matches the intended preference and a simulated next-hop failure follows an approved backup.

Answer and explanations

A.

The static route resolves to the intended egress and a remote test succeeds with return routing verified. This addresses the decisive observation: A static route is installed with a next hop that does not resolve on the intended egress segment.

B.

The host has an IPv6 default route using the router's link-local next hop and reaches an allowed remote prefix. This alternative addresses a different issue (would not prove the reported issue was corrected). The reported case is: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The static route resolves to the intended egress and a remote test succeeds with return routing verified.

C.

This alternative addresses a different issue (would not prove the reported issue was corrected). Large controlled application transfers complete without repeated black-hole retransmissions at the tested path size. In the reported case: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The static route resolves to the intended egress and a remote test succeeds with return routing verified.

D.

The chosen route matches the intended preference and a simulated next-hop failure follows an approved backup. The observed condition is: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (would not prove the reported issue was corrected). The decisive distinction is: The static route resolves to the intended egress and a remote test succeeds with return routing verified.

Question 274

At Mosaic Postal Union in Sage Point, engineers maintain a small Huawei VRP-based wired/WLAN campus for retail billing, with client segment 10.41.16.0/24. An approved maintenance window follows change DC-8564. The change team records this observable condition: A static route is installed with a next hop that does not resolve on the intended egress segment. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which remaining limitation should the engineer explicitly record even after the targeted repair?

  1. For the Sage Point network design record: Prefix length changes may disrupt SLAAC and existing sessions and require careful staged migration.
  2. For the Sage Point network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.
  3. For the Sage Point network design record: A valid gateway cannot compensate for missing return routes or remote service failures.
  4. For the Sage Point network design record: A complete adjacency does not imply automatic advertisement of every local interface.

Answer and explanations

A.

For the Sage Point network design record: Prefix length changes may disrupt SLAAC and existing sessions and require careful staged migration. This alternative addresses a different issue (ipv6 prefix length error). The reported case is: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: For the Sage Point network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

B.

The decisive evidence is: A static route is installed with a next hop that does not resolve on the intended egress segment. For the Sage Point network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

C.

For the Sage Point network design record: A valid gateway cannot compensate for missing return routes or remote service failures. The observed condition is: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (incorrect default gateway). The decisive distinction is: For the Sage Point network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

D.

This alternative addresses a different issue (ospf advertisement missing). The option would address: For the Sage Point network design record: A complete adjacency does not imply automatic advertisement of every local interface. The scenario instead reports: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: For the Sage Point network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

Question 275

At Mosaic Postal Union in Sage Point, engineers maintain a small Huawei VRP-based wired/WLAN campus for retail billing, with client segment 10.41.16.0/24. An approved maintenance window follows change DC-8564. The change team records this observable condition: A static route is installed with a next hop that does not resolve on the intended egress segment. They can run a controlled laboratory replay and must leave unrelated campuses and production authentication policies unchanged. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at Sage Point: Track retransmission spikes, MTU-related ICMP messages and tunnel overhead changes.
  2. For a monitoring check at Sage Point: Track active route source, preference and backup transition evidence.
  3. For a monitoring check at Sage Point: Monitor next-hop tracking, neighbor resolution and static route usability.
  4. For a monitoring check at Sage Point: Monitor ND failures, duplicate address detection and blocked critical ICMPv6 types.

Answer and explanations

A.

This alternative addresses a different issue (ipv4 mtu and fragmentation symptoms). Track retransmission spikes, MTU-related ICMP messages and tunnel overhead changes. In the reported case: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

B.

Track active route source, preference and backup transition evidence. The observed condition is: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (administrative route preference). The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

C.

Monitor next-hop tracking, neighbor resolution and static route usability. The reported evidence is: A static route is installed with a next hop that does not resolve on the intended egress segment.

D.

Monitor ND failures, duplicate address detection and blocked critical ICMPv6 types. This alternative addresses a different issue (ipv6 neighbor discovery). The reported case is: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

Question 276

During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. What explanation best fits the observed network failure, rather than a merely possible separate fault?

  1. For DC-8569 at Fox River, the technical interpretation is: Equal-cost multipath usually selects an individual flow's next hop by hashing rather than duplicating every packet.
  2. For DC-8569 at Fox River, the technical interpretation is: A misconfigured on-link route or mask makes the router treat a remote IP as locally attached.
  3. For DC-8569 at Fox River, the technical interpretation is: ICMPv6 neighbor discovery must function for same-link IPv6 address-to-MAC resolution.
  4. For DC-8569 at Fox River, the technical interpretation is: The configured static next hop is not reachable through its expected local forwarding adjacency.

Answer and explanations

A.

Equal-cost multipath usually selects an individual flow's next hop by hashing rather than duplicating every packet. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (ecmp next-hop behavior). The decisive distinction is: The configured static next hop is not reachable through its expected local forwarding adjacency.

B.

This alternative addresses a different issue (ipv4 arp versus routing decision). The option would address: A misconfigured on-link route or mask makes the router treat a remote IP as locally attached. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

C.

ICMPv6 neighbor discovery must function for same-link IPv6 address-to-MAC resolution. This alternative addresses a different issue (ipv6 neighbor discovery). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The configured static next hop is not reachable through its expected local forwarding adjacency.

D.

The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. That points to this explanation: The configured static next hop is not reachable through its expected local forwarding adjacency. Confirm the affected layer or service before applying a configuration change.

Question 277

During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which precise corrective change addresses the demonstrated failure with minimal unrelated disruption?

  1. For a controlled repair of public ticketing in Fox River: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability.
  2. For a controlled repair of public ticketing in Fox River: Correct the connected prefix or route next hop and verify FIB resolution for the distant destination.
  3. For a controlled repair of public ticketing in Fox River: Align the link's documented IPv6 prefix and RA settings while preserving addressing plan and SLAAC constraints.
  4. For a controlled repair of public ticketing in Fox River: Calculate the network and broadcast boundaries from the documented mask and correct the address or use a router for off-link traffic.

Answer and explanations

A.

For a controlled repair of public ticketing in Fox River: Correct next-hop addressing or the supporting connected path, then confirm recursive resolution and interface reachability. This addresses the decisive observation: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. Validate it through the controlled case because A configured route line is not proof that a forwarding adjacency or remote return route exists.

B.

For a controlled repair of public ticketing in Fox River: Correct the connected prefix or route next hop and verify FIB resolution for the distant destination. This alternative addresses a different issue (ipv4 arp versus routing decision). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

C.

This alternative addresses a different issue (ipv6 prefix length error). For a controlled repair of public ticketing in Fox River: Align the link's documented IPv6 prefix and RA settings while preserving addressing plan and SLAAC constraints. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

D.

For a controlled repair of public ticketing in Fox River: Calculate the network and broadcast boundaries from the documented mask and correct the address or use a router for off-link traffic. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (cidr subnet boundary).

Question 278

During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which acceptance evidence most directly demonstrates that the proposed targeted correction works?

  1. For acceptance review of Fox River change DC-8569: The neighbor cache reaches a reachable state and IPv6 unicast exchange succeeds locally.
  2. For acceptance review of Fox River change DC-8569: The static route resolves to the intended egress and a remote test succeeds with return routing verified.
  3. For acceptance review of Fox River change DC-8569: After a supervised link failure the stale route withdraws and permitted traffic uses the expected backup within the measured objective.
  4. For acceptance review of Fox River change DC-8569: Both routers report stable Full adjacency and exchange the expected LSAs.

Answer and explanations

A.

The neighbor cache reaches a reachable state and IPv6 unicast exchange succeeds locally. This alternative addresses a different issue (would not prove the reported issue was corrected). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: The static route resolves to the intended egress and a remote test succeeds with return routing verified.

B.

The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The static route resolves to the intended egress and a remote test succeeds with return routing verified.

C.

After a supervised link failure the stale route withdraws and permitted traffic uses the expected backup within the measured objective. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (would not prove the reported issue was corrected).

D.

This alternative addresses a different issue (would not prove the reported issue was corrected). The option would address: Both routers report stable Full adjacency and exchange the expected LSAs. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

Question 279

During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which remaining limitation should the engineer explicitly record even after the targeted repair?

  1. For the Fox River network design record: An IPv6 next hop can be reachable while destination return routing is still missing.
  2. For the Fox River network design record: Route preference values compare candidates for the same prefix, not replace longest-prefix logic.
  3. For the Fox River network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.
  4. For the Fox River network design record: ECMP provides path diversity but not guaranteed 50:50 bandwidth per single application session.

Answer and explanations

A.

This alternative addresses a different issue (ipv6 static route next hop). For the Fox River network design record: An IPv6 next hop can be reachable while destination return routing is still missing. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

B.

For the Fox River network design record: Route preference values compare candidates for the same prefix, not replace longest-prefix logic. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (longest prefix route selection). The decisive distinction is: For the Fox River network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

C.

For the Fox River network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists. The reported evidence is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment.

D.

For the Fox River network design record: ECMP provides path diversity but not guaranteed 50:50 bandwidth per single application session. This alternative addresses a different issue (ecmp next-hop behavior). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: For the Fox River network design record: A configured route line is not proof that a forwarding adjacency or remote return route exists.

Question 280

During an independent network handover at the Fox River branch of Fjord City Library, the monitored service is public ticketing for clients in 172.20.54.0/24; incident reference is DC-8569. The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The branch requires an auditable explanation, a narrowly staged change, and a rollback plan that preserves its working services. Which ongoing operational check is most relevant to recognizing recurrence of this failure?

  1. For a monitoring check at Fox River: Measure convergence intervals and route flap frequency during fault drills.
  2. For a monitoring check at Fox River: Alert on adjacency down events and area configuration drift.
  3. For a monitoring check at Fox River: Audit RA prefix information and host neighbor/route tables after IPv6 changes.
  4. For a monitoring check at Fox River: Monitor next-hop tracking, neighbor resolution and static route usability.

Answer and explanations

A.

Measure convergence intervals and route flap frequency during fault drills. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. This alternative addresses a different issue (ospf route withdrawal after failure). The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

B.

This alternative addresses a different issue (ospf neighbor area mismatch). The option would address: Alert on adjacency down events and area configuration drift. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

C.

Audit RA prefix information and host neighbor/route tables after IPv6 changes. This alternative addresses a different issue (ipv6 prefix length error). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. The decisive distinction is: Monitor next-hop tracking, neighbor resolution and static route usability.

D.

The on-duty analyst documents this symptom before proposing any configuration: A static route is installed with a next hop that does not resolve on the intended egress segment. That points to this explanation: Monitor next-hop tracking, neighbor resolution and static route usability.