Cisco 350-601 Practice Test 77
Question 760
An MDS ISL traverses a long-distance optical circuit where the default buffer-to-buffer credit budget cannot fill the bandwidth-delay product. The observed failure is: insufficient credits can throttle a clean FC link even when optical errors are absent. What is the BEST controlled recovery once this failure is recognized?
- The controlled remediation is to change an IP gateway address to add buffer credits to an FC ISL.
- The controlled remediation is to disable all FC flow control credits to allow unlimited transmission.
- The controlled remediation is to reduce zoning security to increase propagation speed.
- The controlled remediation is to allocate supported credits and confirm credit recovery and throughput under load.
Explanation
Correct Answer
D:Fibre Channel uses buffer-to-buffer credits for hop flow control, so long propagation delay can require more credits. Validate against bB-credit counters, zero-credit intervals, distance and line rate, and frame throughput.
Incorrect Answers
A:Change an IP gateway address to add buffer credits to an FC ISL. This would not reliably restore service after the stated fault. Insufficient credits can throttle a clean FC link even when optical errors are absent. The controlled recovery is to allocate supported credits and confirm credit recovery and throughput under load.
B:Disable all FC flow control credits to allow unlimited transmission. This would not reliably restore service after the stated fault. Insufficient credits can throttle a clean FC link even when optical errors are absent. The controlled recovery is to allocate supported credits and confirm credit recovery and throughput under load.
C:Reduce zoning security to increase propagation speed. This would not reliably restore service after the stated fault. Insufficient credits can throttle a clean FC link even when optical errors are absent. The controlled recovery is to allocate supported credits and confirm credit recovery and throughput under load.
Question 761
Several SAN initiators suffer head-of-line blocking when one storage target drains frames unusually slowly. What is the BEST supported implementation or corrective action?
- Identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
- Increase every host's TCP window to fix FC credit starvation.
- Disable SAN telemetry so congestion alarms disappear.
- Change switch hostname to reduce storage target response time.
Explanation
Correct Answer
A:This directly addresses slow-drain device congestion because a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. Confirm the change against FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
Incorrect Answers
B:Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The relevant correction is to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
C:Disable SAN telemetry so congestion alarms disappear. The proposed change targets the wrong mechanism or lacks essential validation. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. Relevant evidence is FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
D:Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The appropriate action remains to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
Question 762
Several SAN initiators suffer head-of-line blocking when one storage target drains frames unusually slowly. Which evidence BEST verifies the intended technical behavior?
- A historical FC topology drawing with no current WWPN or port state.
- FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
- A storage vendor slogan without the relevant login and path counters.
- A copied zoneset name without its active effective members.
Explanation
Correct Answer
B:These observations test the actual slow-drain device congestion mechanism rather than a superficial management status. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Incorrect Answers
A:A historical FC topology drawing with no current WWPN or port state. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
C:A storage vendor slogan without the relevant login and path counters. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
D:A copied zoneset name without its active effective members. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Question 763
Several SAN initiators suffer head-of-line blocking when one storage target drains frames unusually slowly. Which principle BEST explains why the recommended solution is appropriate?
- Every storage protocol provides the same file and block semantics.
- Fibre Channel name service entries are identical to host multipath device state.
- A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
- An unused VSAN number can replace an active zoning or port security rule.
Explanation
Correct Answer
C:This explains why the most appropriate response is to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation. Validation depends on FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
Incorrect Answers
A:Every storage protocol provides the same file and block semantics. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
B:Fibre Channel name service entries are identical to host multipath device state. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
D:An unused VSAN number can replace an active zoning or port security rule. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
Question 764
Several SAN initiators suffer head-of-line blocking when one storage target drains frames unusually slowly. Assume an engineer instead chooses to increase every host's TCP window to fix FC credit starvation. What is the MOST significant failure introduced by that shortcut?
- The sole error was using a verified SAN maintenance window for a risky operation.
- Inspecting credit counters prevents FC frames from forwarding.
- A well-documented host multipath test is the source of the original fabric fault.
- Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure.
Explanation
Correct Answer
D:The proper corrective action is to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Incorrect Answers
A:This does not explain the actual slow-drain device congestion defect after the shortcut. The meaningful failure is that treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure.
B:This does not explain the actual slow-drain device congestion defect after the shortcut. The relevant evidence is FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
C:This does not explain the actual slow-drain device congestion defect after the shortcut. A well-documented host multipath test is the source of the original fabric fault.
Question 765
Several SAN initiators suffer head-of-line blocking when one storage target drains frames unusually slowly. The observed failure is: treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. What is the BEST controlled recovery once this failure is recognized?
- Repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
- Disable SAN telemetry so congestion alarms disappear.
- Change switch hostname to reduce storage target response time.
- Increase every host's TCP window to fix FC credit starvation.
Explanation
Correct Answer
A:This addresses the observable fault while preserving a check of the expected result. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Incorrect Answers
B:Disable SAN telemetry so congestion alarms disappear. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
C:Change switch hostname to reduce storage target response time. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
D:Increase every host's TCP window to fix FC credit starvation. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
Question 766
A single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy. Which configuration decision MOST directly resolves the issue?
- On this affected device, the engineer should disable SAN telemetry so congestion alarms disappear.
- On this affected device, the engineer should identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
- On this affected device, the engineer should change switch hostname to reduce storage target response time.
- On this affected device, the engineer should increase every host's TCP window to fix FC credit starvation.
Explanation
Correct Answer
B:This directly addresses slow-drain device congestion because a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Incorrect Answers
A:Disable SAN telemetry so congestion alarms disappear. The proposed change targets the wrong mechanism or lacks essential validation. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. Relevant evidence is FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
C:Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. In the given case, a single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy.
D:Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. Increase every host's TCP window to fix FC credit starvation.
Question 767
A single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy. What should the engineer inspect to confirm the actual state?
- For this deployment, examine a green physical FC link light without fabric login, zoning or I/O evidence.
- For this deployment, examine a historical FC topology drawing with no current WWPN or port state.
- For this deployment, examine FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
- For this deployment, examine a storage vendor slogan without the relevant login and path counters.
Explanation
Correct Answer
C:These observations test the actual slow-drain device congestion mechanism rather than a superficial management status. They should be checked after identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
Incorrect Answers
A:A green physical FC link light without fabric login, zoning or I/O evidence. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
B:A historical FC topology drawing with no current WWPN or port state. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
D:A storage vendor slogan without the relevant login and path counters. This information cannot independently verify slow-drain device congestion. The decisive records instead include FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events. A slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Question 768
A single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy. What technical behavior underlies the correct decision?
- For this condition, the applicable principle is that an unused VSAN number can replace an active zoning or port security rule.
- For this condition, the applicable principle is that every storage protocol provides the same file and block semantics.
- For this condition, the applicable principle is that a lit Fibre Channel link proves end-to-end LUN visibility and authorized I/O.
- For this condition, the applicable principle is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources.
Explanation
Correct Answer
D:This explains why the most appropriate response is to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation.
Incorrect Answers
A:An unused VSAN number can replace an active zoning or port security rule. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
B:Every storage protocol provides the same file and block semantics. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
C:A lit Fibre Channel link proves end-to-end LUN visibility and authorized I/O. This is an incorrect generalization for slow-drain device congestion. The applicable technical behavior is that a slow-drain FC device can propagate backpressure and affect unrelated workloads sharing fabric resources. The operator should verify FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
Question 769
A single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy. Assume an engineer instead chooses to increase every host's TCP window to fix FC credit starvation. Which resulting risk or fault should the reviewer identify?
- The resulting defect is that treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure.
- The resulting defect is that a well-documented host multipath test is the source of the original fabric fault.
- The resulting defect is that examining FCNS entries automatically removes the authorized zoning policy.
- The resulting defect is that inspecting credit counters prevents FC frames from forwarding.
Explanation
Correct Answer
A:The proper corrective action is to identify the slow-drain endpoint using per-port congestion evidence and apply supported isolation or remediation. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
B:This does not explain the actual slow-drain device congestion defect after the shortcut. In the given case, a single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy.
C:This does not explain the actual slow-drain device congestion defect after the shortcut. Examining FCNS entries automatically removes the authorized zoning policy.
D:The meaningful failure is that treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure.
Question 770
A single impaired FC endpoint creates increasing transmit queue occupancy on shared MDS paths while other devices are healthy. The observed failure is: treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. Which remediation most directly restores the intended behavior?
- The controlled remediation is to change switch hostname to reduce storage target response time.
- The controlled remediation is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
- The controlled remediation is to increase every host's TCP window to fix FC credit starvation.
- The controlled remediation is to disable SAN telemetry so congestion alarms disappear.
Explanation
Correct Answer
B:This addresses the observable fault while preserving a check of the expected result. Validate against FC queue occupancy, transmit credit loss, latency and endpoint-specific congestion events.
Incorrect Answers
A:Change switch hostname to reduce storage target response time. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
C:Increase every host's TCP window to fix FC credit starvation. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.
D:Disable SAN telemetry so congestion alarms disappear. This would not reliably restore service after the stated fault. Treating all SAN congestion as simple bandwidth shortage can miss one stalled receiver causing backpressure. The controlled recovery is to repair the slow endpoint or apply supported congestion isolation and verify unaffected traffic recovery.