Cisco 350-601 Practice Test 42
Question 410
An FI uplink is configured for Fibre Channel traffic, but a new service profile's vHBA is associated with the wrong SAN policy. The observed failure is: a mismatched VSAN blocks the expected initiator-to-target login despite physical link operation. Which remediation most directly restores the intended behavior?
- The controlled remediation is to modify the compute hostname instead of checking SAN membership.
- The controlled remediation is to correct SAN policy and VSAN association, then validate initiator login and boot target visibility.
- The controlled remediation is to add the SAN VSAN number as a VLAN on an unrelated Internet-facing switch.
- The controlled remediation is to disable every HBA on the service profile to force target discovery.
Explanation
Correct Answer
B:UCS vHBA connectivity requires a coherent virtual HBA identity and associated Fibre Channel fabric or VSAN. Validate against vHBA VSAN membership, SAN pin group, FI FC uplink state and target login on the fabric.
Incorrect Answers
A:Modify the compute hostname instead of checking SAN membership. This would not reliably restore service after the stated fault. A mismatched VSAN blocks the expected initiator-to-target login despite physical link operation. The controlled recovery is to correct SAN policy and VSAN association, then validate initiator login and boot target visibility.
C:Add the SAN VSAN number as a VLAN on an unrelated Internet-facing switch. This would not reliably restore service after the stated fault. A mismatched VSAN blocks the expected initiator-to-target login despite physical link operation. The controlled recovery is to correct SAN policy and VSAN association, then validate initiator login and boot target visibility.
D:Disable every HBA on the service profile to force target discovery. This would not reliably restore service after the stated fault. A mismatched VSAN blocks the expected initiator-to-target login despite physical link operation. The controlled recovery is to correct SAN policy and VSAN association, then validate initiator login and boot target visibility.
Question 411
A service profile fails SAN provisioning when the WWPN identity pool has no available addresses. Which configuration decision MOST directly resolves the issue?
- Assign the same WWPN to every blade to enable shared access.
- Use a server's IPv4 address as its FC worldwide name.
- Assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
- Disable SAN name-service lookups instead of resolving duplicated WWPNs.
Explanation
Correct Answer
C:This directly addresses wWNN and WWPN identity pools because Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. Confirm the change against wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
Incorrect Answers
A:WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The relevant correction is to assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
B:Use a server's IPv4 address as its FC worldwide name. The proposed change targets the wrong mechanism or lacks essential validation. Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. Relevant evidence is wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
D:WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The appropriate action remains to assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
Question 412
A service profile fails SAN provisioning when the WWPN identity pool has no available addresses. What should the engineer inspect to confirm the actual state?
- An old inventory export that omits the current chassis and firmware state.
- An operator assurance without current logs, component inventory or health faults.
- The planned service profile template without checking effective deployed settings.
- WWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
Explanation
Correct Answer
D:These observations test the actual wWNN and WWPN identity pools mechanism rather than a superficial management status. Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
Incorrect Answers
A:This information cannot independently verify wWNN and WWPN identity pools. The decisive records instead include wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
B:This information cannot independently verify wWNN and WWPN identity pools. Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
C:This information cannot independently verify wWNN and WWPN identity pools. The planned service profile template without checking effective deployed settings.
Question 413
A service profile fails SAN provisioning when the WWPN identity pool has no available addresses. What technical behavior underlies the correct decision?
- Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
- Two logical objects always provide resilience even if they share one failed hardware path.
- All UCS configuration edits take effect without maintenance, validation or dependencies.
- Out-of-band management reachability guarantees that all host interfaces operate correctly.
Explanation
Correct Answer
A:Validation depends on wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks. This explains why the most appropriate response is to assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
Incorrect Answers
B:Two logical objects always provide resilience even if they share one failed hardware path. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
C:All UCS configuration edits take effect without maintenance, validation or dependencies. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
D:Out-of-band management reachability guarantees that all host interfaces operate correctly. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
Question 414
A service profile fails SAN provisioning when the WWPN identity pool has no available addresses. Assume an engineer instead chooses to assign the same WWPN to every blade to enable shared access. Which resulting risk or fault should the reviewer identify?
- A controlled failover test itself proves that the previous outage had no cause.
- WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization.
- The only failure is that the administrator preserved a known-good backup.
- Recording chassis health events is what prevents server management.
Explanation
Correct Answer
B:Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. The meaningful failure is that wWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization.
C:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. The relevant evidence is wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
D:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. Recording chassis health events is what prevents server management.
Question 415
A service profile fails SAN provisioning when the WWPN identity pool has no available addresses. The observed failure is: wWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. Which remediation most directly restores the intended behavior?
- Use a server's IPv4 address as its FC worldwide name.
- Disable SAN name-service lookups instead of resolving duplicated WWPNs.
- Repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
- Assign the same WWPN to every blade to enable shared access.
Explanation
Correct Answer
C:Validate against wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A:Use a server's IPv4 address as its FC worldwide name. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
B:Disable SAN name-service lookups instead of resolving duplicated WWPNs. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
D:Assign the same WWPN to every blade to enable shared access. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
Question 416
Two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities. Which operator action best meets this technical requirement?
- On this affected device, the engineer should use a server's IPv4 address as its FC worldwide name.
- On this affected device, the engineer should disable SAN name-service lookups instead of resolving duplicated WWPNs.
- On this affected device, the engineer should assign the same WWPN to every blade to enable shared access.
- On this affected device, the engineer should assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
Explanation
Correct Answer
D:This directly addresses wWNN and WWPN identity pools because Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
Incorrect Answers
A:Use a server's IPv4 address as its FC worldwide name. The proposed change targets the wrong mechanism or lacks essential validation. Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. Relevant evidence is wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
B:WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. Disable SAN name-service lookups instead of resolving duplicated WWPNs.
C:WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. Assign the same WWPN to every blade to enable shared access.
Question 417
Two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities. Which collection of observations most directly tests the suspected cause?
- For this deployment, examine wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
- For this deployment, examine the rack label without current UCS or Intersight policy associations.
- For this deployment, examine an old inventory export that omits the current chassis and firmware state.
- For this deployment, examine an operator assurance without current logs, component inventory or health faults.
Explanation
Correct Answer
A:These observations test the actual wWNN and WWPN identity pools mechanism rather than a superficial management status. They should be checked after assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
Incorrect Answers
B:This information cannot independently verify wWNN and WWPN identity pools. The rack label without current UCS or Intersight policy associations.
C:This information cannot independently verify wWNN and WWPN identity pools. An old inventory export that omits the current chassis and firmware state.
D:This information cannot independently verify wWNN and WWPN identity pools. An operator assurance without current logs, component inventory or health faults.
Question 418
Two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities. Which statement most accurately explains this scenario?
- For this condition, the applicable principle is that out-of-band management reachability guarantees that all host interfaces operate correctly.
- For this condition, the applicable principle is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
- For this condition, the applicable principle is that two logical objects always provide resilience even if they share one failed hardware path.
- For this condition, the applicable principle is that a rack server that powers on is automatically configured for every SAN and LAN service.
Explanation
Correct Answer
B:Validation depends on wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
Incorrect Answers
A:Out-of-band management reachability guarantees that all host interfaces operate correctly. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
C:Two logical objects always provide resilience even if they share one failed hardware path. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
D:A rack server that powers on is automatically configured for every SAN and LAN service. This is an incorrect generalization for wWNN and WWPN identity pools. The applicable technical behavior is that Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The operator should verify wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks.
Question 419
Two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities. Assume an engineer instead chooses to assign the same WWPN to every blade to enable shared access. What is the principal technical consequence of the mistaken choice?
- The resulting defect is that recording chassis health events is what prevents server management.
- The resulting defect is that checking effective service-profile bindings caused the original hardware mismatch.
- The resulting defect is that wWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization.
- The resulting defect is that the only failure is that the administrator preserved a known-good backup.
Explanation
Correct Answer
C:Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint. The proper corrective action is to assign distinct WWNN and WWPN identities through appropriately scoped UCS pools and service profiles.
Incorrect Answers
A:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. In the given case, two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities.
B:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. Checking effective service-profile bindings caused the original hardware mismatch.
D:This does not explain the actual wWNN and WWPN identity pools defect after the shortcut. The only failure is that the administrator preserved a known-good backup.
Question 420
Two cloned compute profiles accidentally reference identical WWPNs and the Fibre Channel fabric reports duplicate identities. The observed failure is: wWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. What should the engineer do to recover and validate the service?
- The controlled remediation is to disable SAN name-service lookups instead of resolving duplicated WWPNs.
- The controlled remediation is to assign the same WWPN to every blade to enable shared access.
- The controlled remediation is to use a server's IPv4 address as its FC worldwide name.
- The controlled remediation is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
Explanation
Correct Answer
D:Validate against wWN pool allocations, service-profile vHBA identities, FC fabric login database and uniqueness checks. Fibre Channel SAN zoning and logins rely on stable unique WWN identities for each initiator endpoint.
Incorrect Answers
A:Disable SAN name-service lookups instead of resolving duplicated WWPNs. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
B:Assign the same WWPN to every blade to enable shared access. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.
C:Use a server's IPv4 address as its FC worldwide name. This would not reliably restore service after the stated fault. WWPN duplication or exhaustion prevents reliable FC fabric login and storage authorization. The controlled recovery is to repair pool allocation and zone entries for the correct WWPNs, then validate each initiator login.