Exam Bundle

At a public library in Portland, this would verify VSX inter-switch link and keepalive, not the failure reported in this scenario. The requested closure criterion instead concerns Multi-chassis LAGs and active paths: the dual-homed access device negotiates its expected LAG and forwards without a layer-two loop after a controlled member failure.

At a public library in Portland, the observation may be useful for a separate First-hop gateway redundancy and failover test, but it does not establish that after a link failure only one physical path remains but the aggregated interface incorrectly reports no active members has been resolved. The relevant check is the Multi-chassis LAGs and active paths outcome.

At a public library in Portland, this measures a different network requirement, VSF member roles and stack consistency. The case describes that after a link failure only one physical path remains but the aggregated interface incorrectly reports no active members, so accepting this result would leave the primary fault without direct verification.

At a regional hospital campus in Richmond, the option addresses VSX inter-switch link and keepalive rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a regional hospital campus in Richmond, that change is aimed at VSF member roles and stack consistency, not at the actual fault: hosts use a distribution switch as default gateway and lose service when that one switch is reloaded. A successful repair here must show that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

Although this is a valid design approach for Multi-chassis LAGs and active paths in an appropriate case, it leaves the First-hop gateway redundancy and failover dependency untested. The observed condition at a regional hospital campus in Richmond is that hosts use a distribution switch as default gateway and lose service when that one switch is reloaded.

At a regional hospital campus in Richmond, this would verify VSX inter-switch link and keepalive, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a regional hospital campus in Richmond, this measures a different network requirement, Multi-chassis LAGs and active paths. The case describes that hosts use a distribution switch as default gateway and lose service when that one switch is reloaded, so accepting this result would leave the primary fault without direct verification.

At a regional hospital campus in Richmond, this would verify VSF member roles and stack consistency, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a hotel campus in Vancouver, the option addresses VSF member roles and stack consistency rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a hotel campus in Vancouver, that change is aimed at Multi-chassis LAGs and active paths, not at the actual fault: hosts use a distribution switch as default gateway and lose service when that one switch is reloaded. A successful repair here must show that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a hotel campus in Vancouver, the option addresses VSX inter-switch link and keepalive rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a hotel campus in Vancouver, this would verify Multi-chassis LAGs and active paths, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a hotel campus in Vancouver, the observation may be useful for a separate VSX inter-switch link and keepalive test, but it does not establish that hosts use a distribution switch as default gateway and lose service when that one switch is reloaded has been resolved. The relevant check is the First-hop gateway redundancy and failover outcome.

At a hotel campus in Vancouver, this measures a different network requirement, VSF member roles and stack consistency. The case describes that hosts use a distribution switch as default gateway and lose service when that one switch is reloaded, so accepting this result would leave the primary fault without direct verification.

At a manufacturing complex in Detroit, that change is aimed at Multi-chassis LAGs and active paths, not at the actual fault: two core devices advertise different virtual gateway addresses to the same access VLAN. A successful repair here must show that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

Although this is a valid design approach for VSF member roles and stack consistency in an appropriate case, it leaves the First-hop gateway redundancy and failover dependency untested. The observed condition at a manufacturing complex in Detroit is that two core devices advertise different virtual gateway addresses to the same access VLAN.

At a manufacturing complex in Detroit, the option addresses VSX inter-switch link and keepalive rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a manufacturing complex in Detroit, the observation may be useful for a separate VSF member roles and stack consistency test, but it does not establish that two core devices advertise different virtual gateway addresses to the same access VLAN has been resolved. The relevant check is the First-hop gateway redundancy and failover outcome.

At a manufacturing complex in Detroit, this measures a different network requirement, VSX inter-switch link and keepalive. The case describes that two core devices advertise different virtual gateway addresses to the same access VLAN, so accepting this result would leave the primary fault without direct verification.

At a manufacturing complex in Detroit, this would verify Multi-chassis LAGs and active paths, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

Although this is a valid design approach for VSF member roles and stack consistency in an appropriate case, it leaves the First-hop gateway redundancy and failover dependency untested. The observed condition at a public safety training center in Oslo is that two core devices advertise different virtual gateway addresses to the same access VLAN.

At a public safety training center in Oslo, the option addresses VSX inter-switch link and keepalive rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a public safety training center in Oslo, that change is aimed at Multi-chassis LAGs and active paths, not at the actual fault: two core devices advertise different virtual gateway addresses to the same access VLAN. A successful repair here must show that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a public safety training center in Oslo, the observation may be useful for a separate VSF member roles and stack consistency test, but it does not establish that two core devices advertise different virtual gateway addresses to the same access VLAN has been resolved. The relevant check is the First-hop gateway redundancy and failover outcome.

At a public safety training center in Oslo, this measures a different network requirement, Multi-chassis LAGs and active paths. The case describes that two core devices advertise different virtual gateway addresses to the same access VLAN, so accepting this result would leave the primary fault without direct verification.

At a public safety training center in Oslo, this would verify VSX inter-switch link and keepalive, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

Although this is a valid design approach for VSF member roles and stack consistency in an appropriate case, it leaves the First-hop gateway redundancy and failover dependency untested. The observed condition at a design studio in Berlin is that an engineer mistakes routing ECMP for a replacement of host first-hop redundancy.

At a design studio in Berlin, the option addresses VSX inter-switch link and keepalive rather than the reported issue. For the stated symptom, the expected evidence is that hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

Although this is a valid design approach for Multi-chassis LAGs and active paths in an appropriate case, it leaves the First-hop gateway redundancy and failover dependency untested. The observed condition at a design studio in Berlin is that an engineer mistakes routing ECMP for a replacement of host first-hop redundancy.

At a design studio in Berlin, this would verify Multi-chassis LAGs and active paths, not the failure reported in this scenario. The requested closure criterion instead concerns First-hop gateway redundancy and failover: hosts retain the intended gateway identity and route through an available peer when the active first-hop device is lost.

At a design studio in Berlin, the observation may be useful for a separate VSF member roles and stack consistency test, but it does not establish that an engineer mistakes routing ECMP for a replacement of host first-hop redundancy has been resolved. The relevant check is the First-hop gateway redundancy and failover outcome.

At a design studio in Berlin, this measures a different network requirement, VSX inter-switch link and keepalive. The case describes that an engineer mistakes routing ECMP for a replacement of host first-hop redundancy, so accepting this result would leave the primary fault without direct verification.