Practice Exams:

HP HPE6-A86 Dumps

EXAM: HPE Network Switching Associate
Verified By Experts
Premium Bundle
$19.99
$54.99 $74.98

HPE6-A86 Premium Bundle


  • Premium File 108 Questions & Answers
  • Study Guide 427 Pages

HP HPE6-A86 Practice Test 31

Question 300

A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags What observable postchange evidence would most directly demonstrate that the fix worked?

  1. Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles
  2. Trace a tagged test frame for each required VLAN and verify per-VLAN MAC learning on the far switch
  3. Confirm the expected LLDP neighbor IDs and local-port identities on both ends before changing VLANs
  4. Verify FULL neighbor state where expected and confirm remote prefixes appear through the intended interface

Answer & Explanations

Correct answer: B

A.

This observation would verify a different remedy: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. That remedy applies to: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The present condition is: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. To assess it, check: Trace a tagged test frame for each required VLAN and verify per-VLAN MAC learning on the far switch.

B.

Trace a tagged test frame for each required VLAN and verify per-VLAN MAC learning on the far switch. This check directly tests: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments. The underlying behavior is: A VLAN can cross an inter-switch trunk only when forwarding and tagging are consistent through the actual path. The case is: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags.

C.

This observation would verify a different remedy: Enable authorized LLDP discovery and compare reported neighbor chassis and interface identifiers against the wiring plan. That remedy applies to: A university data closet contains several unlabeled cross-connects after a contractor rewired the patch field. The present condition is: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. To assess it, check: Trace a tagged test frame for each required VLAN and verify per-VLAN MAC learning on the far switch.

D.

This observation would verify a different remedy: Match routed link subnet, OSPF area, authentication and hello/dead parameters across intended neighbors. That remedy applies to: A regional airport turns up a backup routed interconnect but its OSPF peer stays in INIT. The present condition is: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. To assess it, check: Trace a tagged test frame for each required VLAN and verify per-VLAN MAC learning on the far switch.

Question 301

A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags The team wants to implement an approved fix while avoiding a regression. Which proposed shortcut would most directly undermine a safe correction for this particular case?

  1. Permit every available VLAN on every trunk instead of scoping to required segments
  2. Let a newly installed edge switch with an accidental low bridge ID become the root
  3. Assume interface labels are accurate without validating the cable's real far-end neighbor
  4. Troubleshoot missing OSPF routes by increasing link bandwidth without checking adjacency state

Answer & Explanations

Correct answer: A

A.

Permit every available VLAN on every trunk instead of scoping to required segments. This shortcut is unsafe for: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. The resulting failure can be: Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks. The safer response is: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

B.

This proposed shortcut concerns a separate case: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The risk in this question concerns: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. Here the unsafe shortcut is: Permit every available VLAN on every trunk instead of scoping to required segments. Use this response instead: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

C.

This proposed shortcut concerns a separate case: A university data closet contains several unlabeled cross-connects after a contractor rewired the patch field. The risk in this question concerns: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. Here the unsafe shortcut is: Permit every available VLAN on every trunk instead of scoping to required segments. Use this response instead: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

D.

This proposed shortcut concerns a separate case: A regional airport turns up a backup routed interconnect but its OSPF peer stays in INIT. The risk in this question concerns: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. Here the unsafe shortcut is: Permit every available VLAN on every trunk instead of scoping to required segments. Use this response instead: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

Question 302

A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags Suppose the team instead chooses this shortcut: Permit every available VLAN on every trunk instead of scoping to required segments. If the team instead takes the following shortcut, what specific outcome is most likely?

  1. Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly
  2. Engineers apply changes to the wrong physical link and create unexpected reachability loss
  3. Neighbors never form and the downstream routes remain absent regardless of bandwidth
  4. Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks

Answer & Explanations

Correct answer: D

A.

This failure concerns another scenario: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. In the stated case: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. The relevant consequence is: Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks. The control that prevents it is: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

B.

This failure concerns another scenario: A university data closet contains several unlabeled cross-connects after a contractor rewired the patch field. In the stated case: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. The relevant consequence is: Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks. The control that prevents it is: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

C.

This failure concerns another scenario: A regional airport turns up a backup routed interconnect but its OSPF peer stays in INIT. In the stated case: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. The relevant consequence is: Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks. The control that prevents it is: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

D.

Unauthorized broadcast domains spread and irrelevant traffic traverses shared uplinks. This is the risk in the stated situation: A concert hall adds a production VLAN and the core trunk carries only older staff VLAN tags. The risky shortcut is: Permit every available VLAN on every trunk instead of scoping to required segments. Prevent it by: Configure required 802.1Q tagged VLANs consistently at each trunk endpoint and exclude unneeded segments.

Question 303

A city council installs an inexpensive access switch that unexpectedly becomes the STP root Which proposed switching or network-engineering action most directly resolves the stated issue?

  1. Align MST region name, revision and VLAN-to-instance mappings across participating switches
  2. Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability
  3. Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances
  4. Configure a supported DHCP relay on the client VLAN interface directed at the authorized server

Answer & Explanations

Correct answer: C

A.

This action is appropriate in a different case: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. There, the reason is: MSTP switches only share consistent instance calculations when region identifiers and VLAN mapping match, avoiding unexpected CIST boundaries. The current case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

B.

This action is appropriate in a different case: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. There, the reason is: A VLAN interface acts as the subnet gateway and participates in route selection; pure Layer 2 access membership does not provide inter-VLAN routing. The current case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

C.

Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. The technical reason is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. The stated condition is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. Confirm the result by: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

D.

This action is appropriate in a different case: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. There, the reason is: DHCP discover broadcasts are local to the client subnet unless a relay forwards the request across the routed boundary with subnet identity. The current case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

Question 304

A city council installs an inexpensive access switch that unexpectedly becomes the STP root An engineer proposes to set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. What technical explanation best supports the intended corrective action?

  1. MSTP switches only share consistent instance calculations when region identifiers and VLAN mapping match, avoiding unexpected CIST boundaries
  2. Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links
  3. A VLAN interface acts as the subnet gateway and participates in route selection; pure Layer 2 access membership does not provide inter-VLAN routing
  4. DHCP discover broadcasts are local to the client subnet unless a relay forwards the request across the routed boundary with subnet identity

Answer & Explanations

Correct answer: B

A.

This principle explains a different technical intervention: Align MST region name, revision and VLAN-to-instance mappings across participating switches. It applies to: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. The actual case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

B.

Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. That mechanism explains the decision: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. In the reported situation: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. Confirmation requires: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

C.

This principle explains a different technical intervention: Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability. It applies to: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. The actual case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

D.

This principle explains a different technical intervention: Configure a supported DHCP relay on the client VLAN interface directed at the authorized server. It applies to: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. The actual case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

Question 305

A city council installs an inexpensive access switch that unexpectedly becomes the STP root What observable postchange evidence would most directly demonstrate that the fix worked?

  1. Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles
  2. Compare region digests and per-instance port roles on each intended region neighbor
  3. Ping the SVI from a host in each source VLAN and trace a permitted inter-VLAN flow end to end
  4. Obtain a fresh lease from a client in each VLAN and verify correct scope, router and server acknowledgement

Answer & Explanations

Correct answer: A

A.

Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles. This check directly tests: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. The underlying behavior is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. The case is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root.

B.

This observation would verify a different remedy: Align MST region name, revision and VLAN-to-instance mappings across participating switches. That remedy applies to: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. The present condition is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

C.

This observation would verify a different remedy: Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability. That remedy applies to: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. The present condition is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

D.

This observation would verify a different remedy: Configure a supported DHCP relay on the client VLAN interface directed at the authorized server. That remedy applies to: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. The present condition is: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

Question 306

A city council installs an inexpensive access switch that unexpectedly becomes the STP root The team wants to implement an approved fix while avoiding a regression. Which proposed shortcut would most directly undermine a safe correction for this particular case?

  1. Change the MST region revision on just one member and assume all switches remain in the same region
  2. Configure access VLANs only and expect isolated subnets to route automatically
  3. Add a static route to the DHCP server but omit the actual DHCP relay configuration
  4. Let a newly installed edge switch with an accidental low bridge ID become the root

Answer & Explanations

Correct answer: D

A.

This proposed shortcut concerns a separate case: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. The risk in this question concerns: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. Here the unsafe shortcut is: Let a newly installed edge switch with an accidental low bridge ID become the root. Use this response instead: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

B.

This proposed shortcut concerns a separate case: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. The risk in this question concerns: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. Here the unsafe shortcut is: Let a newly installed edge switch with an accidental low bridge ID become the root. Use this response instead: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

C.

This proposed shortcut concerns a separate case: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. The risk in this question concerns: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. Here the unsafe shortcut is: Let a newly installed edge switch with an accidental low bridge ID become the root. Use this response instead: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

D.

Let a newly installed edge switch with an accidental low bridge ID become the root. This shortcut is unsafe for: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The resulting failure can be: Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly. The safer response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

Question 307

A city council installs an inexpensive access switch that unexpectedly becomes the STP root Suppose the team instead chooses this shortcut: Let a newly installed edge switch with an accidental low bridge ID become the root. If the team instead takes the following shortcut, what specific outcome is most likely?

  1. An unintended region boundary alters root and path selection for affected VLANs
  2. Users can communicate locally but fail when attempting any cross-subnet service
  3. Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly
  4. Clients in remote VLANs continue timing out because discovery messages never leave their broadcast domains

Answer & Explanations

Correct answer: C

A.

This failure concerns another scenario: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. In the stated case: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The relevant consequence is: Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly. The control that prevents it is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

B.

This failure concerns another scenario: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. In the stated case: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The relevant consequence is: Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly. The control that prevents it is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

C.

Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly. This is the risk in the stated situation: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The risky shortcut is: Let a newly installed edge switch with an accidental low bridge ID become the root. Prevent it by: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

D.

This failure concerns another scenario: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. In the stated case: A city council installs an inexpensive access switch that unexpectedly becomes the STP root. The relevant consequence is: Traffic traverses an inefficient or unstable tree and planned failover paths change unexpectedly. The control that prevents it is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

Question 308

A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link Which proposed switching or network-engineering action most directly resolves the stated issue?

  1. Align MST region name, revision and VLAN-to-instance mappings across participating switches
  2. Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances
  3. Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability
  4. Configure a supported DHCP relay on the client VLAN interface directed at the authorized server

Answer & Explanations

Correct answer: B

A.

This action is appropriate in a different case: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. There, the reason is: MSTP switches only share consistent instance calculations when region identifiers and VLAN mapping match, avoiding unexpected CIST boundaries. The current case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

B.

Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. The technical reason is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. The stated condition is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. Confirm the result by: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

C.

This action is appropriate in a different case: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. There, the reason is: A VLAN interface acts as the subnet gateway and participates in route selection; pure Layer 2 access membership does not provide inter-VLAN routing. The current case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

D.

This action is appropriate in a different case: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. There, the reason is: DHCP discover broadcasts are local to the client subnet unless a relay forwards the request across the routed boundary with subnet identity. The current case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The appropriate response is: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances.

Question 309

A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link An engineer proposes to set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. What technical explanation best supports the intended corrective action?

  1. Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links
  2. MSTP switches only share consistent instance calculations when region identifiers and VLAN mapping match, avoiding unexpected CIST boundaries
  3. A VLAN interface acts as the subnet gateway and participates in route selection; pure Layer 2 access membership does not provide inter-VLAN routing
  4. DHCP discover broadcasts are local to the client subnet unless a relay forwards the request across the routed boundary with subnet identity

Answer & Explanations

Correct answer: A

A.

Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. That mechanism explains the decision: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. In the reported situation: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. Confirmation requires: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

B.

This principle explains a different technical intervention: Align MST region name, revision and VLAN-to-instance mappings across participating switches. It applies to: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. The actual case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

C.

This principle explains a different technical intervention: Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability. It applies to: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. The actual case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

D.

This principle explains a different technical intervention: Configure a supported DHCP relay on the client VLAN interface directed at the authorized server. It applies to: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. The actual case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. The mechanism relevant here is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links.

Question 310

A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link What observable postchange evidence would most directly demonstrate that the fix worked?

  1. Compare region digests and per-instance port roles on each intended region neighbor
  2. Ping the SVI from a host in each source VLAN and trace a permitted inter-VLAN flow end to end
  3. Obtain a fresh lease from a client in each VLAN and verify correct scope, router and server acknowledgement
  4. Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles

Answer & Explanations

Correct answer: D

A.

This observation would verify a different remedy: Align MST region name, revision and VLAN-to-instance mappings across participating switches. That remedy applies to: A research center upgrades one distribution switch and its VLAN-to-MST instance mapping differs from the rest. The present condition is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

B.

This observation would verify a different remedy: Configure the appropriate Layer 3 VLAN interfaces and routing permissions on a switch with supported routing capability. That remedy applies to: An outpatient clinic separates lab printers from reception workstations and now requires tightly scoped inter-VLAN service. The present condition is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

C.

This observation would verify a different remedy: Configure a supported DHCP relay on the client VLAN interface directed at the authorized server. That remedy applies to: A health clinic migrates desktops into a new VLAN but all new devices fail to receive leases. The present condition is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link. To assess it, check: Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles.

D.

Use spanning-tree show commands to verify root identity, path cost and active or alternate port roles. This check directly tests: Set deliberate bridge priorities so the intended distribution switch is the spanning-tree root for relevant instances. The underlying behavior is: Root election controls forwarding tree shape and avoids unintended hairpin or blocked paths through lower-capacity access links. The case is: A broadcast studio adds a floor switch and most inter-floor traffic starts hairpinning over a 1G edge link.

HPE Network Switching Associate (HPE6-A86) Practice Tests