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 23

Question 220

During an independent network handover at the Coastal Haven branch of Harbor East Foods, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8467. The on-duty analyst documents this symptom before proposing any configuration: Two guest devices on separate access ports in the same VLAN can contact each other despite a policy requiring client separation. 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 Coastal Haven: Track trunk VLAN membership, VLAN pruning events and voice endpoint connectivity after changes.
  2. For a monitoring check at Coastal Haven: Review root and port-role state and controlled failover tests.
  3. For a monitoring check at Coastal Haven: Audit native/PVID mismatches and unexpected source MAC learning in management VLANs.
  4. For a monitoring check at Coastal Haven: Run scheduled same-VLAN isolation probes and watch unexpected east-west traffic.

Answer and explanations

A.

Track trunk VLAN membership, VLAN pruning events and voice endpoint connectivity after changes. The observed condition is: During an independent network handover at the Coastal Haven branch of Harbor East Foods, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8467. This alternative addresses a different issue (trunk allowed vlans). The decisive distinction is: Run scheduled same-VLAN isolation probes and watch unexpected east-west traffic.

B.

This alternative addresses a different issue (stp blocking redundant link). The option would address: Review root and port-role state and controlled failover tests. The scenario instead reports: During an independent network handover at the Coastal Haven branch of Harbor East Foods, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8467.

C.

Audit native/PVID mismatches and unexpected source MAC learning in management VLANs. This alternative addresses a different issue (untagged trunk pvid). The reported case is: During an independent network handover at the Coastal Haven branch of Harbor East Foods, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8467. The decisive distinction is: Run scheduled same-VLAN isolation probes and watch unexpected east-west traffic.

D.

During an independent network handover at the Coastal Haven branch of Harbor East Foods, the monitored service is laboratory instrument upload for clients in 172.18.14.0/24; incident reference is DC-8467. That points to this explanation: Run scheduled same-VLAN isolation probes and watch unexpected east-west traffic.

Question 221

At North Basin Transit in Raven Valley, engineers maintain a small Huawei VRP-based wired/WLAN campus for facility access control, with client segment 192.168.84.0/24. An approved maintenance window follows change DC-8479. The change team records this observable condition: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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-8479 at Raven Valley, the technical interpretation is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.
  2. For DC-8479 at Raven Valley, the technical interpretation is: The edge-facing interface is treated as a switch-to-switch topology port.
  3. For DC-8479 at Raven Valley, the technical interpretation is: The member attributes or LACP partner parameters are inconsistent with the intended aggregation.
  4. For DC-8479 at Raven Valley, the technical interpretation is: The VLAN needs an operational Layer 3 gateway and appropriate inter-VLAN routes.

Answer and explanations

A.

Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes. This addresses the decisive observation: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. Confirm the affected layer or service before applying a configuration change.

B.

The edge-facing interface is treated as a switch-to-switch topology port. This alternative addresses a different issue (rstp edge port classification). The reported case is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.

C.

This alternative addresses a different issue (lacp member inconsistency). The member attributes or LACP partner parameters are inconsistent with the intended aggregation. In the reported case: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.

D.

The VLAN needs an operational Layer 3 gateway and appropriate inter-VLAN routes. The observed condition is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (vlan interface gateway). The decisive distinction is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.

Question 222

At North Basin Transit in Raven Valley, engineers maintain a small Huawei VRP-based wired/WLAN campus for facility access control, with client segment 192.168.84.0/24. An approved maintenance window follows change DC-8479. The change team records this observable condition: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 facility access control in Raven Valley: Align allowed member speed/duplex, aggregation mode, peer identity and LACP parameters on both ends.
  2. For a controlled repair of facility access control in Raven Valley: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls.
  3. For a controlled repair of facility access control in Raven Valley: Enable supported port isolation or an equivalent guest client separation policy on appropriate access ports.
  4. For a controlled repair of facility access control in Raven Valley: Align the interface's PVID with the approved untagged VLAN mapping on both interconnected devices where required.

Answer and explanations

A.

For a controlled repair of facility access control in Raven Valley: Align allowed member speed/duplex, aggregation mode, peer identity and LACP parameters on both ends. This alternative addresses a different issue (lacp member inconsistency). The reported case is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: For a controlled repair of facility access control in Raven Valley: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls.

B.

The decisive evidence is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. For a controlled repair of facility access control in Raven Valley: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls. Validate it through the controlled case because Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

C.

For a controlled repair of facility access control in Raven Valley: Enable supported port isolation or an equivalent guest client separation policy on appropriate access ports. The observed condition is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (port isolation). The decisive distinction is: For a controlled repair of facility access control in Raven Valley: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls.

D.

This alternative addresses a different issue (untagged trunk pvid). The option would address: For a controlled repair of facility access control in Raven Valley: Align the interface's PVID with the approved untagged VLAN mapping on both interconnected devices where required. The scenario instead reports: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

Question 223

At North Basin Transit in Raven Valley, engineers maintain a small Huawei VRP-based wired/WLAN campus for facility access control, with client segment 192.168.84.0/24. An approved maintenance window follows change DC-8479. The change team records this observable condition: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 Raven Valley change DC-8479: A VLAN 40 host ARPs for its gateway and reaches an allowed remote VLAN through the routing point.
  2. For acceptance review of Raven Valley change DC-8479: Frames tagged for the voice VLAN traverse the link and a test phone reaches its intended voice service.
  3. For acceptance review of Raven Valley change DC-8479: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.
  4. For acceptance review of Raven Valley change DC-8479: A supervised primary-link failure activates the alternate forwarding path without a loop.

Answer and explanations

A.

This alternative addresses a different issue (would not prove the reported issue was corrected). A VLAN 40 host ARPs for its gateway and reaches an allowed remote VLAN through the routing point. In the reported case: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

B.

Frames tagged for the voice VLAN traverse the link and a test phone reaches its intended voice service. The observed condition is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (would not prove the reported issue was corrected). The decisive distinction is: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

C.

CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption. The reported evidence is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

D.

A supervised primary-link failure activates the alternate forwarding path without a loop. This alternative addresses a different issue (would not prove the reported issue was corrected). The reported case is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

Question 224

At North Basin Transit in Raven Valley, engineers maintain a small Huawei VRP-based wired/WLAN campus for facility access control, with client segment 192.168.84.0/24. An approved maintenance window follows change DC-8479. The change team records this observable condition: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 Raven Valley network design record: Reallowing every VLAN indiscriminately increases unnecessary broadcast reach and security exposure.
  2. For the Raven Valley network design record: Unknown unicast behavior is not identical to IP multicast membership or broadcast forwarding.
  3. For the Raven Valley network design record: A VLAN interface does not imply permission for unrestricted cross-VLAN communication.
  4. For the Raven Valley network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

Answer and explanations

A.

For the Raven Valley network design record: Reallowing every VLAN indiscriminately increases unnecessary broadcast reach and security exposure. The observed condition is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (vlan pruning during migration). The decisive distinction is: For the Raven Valley network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

B.

This alternative addresses a different issue (unknown unicast flooding). The option would address: For the Raven Valley network design record: Unknown unicast behavior is not identical to IP multicast membership or broadcast forwarding. The scenario instead reports: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

C.

For the Raven Valley network design record: A VLAN interface does not imply permission for unrestricted cross-VLAN communication. This alternative addresses a different issue (vlan interface gateway). The reported case is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: For the Raven Valley network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

D.

An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. That points to this explanation: For the Raven Valley network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

Question 225

At North Basin Transit in Raven Valley, engineers maintain a small Huawei VRP-based wired/WLAN campus for facility access control, with client segment 192.168.84.0/24. An approved maintenance window follows change DC-8479. The change team records this observable condition: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 Raven Valley: Trend CRC, discards, optical power and link renegotiations.
  2. For a monitoring check at Raven Valley: Track trunk VLAN membership, VLAN pruning events and voice endpoint connectivity after changes.
  3. For a monitoring check at Raven Valley: Review root and port-role state and controlled failover tests.
  4. For a monitoring check at Raven Valley: Audit native/PVID mismatches and unexpected source MAC learning in management VLANs.

Answer and explanations

A.

Trend CRC, discards, optical power and link renegotiations. This addresses the decisive observation: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

B.

Track trunk VLAN membership, VLAN pruning events and voice endpoint connectivity after changes. This alternative addresses a different issue (trunk allowed vlans). The reported case is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Trend CRC, discards, optical power and link renegotiations.

C.

This alternative addresses a different issue (stp blocking redundant link). Review root and port-role state and controlled failover tests. In the reported case: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Trend CRC, discards, optical power and link renegotiations.

D.

Audit native/PVID mismatches and unexpected source MAC learning in management VLANs. The observed condition is: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (untagged trunk pvid). The decisive distinction is: Trend CRC, discards, optical power and link renegotiations.

Question 226

During an independent network handover at the River Mill branch of Union Hill Development, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8484. The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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-8484 at River Mill, the technical interpretation is: The user port requires enforcement against unexpected bridge protocol data units.
  2. For DC-8484 at River Mill, the technical interpretation is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.
  3. For DC-8484 at River Mill, the technical interpretation is: Hash-based aggregation generally keeps one conversation on one physical member rather than summing bandwidth for a single flow.
  4. For DC-8484 at River Mill, the technical interpretation is: Simple VLAN membership alone permits same-segment L2 reachability unless isolation is enforced.

Answer and explanations

A.

The user port requires enforcement against unexpected bridge protocol data units. This alternative addresses a different issue (bpdu protection on user access). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.

B.

The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes. Confirm the affected layer or service before applying a configuration change.

C.

Hash-based aggregation generally keeps one conversation on one physical member rather than summing bandwidth for a single flow. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (per-flow aggregation hashing). The decisive distinction is: Physical-layer corruption or cabling/optics problems must be checked before VLAN or routing changes.

D.

This alternative addresses a different issue (port isolation). The option would address: Simple VLAN membership alone permits same-segment L2 reachability unless isolation is enforced. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

Question 227

During an independent network handover at the River Mill branch of Union Hill Development, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8484. The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 retail billing in River Mill: Validate the bundle and distribute multiple independent flows when assessing aggregate capacity.
  2. For a controlled repair of retail billing in River Mill: Restore the approved VLAN on only the necessary uplink path and reconcile endpoint-to-trunk dependency records.
  3. For a controlled repair of retail billing in River Mill: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls.
  4. For a controlled repair of retail billing in River Mill: Verify link activity and MAC learning on the correct ingress port, then age or refresh the stale table entry safely.

Answer and explanations

A.

This alternative addresses a different issue (per-flow aggregation hashing). For a controlled repair of retail billing in River Mill: Validate the bundle and distribute multiple independent flows when assessing aggregate capacity. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

B.

For a controlled repair of retail billing in River Mill: Restore the approved VLAN on only the necessary uplink path and reconcile endpoint-to-trunk dependency records. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (vlan pruning during migration).

C.

For a controlled repair of retail billing in River Mill: Test the patch path, transceivers and speed/duplex negotiation under maintenance controls. The reported evidence is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. Validate it through the controlled case because Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

D.

For a controlled repair of retail billing in River Mill: Verify link activity and MAC learning on the correct ingress port, then age or refresh the stale table entry safely. This alternative addresses a different issue (mac address learning and forwarding). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

Question 228

During an independent network handover at the River Mill branch of Union Hill Development, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8484. The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 River Mill change DC-8484: Two guest clients cannot directly exchange L2 traffic while retaining required upstream gateway access.
  2. For acceptance review of River Mill change DC-8484: An untagged test frame lands in the intended VLAN and no management frame leaks into the user broadcast domain.
  3. For acceptance review of River Mill change DC-8484: Normal endpoint link transitions do not cause avoidable campus-wide reconvergence and received BPDUs trigger protection.
  4. For acceptance review of River Mill change DC-8484: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

Answer and explanations

A.

Two guest clients cannot directly exchange L2 traffic while retaining required upstream gateway access. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (would not prove the reported issue was corrected). The decisive distinction is: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

B.

This alternative addresses a different issue (would not prove the reported issue was corrected). The option would address: An untagged test frame lands in the intended VLAN and no management frame leaks into the user broadcast domain. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

C.

Normal endpoint link transitions do not cause avoidable campus-wide reconvergence and received BPDUs trigger protection. 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: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

D.

The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. That points to this explanation: CRC/error counters stop increasing and a controlled throughput test completes without repeated frame corruption.

Question 229

During an independent network handover at the River Mill branch of Union Hill Development, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8484. The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 River Mill network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.
  2. For the River Mill network design record: Correct access VLAN membership does not create a routed path or bypass network access controls.
  3. For the River Mill network design record: Storm control can limit damage but does not substitute for a loop-free topology.
  4. For the River Mill network design record: Port isolation is not a replacement for routed firewall policy to other subnets.

Answer and explanations

A.

For the River Mill network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation. This addresses the decisive observation: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

B.

For the River Mill network design record: Correct access VLAN membership does not create a routed path or bypass network access controls. This alternative addresses a different issue (access port vlan membership). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

C.

This alternative addresses a different issue (broadcast storm and loop). For the River Mill network design record: Storm control can limit damage but does not substitute for a loop-free topology. In the reported case: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.

D.

For the River Mill network design record: Port isolation is not a replacement for routed firewall policy to other subnets. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (port isolation). The decisive distinction is: For the River Mill network design record: Clearing counters hides historic evidence and a healthy link light cannot prove error-free operation.

Question 230

During an independent network handover at the River Mill branch of Union Hill Development, the monitored service is retail billing for clients in 10.102.20.0/24; incident reference is DC-8484. The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. 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 River Mill: Audit native/PVID mismatches and unexpected source MAC learning in management VLANs.
  2. For a monitoring check at River Mill: Trend CRC, discards, optical power and link renegotiations.
  3. For a monitoring check at River Mill: Monitor edge-port BPDU violations and topology change counters.
  4. For a monitoring check at River Mill: Observe MAC move frequency and address-table stability during migrations.

Answer and explanations

A.

Audit native/PVID mismatches and unexpected source MAC learning in management VLANs. This alternative addresses a different issue (untagged trunk pvid). The reported case is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. The decisive distinction is: Trend CRC, discards, optical power and link renegotiations.

B.

The decisive evidence is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. Trend CRC, discards, optical power and link renegotiations.

C.

Monitor edge-port BPDU violations and topology change counters. The observed condition is: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct. This alternative addresses a different issue (rstp edge port classification). The decisive distinction is: Trend CRC, discards, optical power and link renegotiations.

D.

This alternative addresses a different issue (mac address learning and forwarding). The option would address: Observe MAC move frequency and address-table stability during migrations. The scenario instead reports: The on-duty analyst documents this symptom before proposing any configuration: An uplink reports CRC errors and intermittent throughput drops although its VLAN and spanning-tree roles are correct.