Question 360
A UCS fabric interconnect in NPV mode can establish an FC physical uplink but attached server vHBAs cannot complete login. A storage change board requires a traceable diagnosis before allowing further fabric changes. What information should be inspected before the change is applied?
- Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs.
- Inspect alias database, recorded target WWPNs, zones using the alias and change approvals.
- Inspect interface-to-VSAN membership, active zonesets, fabric IDs and authorized inter-VSAN designs.
- Inspect CFS peers, lock ownership, pending changes, feature status and activation records.
Explanation
Correct Answer
A:Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. That response is associated with device alias maintenance rather than the specific npv uplink fabric services condition described here. For the stated failure, the preferred action is: Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. Relevant evidence: Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:Inspect interface-to-VSAN membership, active zonesets, fabric IDs and authorized inter-VSAN designs. That response is associated with vsan isolation rather than the specific npv uplink fabric services condition described here. For the stated failure, the preferred action is: Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. Relevant evidence: Inspect upstream NPIV configuration, NPV status, uplink VSAN, FLOGI database and server WWPNs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Inspect CFS peers, lock ownership, pending changes, feature status and activation records. This concerns cisco fabric services distribution, not npv uplink fabric services.
Question 361
A VXLAN VTEP can ping peers but no EVPN address-family neighbor is established and remote MAC/IP routes are absent. The team is preparing a controlled production change and must preserve fabric reachability. Which technical principle best explains the recommended response?
- PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery.
- EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings.
- OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings.
- Hybrid cloud combines distinct cloud infrastructures linked to support data and application portability.
Explanation
Correct Answer
B:EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery. That response is associated with pim multicast rendezvous point rather than the specific mp-bgp evpn route learning condition described here. For the stated failure, the preferred action is: Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane. Relevant evidence: Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. The team is preparing a controlled production change and must preserve fabric reachability.
C:OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings. That response is associated with ospfv3 ipv6 neighbor discovery rather than the specific mp-bgp evpn route learning condition described here. For the stated failure, the preferred action is: Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane. Relevant evidence: Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. The team is preparing a controlled production change and must preserve fabric reachability.
D:Hybrid cloud combines distinct cloud infrastructures linked to support data and application portability. This concerns hybrid cloud model classification, not mp-BGP evpn route learning.
Question 362
A new MDS FC port channel comes up with only one member while the remaining ports are suspended. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which technical principle best explains the recommended response?
- FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
- SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints.
- An initiator must complete fabric login and receive an FCID before normal fabric services can identify it.
Explanation
Correct Answer
B:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. That response is associated with fcid and domain id stability rather than the specific fibre channel port-channel consistency condition described here. For the stated failure, the preferred action is: Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. Relevant evidence: Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints. This concerns mds nondisruptive upgrade planning, not fibre channel port-channel consistency.
D:An initiator must complete fabric login and receive an FCID before normal fabric services can identify it. That response is associated with fibre channel fabric login rather than the specific fibre channel port-channel consistency condition described here. For the stated failure, the preferred action is: Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. Relevant evidence: Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 363
Two MDS switches show divergent fabric-level configuration after an operator changed a distributed feature on only one switch. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What should the operator avoid assuming from the observed state?
- Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict.
- Assuming that every local command is distributed automatically can leave peers inconsistent.
- A permissive zone may increase unintended device visibility even when array LUN masking also exists.
- Opening all export access to the entire subnet may bypass least privilege rather than fix the specific denial.
Explanation
Correct Answer
B:Assuming that every local command is distributed automatically can leave peers inconsistent. Cisco Fabric Services can distribute feature configuration among fabric switches, subject to feature-specific rules. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict. This concerns fcid and domain id stability, not cisco fabric services distribution.
C:A permissive zone may increase unintended device visibility even when array LUN masking also exists. This concerns single-initiator zoning, not cisco fabric services distribution.
D:Opening all export access to the entire subnet may bypass least privilege rather than fix the specific denial. This concerns nfs export permissions, not cisco fabric services distribution.
Question 364
A new MDS FC port channel comes up with only one member while the remaining ports are suspended. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which qualification should the change record include?
- An old name-server entry for the former target port does not prove the replacement path is live.
- A target LUN mapping cannot repair a failed physical or fabric login on the initiator port.
- Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric.
- Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict.
Explanation
Correct Answer
C:Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric. Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:An old name-server entry for the former target port does not prove the replacement path is live. This concerns fibre channel name-server entries, not fibre channel port-channel consistency.
B:A target LUN mapping cannot repair a failed physical or fabric login on the initiator port. This concerns fibre channel fabric login, not fibre channel port-channel consistency.
D:Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict. This concerns fcid and domain id stability, not fibre channel port-channel consistency.
Question 365
A VXLAN tenant sees ARP requests at one VTEP but not at another after a change to head-end replication peers. The team is preparing a controlled production change and must preserve fabric reachability. What post-change observation gives the strongest evidence of success?
- The collector receives fresh, structured device state and alerts on a deliberately induced test event.
- Remote tenant prefixes appear in the intended VRF and routed reachability is confirmed end to end.
- ARP broadcasts reach all intended member VTEPs without loops or unintended tenant leakage.
- Captured packets reproduce the reset sequence and identify which endpoint initiated it.
Explanation
Correct Answer
C:ARP broadcasts reach all intended member VTEPs without loops or unintended tenant leakage. This result tests the original failure rather than reporting merely that the configuration command was accepted. Unknown-unicast, broadcast and multicast frames require an appropriate VXLAN replication or multicast transport method. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:The collector receives fresh, structured device state and alerts on a deliberately induced test event. This concerns streaming telemetry health, not bum replication behavior.
B:Remote tenant prefixes appear in the intended VRF and routed reachability is confirmed end to end. This concerns mp-BGP tenant route import, not bum replication behavior.
D:Captured packets reproduce the reset sequence and identify which endpoint initiated it. This concerns span packet-level diagnosis, not bum replication behavior.
Question 366
An API workflow creates an Intersight server profile but fails because referenced policy objects belong to another inaccessible organization. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. How should the implementation be validated against the original failure?
- The job succeeds using protected credentials while committed scripts contain no reusable secret material.
- The authorized profile is created with valid visible policy references and its deployment succeeds.
- The plan lists only intended devices and the deployment audit matches those targets without collateral changes.
- The approved plan contains only intended changes and apply converges without surprising production reversions.
Explanation
Correct Answer
B:The authorized profile is created with valid visible policy references and its deployment succeeds. This result tests the original failure rather than reporting merely that the configuration command was accepted. Intersight objects and their assignments must satisfy resource visibility and scope permissions. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:The job succeeds using protected credentials while committed scripts contain no reusable secret material. This concerns powershell api token security, not intersight policy automation.
C:The plan lists only intended devices and the deployment audit matches those targets without collateral changes. This concerns nexus dashboard automation scope, not intersight policy automation.
D:The approved plan contains only intended changes and apply converges without surprising production reversions. This concerns terraform plan and state, not intersight policy automation.
Question 367
A SAN array replaces a target HBA but operators try to keep its old WWPN hidden behind the same device alias without verification. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which controlled change is most appropriate given the evidence?
- Align trunk allowed VSANs and verify the operational VSAN membership end to end.
- Reconcile FCNS registrations and target identity changes before recreating the entire VSAN.
- Update the device alias to the authorized new WWPN and validate all zoning references before applying it.
- Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning.
Explanation
Correct Answer
C:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. Device aliases map readable names to FC identifiers and must follow actual hardware identity changes. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Align trunk allowed VSANs and verify the operational VSAN membership end to end. This concerns VSAN trunk mismatch, not device alias maintenance.
B:Reconcile FCNS registrations and target identity changes before recreating the entire VSAN. That response is associated with fibre channel name-server entries rather than the specific device alias maintenance condition described here. For the stated failure, the preferred action is: Update the device alias to the authorized new WWPN and validate all zoning references before applying it. Relevant evidence: Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. That response is associated with npv uplink fabric services rather than the specific device alias maintenance condition described here. For the stated failure, the preferred action is: Update the device alias to the authorized new WWPN and validate all zoning references before applying it. Relevant evidence: Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 368
A SAN array replaces a target HBA but operators try to keep its old WWPN hidden behind the same device alias without verification. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which technical principle best explains the recommended response?
- Configured zones and active enforced zoning can differ until the appropriate zoneset is activated.
- Device aliases map readable names to FC identifiers and must follow actual hardware identity changes.
- The fabric name server reflects registered port identities and can reveal whether the expected target is visible.
- NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins.
Explanation
Correct Answer
B:Device aliases map readable names to FC identifiers and must follow actual hardware identity changes. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Configured zones and active enforced zoning can differ until the appropriate zoneset is activated. This concerns zoneset activation state, not device alias maintenance.
C:The fabric name server reflects registered port identities and can reveal whether the expected target is visible. This concerns fibre channel name-server entries, not device alias maintenance.
D:NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. This concerns npv uplink fabric services, not device alias maintenance.
Question 369
An operations team sees sporadic storage-path instability but its monitoring only polls device availability every five minutes. A storage change board requires a traceable diagnosis before allowing further fabric changes. What should the operator avoid assuming from the observed state?
- An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric.
- A link-up indicator for the parent trunk does not prove that every intended VSAN is carried.
- A node-level WWNN cannot always replace a port-specific WWPN expected by the zoning policy.
- A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy.
Explanation
Correct Answer
D:A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy. Topology, fabric events and time-series indicators reveal path problems hidden by simple reachability polling. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric. This concerns VSAN isolation, not nexus dashboard SAN monitoring.
B:A link-up indicator for the parent trunk does not prove that every intended VSAN is carried. This concerns VSAN trunk mismatch, not nexus dashboard SAN monitoring.
C:A node-level WWNN cannot always replace a port-specific WWPN expected by the zoning policy. This concerns wwpn versus wwnn, not nexus dashboard SAN monitoring.
Question 370
Two switches exchange frames over an untrusted fiber run, and security requirements call for link-layer encryption. Security engineering must restore the approved service without relaxing unrelated protection. What caveat is critical when interpreting a successful remediation?
- Enabling only an ARP inspection check may not validate every IP data packet's source identity.
- MACsec does not provide end-to-end application-layer confidentiality beyond each protected Ethernet link.
- Increasing OSPF dead timers does not make incompatible authentication keys acceptable.
- Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception.
Explanation
Correct Answer
B:MACsec does not provide end-to-end application-layer confidentiality beyond each protected Ethernet link. MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Enabling only an ARP inspection check may not validate every IP data packet's source identity. That response is associated with first-hop ip/mac spoof defense rather than the specific macsec protection scope condition described here. For the stated failure, the preferred action is: Enable and validate supported MACsec on both compatible link endpoints with an approved keying design. Relevant evidence: Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters. Security engineering must restore the approved service without relaxing unrelated protection.
C:Increasing OSPF dead timers does not make incompatible authentication keys acceptable. That response is associated with routing protocol keychain rollover rather than the specific macsec protection scope condition described here. For the stated failure, the preferred action is: Enable and validate supported MACsec on both compatible link endpoints with an approved keying design. Relevant evidence: Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters. Security engineering must restore the approved service without relaxing unrelated protection.
D:Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception. This concerns dynamic ARP inspection source of truth, not MACsec protection scope.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests