HP HPE7-A01 Practice Test 10
Question 90
A switch uplink uses two physical fibers but a traffic capture reveals only one is in the active LACP aggregation. Which specific corrective design step best meets the stated campus requirement?
- Set valid site DNS resolvers and the supported AP management destination in the existing provisioned configuration.
- Align both ends' LACP settings and compatible member parameters in the approved aggregation group.
- Configure the appropriate DHCP relay on the routed interface and ensure the server scope and return path match the client subnet.
- Place management traffic in the approved dedicated interface or VRF and constrain permitted administrator sources.
Explanation
Correct Answer
B:Align both ends' LACP settings and compatible member parameters in the approved aggregation group. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The proposed configuration targets the stated dependency without broadening unrelated access. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
A:Set valid site DNS resolvers and the supported AP management destination in the existing provisioned configuration. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It would not implement the specifically required change. The immediate problem concerns lag uplink membership and hashing.
C:Configure the appropriate DHCP relay on the routed interface and ensure the server scope and return path match the client subnet. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It would not implement the specifically required change. The immediate problem concerns lag uplink membership and hashing.
D:Place management traffic in the approved dedicated interface or VRF and constrain permitted administrator sources. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It would not implement the specifically required change. The immediate problem concerns lag uplink membership and hashing.
Question 91
A switch uplink uses two physical fibers but a traffic capture reveals only one is in the active LACP aggregation. Following a targeted change, which acceptance test would most directly demonstrate success?
- Confirm both expected links are collecting and distributing and balanced flows pass without new interface errors.
- Verify the AP resolves the expected control-plane hostname and appears online in its assigned management inventory.
- Capture DHCP discover, relay, offer and acknowledgment packets to confirm clients receive appropriate leases.
- Verify approved NOC sessions succeed and blocked campus-client sources cannot reach management services.
Explanation
Correct Answer
A:Confirm both expected links are collecting and distributing and balanced flows pass without new interface errors. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The result tests actual working behavior, not merely a saved configuration. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
B:Verify the AP resolves the expected control-plane hostname and appears online in its assigned management inventory. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
C:Capture DHCP discover, relay, offer and acknowledgment packets to confirm clients receive appropriate leases. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
D:Verify approved NOC sessions succeed and blocked campus-client sources cannot reach management services. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
Question 92
A switch uplink uses two physical fibers but a traffic capture reveals only one is in the active LACP aggregation. The change fails acceptance. What is the safest targeted restoration action?
- Restore the last verified DNS settings for the site and confirm AP control connectivity before retrying the change.
- Reinstate the previous relay configuration and server route to restore leases while the new path is investigated.
- Reapply the last controlled management ACL and known-good out-of-band path to preserve access while repairing isolation.
- Restore the former compatible LAG membership and disable the mismatched link until its configuration is corrected.
Explanation
Correct Answer
D:Restore the former compatible LAG membership and disable the mismatched link until its configuration is corrected. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The focused rollback restores a known safe baseline before another change attempt. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
A:Restore the last verified DNS settings for the site and confirm AP control connectivity before retrying the change. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
B:Reinstate the previous relay configuration and server route to restore leases while the new path is investigated. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
C:Reapply the last controlled management ACL and known-good out-of-band path to preserve access while repairing isolation. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
Question 93
An aggregation uplink has one member suspended after a port-channel ID mismatch and users observe reduced bandwidth. Before implementing a remedy, what should the engineer check first?
- Review DHCP-provided resolver information, DNS name resolution and reachability to the management service endpoint.
- Review client DHCP discovery, relay destination configuration and permitted server reply path at the VLAN gateway.
- Review LACP partner identifiers, actor state, member compatibility and active aggregated-port status.
- Cross-check management interface or VRF assignments, reachability paths and source-access controls for administrative traffic.
Explanation
Correct Answer
C:Review LACP partner identifiers, actor state, member compatibility and active aggregated-port status. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The evidence check isolates the relevant prerequisite before a disruptive change. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
A:Review DHCP-provided resolver information, DNS name resolution and reachability to the management service endpoint. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It does not isolate the cause of the stated incident. The immediate problem concerns lag uplink membership and hashing.
B:Review client DHCP discovery, relay destination configuration and permitted server reply path at the VLAN gateway. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It does not isolate the cause of the stated incident. The immediate problem concerns lag uplink membership and hashing.
D:Cross-check management interface or VRF assignments, reachability paths and source-access controls for administrative traffic. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It does not isolate the cause of the stated incident. The immediate problem concerns lag uplink membership and hashing.
Question 94
An aggregation uplink has one member suspended after a port-channel ID mismatch and users observe reduced bandwidth. The review requires TWO complementary actions: one diagnostic check and one controlled configuration remedy. Select TWO actions that together meet those requirements.
- Review DHCP-provided resolver information, DNS name resolution and reachability to the management service endpoint.
- Review LACP partner identifiers, actor state, member compatibility and active aggregated-port status.
- Set up the appropriate DHCP relay on the routed interface and ensure the server scope and return path match the client subnet.
- Match both ends' LACP settings and compatible member parameters in the approved aggregation group.
Explanation
Correct Answers
B:Review LACP partner identifiers, actor state, member compatibility and active aggregated-port status. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. This is the required diagnosis or controlled remedy; the other keyed action supplies the complementary role. The decision applies to the described lag uplink membership and hashing situation.
D:Match both ends' LACP settings and compatible member parameters in the approved aggregation group. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. This is the required diagnosis or controlled remedy; the other keyed action supplies the complementary role. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
A:Review DHCP-provided resolver information, DNS name resolution and reachability to the management service endpoint. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It is not one of the requested paired diagnosis and configuration actions. The immediate problem concerns lag uplink membership and hashing.
C:Set up the appropriate DHCP relay on the routed interface and ensure the server scope and return path match the client subnet. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It is not one of the requested paired diagnosis and configuration actions. The immediate problem concerns lag uplink membership and hashing.
Question 95
An aggregation uplink has one member suspended after a port-channel ID mismatch and users observe reduced bandwidth. A deployment job reports success. Which observed result would actually validate the affected service?
- Verify both expected links are collecting and distributing and balanced flows pass without new interface errors.
- Confirm the AP resolves the expected control-plane hostname and appears online in its assigned management inventory.
- Collect DHCP discover, relay, offer and acknowledgment packets to confirm clients receive appropriate leases.
- Confirm approved NOC sessions succeed and blocked campus-client sources cannot reach management services.
Explanation
Correct Answer
A:Verify both expected links are collecting and distributing and balanced flows pass without new interface errors. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The result tests actual working behavior, not merely a saved configuration. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
B:Confirm the AP resolves the expected control-plane hostname and appears online in its assigned management inventory. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
C:Collect DHCP discover, relay, offer and acknowledgment packets to confirm clients receive appropriate leases. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
D:Confirm approved NOC sessions succeed and blocked campus-client sources cannot reach management services. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It would not establish that this function actually works. The immediate problem concerns lag uplink membership and hashing.
Question 96
An aggregation uplink has one member suspended after a port-channel ID mismatch and users observe reduced bandwidth. If the revised setting disrupts users, which controlled rollback would be most relevant?
- Reinstate the last verified DNS settings for the site and confirm AP control connectivity before retrying the change.
- Restore the previous relay configuration and server route to restore leases while the new path is investigated.
- Reapply the last controlled management ACL and known-good out-of-band path to preserve access while repairing isolation for the affected campus deployment.
- Reinstate the former compatible LAG membership and disable the mismatched link until its configuration is corrected.
Explanation
Correct Answer
D:Reinstate the former compatible LAG membership and disable the mismatched link until its configuration is corrected. LACP builds a logical link only from mutually compatible members; physical link-up does not guarantee aggregation eligibility. The focused rollback restores a known safe baseline before another change attempt. The decision applies to the described lag uplink membership and hashing situation.
Incorrect Answers
A:Reinstate the last verified DNS settings for the site and confirm AP control connectivity before retrying the change. This instead concerns ap dns and management reachability. An AP can have valid local addressing while failing discovery if name resolution or reachability to its intended management service is broken. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
B:Restore the previous relay configuration and server route to restore leases while the new path is investigated. This instead concerns dhcp scope and relay on routed vlans. A DHCP broadcast does not normally cross a routed boundary without relay; correct scope and return reachability are both necessary. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
C:Reapply the last controlled management ACL and known-good out-of-band path to preserve access while repairing isolation for the affected campus deployment. This instead concerns management vlan access isolation. Data-plane connectivity and administrative reachability serve different trust boundaries; a dedicated management design restricts who can configure devices. It would not safely roll back the relevant failed change. The immediate problem concerns lag uplink membership and hashing.
Question 97
A pair of campus aggregation switches reports a VSX peer-sync failure after the inter-switch link LAG loses its active members. Which investigation would best isolate the immediate network dependency?
- Inspect VSX keepalive source and peer IP reachability separately from the inter-switch link status.
- Compare active-gateway virtual IP and shared MAC configuration on both peers for the affected VLAN.
- Inspect configured VSX synchronization categories and the current configuration diff for the relevant feature.
- Inspect VSX peer status, inter-switch link aggregation members and the actual ISL forwarding path.
Explanation
Correct Answer
D:Inspect VSX peer status, inter-switch link aggregation members and the actual ISL forwarding path. A VSX deployment requires a healthy inter-switch link for coordinated peer functions; keepalive reachability alone does not replace it. The evidence check isolates the relevant prerequisite before a disruptive change. The decision applies to the described vsx inter-switch link integrity situation.
Incorrect Answers
A:Inspect VSX keepalive source and peer IP reachability separately from the inter-switch link status. This instead concerns vsx keepalive versus isl failure. Keepalive and ISL supply complementary VSX control evidence; treating them as the same link obscures failure isolation. It does not isolate the cause of the stated incident. The immediate problem concerns vsx inter-switch link integrity.
B:Compare active-gateway virtual IP and shared MAC configuration on both peers for the affected VLAN. This instead concerns vsx active-gateway consistency. VSX active gateway depends on consistent virtual gateway identity; uncoordinated peer settings cause intermittent forwarding failures. It does not isolate the cause of the stated incident. The immediate problem concerns vsx inter-switch link integrity.
C:Inspect configured VSX synchronization categories and the current configuration diff for the relevant feature. This instead concerns vsx synchronization scope. VSX synchronizes only supported selected configuration categories; peer devices remain independent control planes with some intentionally distinct settings. It does not isolate the cause of the stated incident. The immediate problem concerns vsx inter-switch link integrity.
Question 98
A pair of campus aggregation switches reports a VSX peer-sync failure after the inter-switch link LAG loses its active members. Which specific corrective design step best meets the stated campus requirement?
- Restore a supported independent peer keepalive path with correct routing without using the ISL as its sole failure domain.
- Configure a consistent supported VSX active-gateway address and virtual MAC across corresponding gateway interfaces.
- Repair the supported VSX ISL LAG and peer configuration while keeping the redundant topology and consistency requirements intact.
- Enable supported synchronization for the intended configuration contexts and make controlled local-only exceptions explicitly.
Explanation
Correct Answer
C:Repair the supported VSX ISL LAG and peer configuration while keeping the redundant topology and consistency requirements intact. A VSX deployment requires a healthy inter-switch link for coordinated peer functions; keepalive reachability alone does not replace it. The proposed configuration targets the stated dependency without broadening unrelated access. The decision applies to the described vsx inter-switch link integrity situation.
Incorrect Answers
A:Restore a supported independent peer keepalive path with correct routing without using the ISL as its sole failure domain. This instead concerns vsx keepalive versus isl failure. Keepalive and ISL supply complementary VSX control evidence; treating them as the same link obscures failure isolation. It would not implement the specifically required change. The immediate problem concerns vsx inter-switch link integrity.
B:Configure a consistent supported VSX active-gateway address and virtual MAC across corresponding gateway interfaces. This instead concerns vsx active-gateway consistency. VSX active gateway depends on consistent virtual gateway identity; uncoordinated peer settings cause intermittent forwarding failures. It would not implement the specifically required change. The immediate problem concerns vsx inter-switch link integrity.
D:Enable supported synchronization for the intended configuration contexts and make controlled local-only exceptions explicitly. This instead concerns vsx synchronization scope. VSX synchronizes only supported selected configuration categories; peer devices remain independent control planes with some intentionally distinct settings. It would not implement the specifically required change. The immediate problem concerns vsx inter-switch link integrity.
Question 99
A pair of campus aggregation switches reports a VSX peer-sync failure after the inter-switch link LAG loses its active members. Following a targeted change, which acceptance test would most directly demonstrate success?
- Confirm stable keepalive probe results and healthy VSX dual-peer status across a controlled path test.
- Confirm the VSX peers and ISL report healthy roles and expected state synchronization under normal load.
- Verify either uplink path reaches the same default gateway and client traffic survives a controlled peer disruption.
- Validate the selected feature is consistent on both peers while intended independent interfaces remain unique.
Explanation
Correct Answer
B:Confirm the VSX peers and ISL report healthy roles and expected state synchronization under normal load. A VSX deployment requires a healthy inter-switch link for coordinated peer functions; keepalive reachability alone does not replace it. The result tests actual working behavior, not merely a saved configuration. The decision applies to the described vsx inter-switch link integrity situation.
Incorrect Answers
A:Confirm stable keepalive probe results and healthy VSX dual-peer status across a controlled path test. This instead concerns vsx keepalive versus isl failure. Keepalive and ISL supply complementary VSX control evidence; treating them as the same link obscures failure isolation. It would not establish that this function actually works. The immediate problem concerns vsx inter-switch link integrity.
C:Verify either uplink path reaches the same default gateway and client traffic survives a controlled peer disruption. This instead concerns vsx active-gateway consistency. VSX active gateway depends on consistent virtual gateway identity; uncoordinated peer settings cause intermittent forwarding failures. It would not establish that this function actually works. The immediate problem concerns vsx inter-switch link integrity.
D:Validate the selected feature is consistent on both peers while intended independent interfaces remain unique. This instead concerns vsx synchronization scope. VSX synchronizes only supported selected configuration categories; peer devices remain independent control planes with some intentionally distinct settings. It would not establish that this function actually works. The immediate problem concerns vsx inter-switch link integrity.
Question 100
A pair of campus aggregation switches reports a VSX peer-sync failure after the inter-switch link LAG loses its active members. The change fails acceptance. What is the safest targeted restoration action?
- Restore the previous stable ISL wiring and configuration before changing active-gateway behavior or reopening traffic.
- Reinstate the previously reachable keepalive interface and route while preserving the working ISL configuration.
- Restore the last matching active-gateway parameters on both peers and verify ARP or neighbor cache convergence.
- Return the affected feature to a documented peer-consistent configuration and disable unsupported synchronization assumptions.
Explanation
Correct Answer
A:Restore the previous stable ISL wiring and configuration before changing active-gateway behavior or reopening traffic. A VSX deployment requires a healthy inter-switch link for coordinated peer functions; keepalive reachability alone does not replace it. The focused rollback restores a known safe baseline before another change attempt. The decision applies to the described vsx inter-switch link integrity situation.
Incorrect Answers
B:Reinstate the previously reachable keepalive interface and route while preserving the working ISL configuration. This instead concerns vsx keepalive versus isl failure. Keepalive and ISL supply complementary VSX control evidence; treating them as the same link obscures failure isolation. It would not safely roll back the relevant failed change. The immediate problem concerns vsx inter-switch link integrity.
C:Restore the last matching active-gateway parameters on both peers and verify ARP or neighbor cache convergence. This instead concerns vsx active-gateway consistency. VSX active gateway depends on consistent virtual gateway identity; uncoordinated peer settings cause intermittent forwarding failures. It would not safely roll back the relevant failed change. The immediate problem concerns vsx inter-switch link integrity.
D:Return the affected feature to a documented peer-consistent configuration and disable unsupported synchronization assumptions. This instead concerns vsx synchronization scope. VSX synchronizes only supported selected configuration categories; peer devices remain independent control planes with some intentionally distinct settings. It would not safely roll back the relevant failed change. The immediate problem concerns vsx inter-switch link integrity.
