Cisco 300-610 Practice Test 47
Question 460
At a high-IOPS virtualized storage farm, the architecture standards group considers the recurring risk: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Monitor slow-drain indicators and isolate high-risk targets where supported.
- Review FC service classes whenever SAN zones and applications change.
- Include microburst stress in storage fabric qualification.
- Run DCB compatibility tests after upgrading switches or UCS fabrics.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Monitor slow-drain indicators and isolate high-risk targets where supported. The risk it addresses is: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. This check is tied to the technical principle: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. The immediate correction remains: Identify the slow-drain device or oversubscribed path and correct its bottleneck before indiscriminately increasing credits. Periodically validate the safeguard through two different observations. Inspect BB-credit-zero and congestion events on adjacent FC ports Compare target response time with ISL utilization for affected flows. The continuing acceptance target is: Well-behaved SAN paths no longer stall behind the slow target.
Incorrect Answers
B:This is a continuing control for fibre channel qos class expectations; its underlying principle is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. The recurring risk here is different: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The intended long-term acceptance condition remains: Well-behaved SAN paths no longer stall behind the slow target.
C:This is a continuing control for san burst buffer and latency; its underlying principle is: Short FC bursts can exhaust buffer credits even when long-period average utilization suggests spare capacity. The recurring risk here is different: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A storage-array controller briefly bursts high-rate FC traffic and one upstream port shows repeated credit loss, yet average utilization is low. The intended long-term acceptance condition remains: Well-behaved SAN paths no longer stall behind the slow target.
D:This is a continuing control for fcoe priority-flow consistency; its underlying principle is: FCoE requires consistent DCB/FCoE traffic classification and PFC handling along the supported converged path. The recurring risk here is different: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: FCoE storage frames arrive on a converged Ethernet fabric with a lossless priority but get remapped to a lossy queue in a transit switch. The intended long-term acceptance condition remains: Well-behaved SAN paths no longer stall behind the slow target.
Question 461
At a high-IOPS virtualized storage farm, a proposed deployment has this failure mode: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Identify the slow-drain device or oversubscribed path and correct its bottleneck before indiscriminately increasing credits.
- Design technology-specific QoS and transport isolation for each storage protocol instead of a blanket policy.
- Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings.
- Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements.
Explanation
Correct Answer
C:The relevant failure is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The technical distinction is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. The targeted correction is: Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings. Before changing the design, check two independent observations. Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion. Accept the change only if: Storage priorities are enforced without inappropriate IP-only controls.
Incorrect Answers
A:This action targets fc slow-drain credit starvation, where the mechanism is: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. That is a separate condition from the problem in this question: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. Even a successful repair of the alternative would not establish the required result: Storage priorities are enforced without inappropriate IP-only controls. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
B:This action targets fc versus iscsi unified traffic requirements, where the mechanism is: Native FC uses its own fabric credit flow control; FCoE uses DCB/PFC transport; iSCSI operates on TCP/IP and ordinary IP congestion behavior. That is a separate condition from the problem in this question: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. Even a successful repair of the alternative would not establish the required result: Storage priorities are enforced without inappropriate IP-only controls. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets isl oversubscription for peak san load, where the mechanism is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. That is a separate condition from the problem in this question: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. Even a successful repair of the alternative would not establish the required result: Storage priorities are enforced without inappropriate IP-only controls. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 462
At a storage-replication data center, the cause remains unconfirmed for this reported issue: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Measure per-ISL throughput and BB-credit stress; compare peak host-to-target flows against the available fabric trunk capacity.
- Capture markings entering and leaving transit devices; compare queue service and storage I/O latency during concurrent load.
- Inspect effective FC QoS policy and traffic class counters; measure latency for priority and best-effort SAN flows under congestion.
- Capture per-port BB-credit and throughput at short intervals; correlate bursts with I/O latency and affected port buffers.
Explanation
Correct Answer
C:The first observation is: Inspect effective FC QoS policy and traffic class counters The independent second observation is: Measure latency for priority and best-effort SAN flows under congestion. Together they test the proposed diagnosis of this incident: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The underlying technical principle is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. If those checks confirm it, the appropriate next action is: Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings. The expected measurable result is: Storage priorities are enforced without inappropriate IP-only controls.
Incorrect Answers
A:These observations investigate isl oversubscription for peak san load; they would be useful if the symptoms were: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. That alternative rests on the principle: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. The question instead asks for evidence about: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The discriminating observations here are: Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion.
B:These observations investigate iscsi dscp-to-queue contract; they would be useful if the symptoms were: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. That alternative rests on the principle: End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it. The question instead asks for evidence about: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The discriminating observations here are: Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion.
D:These observations investigate san burst buffer and latency; they would be useful if the symptoms were: A storage-array controller briefly bursts high-rate FC traffic and one upstream port shows repeated credit loss, yet average utilization is low. That alternative rests on the principle: Short FC bursts can exhaust buffer credits even when long-period average utilization suggests spare capacity. The question instead asks for evidence about: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The discriminating observations here are: Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion.
Question 463
At a dual-fabric enterprise SAN, a failure review must identify the central technical cause of: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Short FC bursts can exhaust buffer credits even when long-period average utilization suggests spare capacity.
- End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it.
- Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
- Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
Explanation
Correct Answer
C:The controlling technical principle is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. This matters because the reported design failure is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The first diagnostic check is: Inspect effective FC QoS policy and traffic class counters The independent check is: Measure latency for priority and best-effort SAN flows under congestion. These facts support the targeted intervention: Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings. Confirm that the resulting design meets this condition: Storage priorities are enforced without inappropriate IP-only controls.
Incorrect Answers
A:The offered principle describes san burst buffer and latency: Short FC bursts can exhaust buffer credits even when long-period average utilization suggests spare capacity. That is useful for a distinct incident, such as: A storage-array controller briefly bursts high-rate FC traffic and one upstream port shows repeated credit loss, yet average utilization is low. It does not account for the reported failure: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The governing principle in this situation is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
B:The offered principle describes iscsi dscp-to-queue contract: End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it. That is useful for a distinct incident, such as: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. It does not account for the reported failure: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The governing principle in this situation is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
D:The offered principle describes isl oversubscription for peak san load: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. That is useful for a distinct incident, such as: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. It does not account for the reported failure: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The governing principle in this situation is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
Question 464
At a converged FCoE storage network, the service owner needs evidence of resolution for: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Each storage technology receives suitable congestion handling without harming neighboring services.
- Storage priorities are enforced without inappropriate IP-only controls.
- Critical storage flows meet bandwidth targets without persistent ISL contention.
- FCoE maintains required continuity through the converged network path.
Explanation
Correct Answer
B:The relevant measurable success criterion is: Storage priorities are enforced without inappropriate IP-only controls. It addresses the original reported defect: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion. The correction being evaluated is: Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings. The underlying reason that correction matters is: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
Incorrect Answers
A:This metric would help validate a correction to fc versus iscsi unified traffic requirements, rather than the original reported issue. The other issue is: An architecture applies a single generic congestion policy to native Fibre Channel, FCoE and iSCSI, ignoring their different transport mechanisms. Here the defect to be resolved is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The expected measurable outcome for the actual incident is: Storage priorities are enforced without inappropriate IP-only controls. A positive result for the other service would not prove this requirement is met.
C:This metric would help validate a correction to isl oversubscription for peak san load, rather than the original reported issue. The other issue is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. Here the defect to be resolved is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The expected measurable outcome for the actual incident is: Storage priorities are enforced without inappropriate IP-only controls. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to fcoe priority-flow consistency, rather than the original reported issue. The other issue is: FCoE storage frames arrive on a converged Ethernet fabric with a lossless priority but get remapped to a lossy queue in a transit switch. Here the defect to be resolved is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The expected measurable outcome for the actual incident is: Storage priorities are enforced without inappropriate IP-only controls. A positive result for the other service would not prove this requirement is met.
Question 465
At a distributed AI checkpoint storage service, after correction, the team wants to prevent recurrence of: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Forecast ISL demand when major hosts or target ports migrate.
- Audit trust boundaries and QoS maps when storage hosts are moved.
- Monitor slow-drain indicators and isolate high-risk targets where supported.
- Review FC service classes whenever SAN zones and applications change.
Explanation
Correct Answer
D:The most relevant ongoing safeguard is: Review FC service classes whenever SAN zones and applications change. The risk it addresses is: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. This check is tied to the technical principle: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. The immediate correction remains: Select supported FC QoS and class-of-service mappings based on storage service requirements, not generic IP settings. Periodically validate the safeguard through two different observations. Inspect effective FC QoS policy and traffic class counters Measure latency for priority and best-effort SAN flows under congestion. The continuing acceptance target is: Storage priorities are enforced without inappropriate IP-only controls.
Incorrect Answers
A:This is a continuing control for isl oversubscription for peak san load; its underlying principle is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. The recurring risk here is different: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The intended long-term acceptance condition remains: Storage priorities are enforced without inappropriate IP-only controls.
B:This is a continuing control for iscsi dscp-to-queue contract; its underlying principle is: End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it. The recurring risk here is different: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. The intended long-term acceptance condition remains: Storage priorities are enforced without inappropriate IP-only controls.
C:This is a continuing control for fc slow-drain credit starvation; its underlying principle is: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. The recurring risk here is different: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The intended long-term acceptance condition remains: Storage priorities are enforced without inappropriate IP-only controls.
Question 466
At a distributed AI checkpoint storage service, a design review reports the following issue: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The maintenance plan must not disrupt unrelated tenants. Which design correction most directly addresses this specific failure or requirement?
- Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements.
- Align FCoE CoS/VLAN/PFC policy end-to-end rather than enabling global Ethernet pause.
- Design technology-specific QoS and transport isolation for each storage protocol instead of a blanket policy.
- Evaluate per-port buffer credit requirements, ISL link distance and storage burst behavior together.
Explanation
Correct Answer
A:The relevant failure is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The technical distinction is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. The targeted correction is: Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements. Before changing the design, check two independent observations. Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity. Accept the change only if: Critical storage flows meet bandwidth targets without persistent ISL contention.
Incorrect Answers
B:This action targets fcoe priority-flow consistency, where the mechanism is: FCoE requires consistent DCB/FCoE traffic classification and PFC handling along the supported converged path. That is a separate condition from the problem in this question: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. Even a successful repair of the alternative would not establish the required result: Critical storage flows meet bandwidth targets without persistent ISL contention. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
C:This action targets fc versus iscsi unified traffic requirements, where the mechanism is: Native FC uses its own fabric credit flow control; FCoE uses DCB/PFC transport; iSCSI operates on TCP/IP and ordinary IP congestion behavior. That is a separate condition from the problem in this question: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. Even a successful repair of the alternative would not establish the required result: Critical storage flows meet bandwidth targets without persistent ISL contention. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
D:This action targets san burst buffer and latency, where the mechanism is: Short FC bursts can exhaust buffer credits even when long-period average utilization suggests spare capacity. That is a separate condition from the problem in this question: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. Even a successful repair of the alternative would not establish the required result: Critical storage flows meet bandwidth targets without persistent ISL contention. The applicable design change must address the diagnosed mechanism of the stated case, not the neighboring design problem.
Question 467
At a high-IOPS virtualized storage farm, two engineers propose competing diagnoses for this condition: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. Acceptance requires evidence from the running system, not just the saved design. Which pair of observations most directly tests the proposed diagnosis before a change?
- Measure per-ISL throughput and BB-credit stress; compare peak host-to-target flows against the available fabric trunk capacity.
- Inspect ingress and egress CoS/priority maps; correlate dropped FCoE frames or fabric logouts with transit queue counters.
- Inspect effective FC QoS policy and traffic class counters; measure latency for priority and best-effort SAN flows under congestion.
- Inspect BB-credit-zero and congestion events on adjacent FC ports; compare target response time with ISL utilization for affected flows.
Explanation
Correct Answer
A:The first observation is: Measure per-ISL throughput and BB-credit stress The independent second observation is: Compare peak host-to-target flows against the available fabric trunk capacity. Together they test the proposed diagnosis of this incident: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The underlying technical principle is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. If those checks confirm it, the appropriate next action is: Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements. The expected measurable result is: Critical storage flows meet bandwidth targets without persistent ISL contention.
Incorrect Answers
B:These observations investigate fcoe priority-flow consistency; they would be useful if the symptoms were: FCoE storage frames arrive on a converged Ethernet fabric with a lossless priority but get remapped to a lossy queue in a transit switch. That alternative rests on the principle: FCoE requires consistent DCB/FCoE traffic classification and PFC handling along the supported converged path. The question instead asks for evidence about: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The discriminating observations here are: Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity.
C:These observations investigate fibre channel qos class expectations; they would be useful if the symptoms were: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. That alternative rests on the principle: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. The question instead asks for evidence about: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The discriminating observations here are: Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity.
D:These observations investigate fc slow-drain credit starvation; they would be useful if the symptoms were: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. That alternative rests on the principle: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. The question instead asks for evidence about: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The discriminating observations here are: Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity.
Question 468
At a storage-replication data center, the design group challenges an assumption behind this issue: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. One component outage must remain inside the agreed availability budget. Which engineering principle best explains the observed behavior?
- Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
- Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS.
- End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it.
- FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs.
Explanation
Correct Answer
A:The controlling technical principle is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. This matters because the reported design failure is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The first diagnostic check is: Measure per-ISL throughput and BB-credit stress The independent check is: Compare peak host-to-target flows against the available fabric trunk capacity. These facts support the targeted intervention: Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements. Confirm that the resulting design meets this condition: Critical storage flows meet bandwidth targets without persistent ISL contention.
Incorrect Answers
B:The offered principle describes fibre channel qos class expectations: Fibre Channel fabric QoS and congestion controls use FC-specific classes and credits with platform capabilities distinct from Ethernet IP QoS. That is useful for a distinct incident, such as: A SAN QoS policy prioritizes certain FC traffic but the design assumes FC behaves like ordinary routed IP DSCP scheduling. It does not account for the reported failure: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The governing principle in this situation is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
C:The offered principle describes iscsi dscp-to-queue contract: End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it. That is useful for a distinct incident, such as: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. It does not account for the reported failure: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The governing principle in this situation is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
D:The offered principle describes fc slow-drain credit starvation: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. That is useful for a distinct incident, such as: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. It does not account for the reported failure: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The governing principle in this situation is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
Question 469
At a dual-fabric enterprise SAN, a change has been proposed for the following condition: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The architect must preserve the intended failure domains. Which measured result most directly proves the original requirement is satisfied?
- Storage traffic reaches its intended scheduler class with predictable service.
- Well-behaved SAN paths no longer stall behind the slow target.
- Critical storage flows meet bandwidth targets without persistent ISL contention.
- FCoE maintains required continuity through the converged network path.
Explanation
Correct Answer
C:The relevant measurable success criterion is: Critical storage flows meet bandwidth targets without persistent ISL contention. It addresses the original reported defect: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. A saved design or configuration command alone does not establish that outcome. Observe the affected system in two independent ways: Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity. The correction being evaluated is: Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements. The underlying reason that correction matters is: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL.
Incorrect Answers
A:This metric would help validate a correction to iscsi dscp-to-queue contract, rather than the original reported issue. The other issue is: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. Here the defect to be resolved is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The expected measurable outcome for the actual incident is: Critical storage flows meet bandwidth targets without persistent ISL contention. A positive result for the other service would not prove this requirement is met.
B:This metric would help validate a correction to fc slow-drain credit starvation, rather than the original reported issue. The other issue is: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. Here the defect to be resolved is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The expected measurable outcome for the actual incident is: Critical storage flows meet bandwidth targets without persistent ISL contention. A positive result for the other service would not prove this requirement is met.
D:This metric would help validate a correction to fcoe priority-flow consistency, rather than the original reported issue. The other issue is: FCoE storage frames arrive on a converged Ethernet fabric with a lossless priority but get remapped to a lossy queue in a transit switch. Here the defect to be resolved is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The expected measurable outcome for the actual incident is: Critical storage flows meet bandwidth targets without persistent ISL contention. A positive result for the other service would not prove this requirement is met.
Question 470
At a converged FCoE storage network, a post-incident design review focuses on preventing: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The team needs a defensible design decision rather than a vendor feature checklist. Which continuing design control best prevents the same problem from recurring?
- Forecast ISL demand when major hosts or target ports migrate.
- Run DCB compatibility tests after upgrading switches or UCS fabrics.
- Audit trust boundaries and QoS maps when storage hosts are moved.
- Monitor slow-drain indicators and isolate high-risk targets where supported.
Explanation
Correct Answer
A:The most relevant ongoing safeguard is: Forecast ISL demand when major hosts or target ports migrate. The risk it addresses is: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. This check is tied to the technical principle: Inter-switch link bandwidth and traffic locality determine SAN oversubscription; host-port nominal rates cannot all be assumed simultaneous across one ISL. The immediate correction remains: Size and distribute FC ISLs using actual traffic matrices and degraded-mode requirements. Periodically validate the safeguard through two different observations. Measure per-ISL throughput and BB-credit stress Compare peak host-to-target flows against the available fabric trunk capacity. The continuing acceptance target is: Critical storage flows meet bandwidth targets without persistent ISL contention.
Incorrect Answers
B:This is a continuing control for fcoe priority-flow consistency; its underlying principle is: FCoE requires consistent DCB/FCoE traffic classification and PFC handling along the supported converged path. The recurring risk here is different: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: FCoE storage frames arrive on a converged Ethernet fabric with a lossless priority but get remapped to a lossy queue in a transit switch. The intended long-term acceptance condition remains: Critical storage flows meet bandwidth targets without persistent ISL contention.
C:This is a continuing control for iscsi dscp-to-queue contract; its underlying principle is: End-to-end iSCSI QoS depends on consistent classification and queuing; packets need not retain their host's mark unless policy trusts it. The recurring risk here is different: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A host marks iSCSI packets with one DSCP value but upstream switches apply a different trust boundary and storage requests are delayed. The intended long-term acceptance condition remains: Critical storage flows meet bandwidth targets without persistent ISL contention.
D:This is a continuing control for fc slow-drain credit starvation; its underlying principle is: FC buffer-to-buffer credit flow control can propagate congestion from a slow-drain endpoint across shared ISLs. The recurring risk here is different: Two FC switches have numerous high-speed host ports but one underprovisioned inter-switch link carries every storage flow. The appropriate ongoing control must prevent recurrence of that particular failure, not just the separate issue of: A Fibre Channel fabric has healthy physical links but one slow storage target causes upstream ports to stop transmitting for lack of credits. The intended long-term acceptance condition remains: Critical storage flows meet bandwidth targets without persistent ISL contention.