Cisco 350-601 Practice Test 74
Question 730
An MDS F-port learns only the first virtual HBA and rejects others when a blade hypervisor starts more VMs. The observed failure is: if NPIV is disabled, additional virtual initiators cannot register independently through the port. Which remediation most directly restores the intended behavior?
- The controlled remediation is to create OSPF adjacencies for each virtual initiator instead of enabling NPIV.
- The controlled remediation is to correct NPIV support and limits and confirm each virtual initiator has a distinct login.
- The controlled remediation is to reassign all virtual HBAs to one duplicate WWPN to conserve addresses.
- The controlled remediation is to assume VLAN tagging replaces Fibre Channel virtual logins.
Explanation
Correct Answer
B:NPIV allows multiple distinct N-port identities to share the same physical connection to a Fibre Channel fabric. Validate against NPIV capability and limits, upstream F-port state, individual virtual WWPN FLOGI entries.
Incorrect Answers
A:Create OSPF adjacencies for each virtual initiator instead of enabling NPIV. This would not reliably restore service after the stated fault. If NPIV is disabled, additional virtual initiators cannot register independently through the port. The controlled recovery is to correct NPIV support and limits and confirm each virtual initiator has a distinct login.
C:Reassign all virtual HBAs to one duplicate WWPN to conserve addresses. This would not reliably restore service after the stated fault. If NPIV is disabled, additional virtual initiators cannot register independently through the port. The controlled recovery is to correct NPIV support and limits and confirm each virtual initiator has a distinct login.
D:Assume VLAN tagging replaces Fibre Channel virtual logins. This would not reliably restore service after the stated fault. If NPIV is disabled, additional virtual initiators cannot register independently through the port. The controlled recovery is to correct NPIV support and limits and confirm each virtual initiator has a distinct login.
Question 731
A device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution. Which configuration decision MOST directly resolves the issue?
- Use duplicate aliases for unrelated WWPNs without tracing identity.
- Assume an uncommitted local alias edit automatically updates every switch.
- Check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
- Convert aliases into arbitrary IPv4 hostnames to make FC zoning work.
Explanation
Correct Answer
C:This directly addresses device alias distribution and consistency because fabric-wide device aliases require supported database management and consistent references across switches. Confirm the change against device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
Incorrect Answers
A:Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The relevant correction is to check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
B:Assume an uncommitted local alias edit automatically updates every switch. The proposed change targets the wrong mechanism or lacks essential validation. Fabric-wide device aliases require supported database management and consistent references across switches. Relevant evidence is device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
D:Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The appropriate action remains to check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
Question 732
A device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution. What should the engineer inspect to confirm the actual state?
- A copied zoneset name without its active effective members.
- A historical FC topology drawing with no current WWPN or port state.
- An Ethernet ping that does not test the required SAN session or VSAN.
- Device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
Explanation
Correct Answer
D:These observations test the actual device alias distribution and consistency mechanism rather than a superficial management status. Fabric-wide device aliases require supported database management and consistent references across switches.
Incorrect Answers
A:This information cannot independently verify device alias distribution and consistency. The decisive records instead include device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
B:This information cannot independently verify device alias distribution and consistency. Fabric-wide device aliases require supported database management and consistent references across switches.
C:This information cannot independently verify device alias distribution and consistency. An Ethernet ping that does not test the required SAN session or VSAN.
Question 733
A device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution. What technical behavior underlies the correct decision?
- Fabric-wide device aliases require supported database management and consistent references across switches.
- An unused VSAN number can replace an active zoning or port security rule.
- WWPN zoning and IP access lists are interchangeable security primitives.
- Fibre Channel name service entries are identical to host multipath device state.
Explanation
Correct Answer
A:Validation depends on device-alias database per switch, current CFS session, alias target WWPN and distribution consistency. This explains why the most appropriate response is to check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
Incorrect Answers
B:An unused VSAN number can replace an active zoning or port security rule. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
C:WWPN zoning and IP access lists are interchangeable security primitives. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
D:Fibre Channel name service entries are identical to host multipath device state. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
Question 734
A device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution. Assume an engineer instead chooses to use duplicate aliases for unrelated WWPNs without tracing identity. Which resulting risk or fault should the reviewer identify?
- The SAN failed because operators retained correct WWPN identity records.
- Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities.
- The sole error was using a verified SAN maintenance window for a risky operation.
- Inspecting credit counters prevents FC frames from forwarding.
Explanation
Correct Answer
B:The proper corrective action is to check device-alias mode and commit or distribute the updated mapping consistently within the fabric. That is the direct consequence of choosing the misleading shortcut.
Incorrect Answers
A:This does not explain the actual device alias distribution and consistency defect after the shortcut. The meaningful failure is that inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities.
C:This does not explain the actual device alias distribution and consistency defect after the shortcut. The relevant evidence is device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
D:This does not explain the actual device alias distribution and consistency defect after the shortcut. In the given case, a device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution.
Question 735
A device alias resolves correctly on one MDS switch but not on another following an incomplete fabric distribution. The observed failure is: inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. Which remediation most directly restores the intended behavior?
- Assume an uncommitted local alias edit automatically updates every switch.
- Convert aliases into arbitrary IPv4 hostnames to make FC zoning work.
- Commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
- Use duplicate aliases for unrelated WWPNs without tracing identity.
Explanation
Correct Answer
C:Validate against device-alias database per switch, current CFS session, alias target WWPN and distribution consistency. This addresses the observable fault while preserving a check of the expected result.
Incorrect Answers
A:Assume an uncommitted local alias edit automatically updates every switch. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
B:Convert aliases into arbitrary IPv4 hostnames to make FC zoning work. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
D:Use duplicate aliases for unrelated WWPNs without tracing identity. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
Question 736
An administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value. Which operator action best meets this technical requirement?
- On this affected device, the engineer should assume an uncommitted local alias edit automatically updates every switch.
- On this affected device, the engineer should convert aliases into arbitrary IPv4 hostnames to make FC zoning work.
- On this affected device, the engineer should use duplicate aliases for unrelated WWPNs without tracing identity.
- On this affected device, the engineer should check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
Explanation
Correct Answer
D:This directly addresses device alias distribution and consistency because fabric-wide device aliases require supported database management and consistent references across switches.
Incorrect Answers
A:Assume an uncommitted local alias edit automatically updates every switch. The proposed change targets the wrong mechanism or lacks essential validation. Fabric-wide device aliases require supported database management and consistent references across switches. Relevant evidence is device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
B:Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. In the given case, an administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value.
C:Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. Use duplicate aliases for unrelated WWPNs without tracing identity.
Question 737
An administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value. Which collection of observations most directly tests the suspected cause?
- For this deployment, examine device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
- For this deployment, examine a storage vendor slogan without the relevant login and path counters.
- For this deployment, examine a copied zoneset name without its active effective members.
- For this deployment, examine a historical FC topology drawing with no current WWPN or port state.
Explanation
Correct Answer
A:These observations test the actual device alias distribution and consistency mechanism rather than a superficial management status. They should be checked after check device-alias mode and commit or distribute the updated mapping consistently within the fabric.
Incorrect Answers
B:This information cannot independently verify device alias distribution and consistency. A storage vendor slogan without the relevant login and path counters.
C:This information cannot independently verify device alias distribution and consistency. A copied zoneset name without its active effective members.
D:This information cannot independently verify device alias distribution and consistency. In the given case, an administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value.
Question 738
An administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value. Which statement most accurately explains this scenario?
- For this condition, the applicable principle is that Fibre Channel name service entries are identical to host multipath device state.
- For this condition, the applicable principle is that fabric-wide device aliases require supported database management and consistent references across switches.
- 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.
Explanation
Correct Answer
B:Validation depends on device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
Incorrect Answers
A:Fibre Channel name service entries are identical to host multipath device state. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
C:An unused VSAN number can replace an active zoning or port security rule. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
D:Every storage protocol provides the same file and block semantics. This is an incorrect generalization for device alias distribution and consistency. The applicable technical behavior is that fabric-wide device aliases require supported database management and consistent references across switches. The operator should verify device-alias database per switch, current CFS session, alias target WWPN and distribution consistency.
Question 739
An administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value. Assume an engineer instead chooses to use duplicate aliases for unrelated WWPNs without tracing identity. What is the principal technical consequence of the mistaken choice?
- The resulting defect is that inspecting credit counters prevents FC frames from forwarding.
- The resulting defect is that a well-documented host multipath test is the source of the original fabric fault.
- The resulting defect is that inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities.
- The resulting defect is that the sole error was using a verified SAN maintenance window for a risky operation.
Explanation
Correct Answer
C:The proper corrective action is to check device-alias mode and commit or distribute the updated mapping consistently within the fabric. Fabric-wide device aliases require supported database management and consistent references across switches.
Incorrect Answers
A:This does not explain the actual device alias distribution and consistency defect after the shortcut. In the given case, an administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value.
B:This does not explain the actual device alias distribution and consistency defect after the shortcut. A well-documented host multipath test is the source of the original fabric fault.
D:This does not explain the actual device alias distribution and consistency defect after the shortcut. The sole error was using a verified SAN maintenance window for a risky operation.
Question 740
An administrator changes a persistent alias-to-WWPN mapping and zone operations on peer switches still reference the old value. The observed failure is: inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. What should the engineer do to recover and validate the service?
- The controlled remediation is to convert aliases into arbitrary IPv4 hostnames to make FC zoning work.
- The controlled remediation is to use duplicate aliases for unrelated WWPNs without tracing identity.
- The controlled remediation is to assume an uncommitted local alias edit automatically updates every switch.
- The controlled remediation is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
Explanation
Correct Answer
D:Validate against device-alias database per switch, current CFS session, alias target WWPN and distribution consistency. Fabric-wide device aliases require supported database management and consistent references across switches.
Incorrect Answers
A:Convert aliases into arbitrary IPv4 hostnames to make FC zoning work. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
B:Use duplicate aliases for unrelated WWPNs without tracing identity. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.
C:Assume an uncommitted local alias edit automatically updates every switch. This would not reliably restore service after the stated fault. Inconsistent aliases complicate zoning and can direct operators toward obsolete SAN identities. The controlled recovery is to commit or distribute the verified alias database and confirm active zones resolve to the intended WWPNs.