Cisco 350-601 Practice Test 4
Question 30
A maintenance change makes an uplink interface passive in OSPF and the adjacent routing device disappears from the neighbor table. The observed failure is: leaving the transit interface passive suppresses expected neighbor discovery and route updates. Which recovery action addresses the underlying technical fault?
- The controlled remediation is to configure a BGP route reflector instead of restoring OSPF hellos.
- The controlled remediation is to correct the interface-specific passive setting and verify hello exchange and routes without exposing host-facing interfaces.
- The controlled remediation is to make every host-facing port an OSPF neighbor interface.
- The controlled remediation is to set the OSPF reference bandwidth to zero.
Explanation
Correct Answer
B:A passive OSPF interface may advertise its connected network but does not actively form protocol adjacencies. Validate against OSPF interface passive status, observed hello packets, full neighbor formation, and route installation.
Incorrect Answers
A:Configure a BGP route reflector instead of restoring OSPF hellos. This would not reliably restore service after the stated fault. Leaving the transit interface passive suppresses expected neighbor discovery and route updates. The controlled recovery is to correct the interface-specific passive setting and verify hello exchange and routes without exposing host-facing interfaces.
C:Make every host-facing port an OSPF neighbor interface. This would not reliably restore service after the stated fault. Leaving the transit interface passive suppresses expected neighbor discovery and route updates. The controlled recovery is to correct the interface-specific passive setting and verify hello exchange and routes without exposing host-facing interfaces.
D:Set the OSPF reference bandwidth to zero. This would not reliably restore service after the stated fault. Leaving the transit interface passive suppresses expected neighbor discovery and route updates. The controlled recovery is to correct the interface-specific passive setting and verify hello exchange and routes without exposing host-facing interfaces.
Question 31
A Nexus Dashboard application reports fabric health degradation but the operations team relies only on interface-up indicators. Which next step should the data center engineer select?
- Disable all assurance alerts because the switches respond to ICMP.
- Assume a healthy management VRF guarantees every tenant flow.
- Use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
- Change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault.
Explanation
Correct Answer
C:This directly addresses Nexus Dashboard fabric health insights because Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. Confirm the change against dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Incorrect Answers
A:A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. The relevant correction is to use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
B:Assume a healthy management VRF guarantees every tenant flow. The proposed change targets the wrong mechanism or lacks essential validation. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. Relevant evidence is dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
D:A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. The appropriate action remains to use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
Question 32
A Nexus Dashboard application reports fabric health degradation but the operations team relies only on interface-up indicators. Which diagnostic record would most strongly confirm the result?
- A healthy optical light without checking protocol neighbors or forwarding entries.
- One successful ping to an unrelated management address.
- A pre-change network diagram with no live control-plane state.
- Dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Explanation
Correct Answer
D:These observations test the actual Nexus Dashboard fabric health insights mechanism rather than a superficial management status. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
Incorrect Answers
A:A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
B:One successful ping to an unrelated management address. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
C:A pre-change network diagram with no live control-plane state. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
Question 33
A Nexus Dashboard application reports fabric health degradation but the operations team relies only on interface-up indicators. Which platform concept should guide the engineer’s assessment?
- Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
- Configuration differences between peer switches cannot affect network traffic.
- A working management-plane ping proves every tenant and application path is healthy.
- All control-plane protocols exchange state automatically after a cable is inserted.
Explanation
Correct Answer
A:Validation depends on dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. This explains why the most appropriate response is to use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
Incorrect Answers
B:Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
C:A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
D:All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Question 34
A Nexus Dashboard application reports fabric health degradation but the operations team relies only on interface-up indicators. Assume an engineer instead chooses to disable all assurance alerts because the switches respond to ICMP. Which root-cause observation follows from that incorrect change?
- Investigating the forwarding table is the reason a broken route cannot converge.
- A per-device ping result alone cannot prove that all application paths and policy relationships are healthy.
- The only consequence of the wrong change is a different device description.
- Verifying topology after maintenance automatically creates a switching loop.
Explanation
Correct Answer
B:Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. The meaningful failure is that a per-device ping result alone cannot prove that all application paths and policy relationships are healthy.
C:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. The relevant evidence is dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
D:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. Verifying topology after maintenance automatically creates a switching loop.
Question 35
A Nexus Dashboard application reports fabric health degradation but the operations team relies only on interface-up indicators. The observed failure is: a per-device ping result alone cannot prove that all application paths and policy relationships are healthy. Which recovery action addresses the underlying technical fault?
- Assume a healthy management VRF guarantees every tenant flow.
- Change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault.
- Correlate Dashboard findings with switch telemetry, repair the implicated link or policy, and validate fabric health improvement.
- Disable all assurance alerts because the switches respond to ICMP.
Explanation
Correct Answer
C:Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A:That option would assume a healthy management VRF guarantees every tenant flow, but it addresses a different concern. This addresses the observable fault while preserving a check of the expected result.
B:That option would change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault, but it addresses a different concern. This addresses the observable fault while preserving a check of the expected result.
D:That option would disable all assurance alerts because the switches respond to ICMP, but it addresses a different concern. This addresses the observable fault while preserving a check of the expected result.
Question 36
An APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed. What is the BEST supported implementation or corrective action?
- On this affected device, the engineer should assume a healthy management VRF guarantees every tenant flow.
- On this affected device, the engineer should change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault.
- On this affected device, the engineer should disable all assurance alerts because the switches respond to ICMP.
- On this affected device, the engineer should use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
Explanation
Correct Answer
D:This directly addresses Nexus Dashboard fabric health insights because Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
Incorrect Answers
A:Assume a healthy management VRF guarantees every tenant flow. The proposed change targets the wrong mechanism or lacks essential validation. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. Relevant evidence is dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
B:A per-device ping result alone cannot prove that all application paths and policy relationships are healthy.
C:A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. Disable all assurance alerts because the switches respond to ICMP.
Question 37
An APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed. Which evidence BEST verifies the intended technical behavior?
- For this deployment, examine dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
- For this deployment, examine an interface description without the effective peer or VXLAN policy.
- For this deployment, examine a healthy optical light without checking protocol neighbors or forwarding entries.
- For this deployment, examine one successful ping to an unrelated management address.
Explanation
Correct Answer
A:These observations test the actual Nexus Dashboard fabric health insights mechanism rather than a superficial management status. They should be checked after use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
Incorrect Answers
B:An interface description without the effective peer or VXLAN policy. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
C:A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
D:One successful ping to an unrelated management address. This information cannot independently verify Nexus Dashboard fabric health insights. The decisive records instead include dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters. Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
Question 38
An APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed. Which principle BEST explains why the recommended solution is appropriate?
- For this condition, the applicable principle is that all control-plane protocols exchange state automatically after a cable is inserted.
- For this condition, the applicable principle is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface.
- For this condition, the applicable principle is that configuration differences between peer switches cannot affect network traffic.
- For this condition, the applicable principle is that a device description always determines actual forwarding policy regardless of running configuration.
Explanation
Correct Answer
B:Validation depends on dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Incorrect Answers
A:All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
C:Configuration differences between peer switches cannot affect network traffic. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
D:A device description always determines actual forwarding policy regardless of running configuration. This is an incorrect generalization for Nexus Dashboard fabric health insights. The applicable technical behavior is that Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The operator should verify dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Question 39
An APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed. Assume an engineer instead chooses to disable all assurance alerts because the switches respond to ICMP. What is the MOST significant failure introduced by that shortcut?
- The resulting defect is that verifying topology after maintenance automatically creates a switching loop.
- The resulting defect is that the defect exists solely because the engineer documented the change.
- The resulting defect is that a per-device ping result alone cannot prove that all application paths and policy relationships are healthy.
- The resulting defect is that the only consequence of the wrong change is a different device description.
Explanation
Correct Answer
C:Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. The proper corrective action is to use Nexus Dashboard fabric topology and assurance findings to localize affected links and policy dependencies.
Incorrect Answers
A:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. In the given case, an APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed.
B:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. The defect exists solely because the engineer documented the change.
D:This does not explain the actual Nexus Dashboard fabric health insights defect after the shortcut. The only consequence of the wrong change is a different device description.
Question 40
An APIC-managed or NX-OS fabric has intermittent application path anomalies while individual switch pings all succeed. The observed failure is: a per-device ping result alone cannot prove that all application paths and policy relationships are healthy. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault.
- The controlled remediation is to disable all assurance alerts because the switches respond to ICMP.
- The controlled remediation is to assume a healthy management VRF guarantees every tenant flow.
- The controlled remediation is to correlate Dashboard findings with switch telemetry, repair the implicated link or policy, and validate fabric health improvement.
Explanation
Correct Answer
D:Nexus Dashboard provides centralized fabric visibility and assurance that can reveal multi-device failures not visible from one interface. Validate against dashboard fabric inventory, correlated assurance alarms, node and link health, and cross-checks with device counters.
Incorrect Answers
A:Change SAN zoning to clear a fabric-wide Nexus Dashboard topology fault. This would not reliably restore service after the stated fault. A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. The controlled recovery is to correlate Dashboard findings with switch telemetry, repair the implicated link or policy, and validate fabric health improvement.
B:Disable all assurance alerts because the switches respond to ICMP. This would not reliably restore service after the stated fault. A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. The controlled recovery is to correlate Dashboard findings with switch telemetry, repair the implicated link or policy, and validate fabric health improvement.
C:Assume a healthy management VRF guarantees every tenant flow. This would not reliably restore service after the stated fault. A per-device ping result alone cannot prove that all application paths and policy relationships are healthy. The controlled recovery is to correlate Dashboard findings with switch telemetry, repair the implicated link or policy, and validate fabric health improvement.