Question 140
A UCS fabric interconnect in NPV mode can establish an FC physical uplink but attached server vHBAs cannot complete login. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What is the strongest technical basis for the recommended action?
- NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins.
- Device aliases map readable names to FC identifiers and must follow actual hardware identity changes.
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
Explanation
Correct Answer
A:NPV proxies initiator logins through an upstream fabric switch, which must support the required virtual-port logins. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Device aliases map readable names to FC identifiers and must follow actual hardware identity changes. This concerns device alias maintenance, not npv uplink fabric services.
C:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. This concerns VSAN isolation, not npv uplink fabric services.
D:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. This concerns VSAN trunk mismatch, not npv uplink fabric services.
Question 141
A scheduled PowerShell script manages Intersight but embeds a long-lived API private key directly in source control. The automation change must pass a preproduction test and leave a verifiable audit trail. What should the engineer do first to address the observed failure?
- Move secrets to a supported secure secret store and scope the automation identity to required API permissions.
- Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context.
- Constrain automation targets using verified site identity and a preflight plan before bulk deployment.
- Reconcile the approved desired configuration and actual state using plan review and controlled state management.
Explanation
Correct Answer
A:Move secrets to a supported secure secret store and scope the automation identity to required API permissions. Credential protection and least privilege reduce the impact of source-code disclosure. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
B:Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. This concerns eem syslog-triggered remediation, not powershell api token security.
C:Constrain automation targets using verified site identity and a preflight plan before bulk deployment. That response is associated with nexus dashboard automation scope rather than the specific powershell api token security condition described here. For the stated failure, the preferred action is: Move secrets to a supported secure secret store and scope the automation identity to required API permissions. Relevant evidence: Inspect repository history, credential storage, role scope, token rotation and execution audit logs. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Reconcile the approved desired configuration and actual state using plan review and controlled state management. That response is associated with terraform plan and state rather than the specific powershell api token security condition described here. For the stated failure, the preferred action is: Move secrets to a supported secure secret store and scope the automation identity to required API permissions. Relevant evidence: Inspect repository history, credential storage, role scope, token rotation and execution audit logs. The automation change must pass a preproduction test and leave a verifiable audit trail.
Question 142
A Nexus vPC secondary suspends downstream vPC member ports when the peer-link goes down but peer-keepalive still reaches the primary. The team is preparing a controlled production change and must preserve fabric reachability. Which explanation most directly accounts for the required correction?
- LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members.
- With peer-link failure and a reachable peer, the secondary suspends vPC member ports to prevent loops and dual-active forwarding.
- MP-BGP session establishment does not guarantee tenant routes will be imported when policy attributes mismatch.
- RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary.
Explanation
Correct Answer
B:With peer-link failure and a reachable peer, the secondary suspends vPC member ports to prevent loops and dual-active forwarding. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members. That response is associated with lacp member mismatch rather than the specific vpc peer-link recovery condition described here. For the stated failure, the preferred action is: Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. Relevant evidence: Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. The team is preparing a controlled production change and must preserve fabric reachability.
C:MP-BGP session establishment does not guarantee tenant routes will be imported when policy attributes mismatch. This concerns mp-BGP tenant route import, not vpc peer-link recovery.
D:RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary. That response is associated with rstp blocked uplink rather than the specific vpc peer-link recovery condition described here. For the stated failure, the preferred action is: Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. Relevant evidence: Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. The team is preparing a controlled production change and must preserve fabric reachability.
Question 143
A contractor must view Nexus interface health but currently has a role that can change routing and security configuration. Security engineering must restore the approved service without relaxing unrelated protection. Which technical principle best explains the recommended response?
- ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing.
- Role-based access control limits administrators to the commands and resources needed for their work.
- Storage network RBAC limits configuration actions independently of physical access to SAN switches.
- Remote AAA improves centralized administration but must have an appropriate resilient recovery mechanism.
Explanation
Correct Answer
B:Role-based access control limits administrators to the commands and resources needed for their work. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. That response is associated with aci inter-epg contract rather than the specific nx-os administrative rbac condition described here. For the stated failure, the preferred action is: Assign a restricted read-only RBAC role covering the required monitoring commands. Relevant evidence: Inspect assigned user roles, AAA server attributes, command authorization and audit logs. Security engineering must restore the approved service without relaxing unrelated protection.
C:Storage network RBAC limits configuration actions independently of physical access to SAN switches. This concerns mds SAN administrative control, not nx-os administrative RBAC.
D:Remote AAA improves centralized administration but must have an appropriate resilient recovery mechanism. That response is associated with centralized aaa fallback rather than the specific nx-os administrative rbac condition described here. For the stated failure, the preferred action is: Assign a restricted read-only RBAC role covering the required monitoring commands. Relevant evidence: Inspect assigned user roles, AAA server attributes, command authorization and audit logs. Security engineering must restore the approved service without relaxing unrelated protection.
Question 144
A fabric orchestrator pushes a template to the wrong Nexus Dashboard site after an inventory tag was copied between environments. The automation change must pass a preproduction test and leave a verifiable audit trail. What should the operator avoid assuming from the observed state?
- Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location.
- Valid API credentials do not make a bulk template safe for every visible site.
- Adding GPUs alone will not solve a fabric bottleneck and may increase east-west network pressure.
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
Explanation
Correct Answer
B:Valid API credentials do not make a bulk template safe for every visible site. Shared management APIs need explicit target selection; ambiguous tags can misdirect otherwise syntactically valid changes. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location. That response is associated with poap bootstrap dependencies rather than the specific nexus dashboard automation scope condition described here. For the stated failure, the preferred action is: Constrain automation targets using verified site identity and a preflight plan before bulk deployment. Relevant evidence: Inspect target site IDs, inventory assignments, proposed diffs and authorizations. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:Adding GPUs alone will not solve a fabric bottleneck and may increase east-west network pressure. This concerns ai cluster network congestion, not nexus dashboard automation scope.
D:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. That response is associated with powershell api token security rather than the specific nexus dashboard automation scope condition described here. For the stated failure, the preferred action is: Constrain automation targets using verified site identity and a preflight plan before bulk deployment. Relevant evidence: Inspect target site IDs, inventory assignments, proposed diffs and authorizations. The automation change must pass a preproduction test and leave a verifiable audit trail.
Question 145
A helpdesk operator needs to review UCS server faults but accidentally receives access to modify global SAN policies. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What is the best next implementation or troubleshooting step?
- Assign a scoped UCS administrative role that permits health visibility without SAN policy modification.
- Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key.
- Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope.
- Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings.
Explanation
Correct Answer
A:Assign a scoped UCS administrative role that permits health visibility without SAN policy modification. Compute management RBAC should separate routine inspection from high-impact infrastructure changes. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
B:Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. This concerns routing protocol keychain rollover, not UCS administrative separation.
C:Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. This concerns DHCP snooping trusted uplink, not UCS administrative separation.
D:Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings. This concerns first-hop ip/mac spoof defense, not UCS administrative separation.
Question 146
An MDS operator edits the configured zoneset but a host still cannot discover the newly authorized storage target. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. How should the implementation be validated against the original failure?
- The correct current target WWPN appears in FCNS and the authorized initiator discovers it.
- The correct active zone now includes the initiator and target, and storage discovery succeeds.
- The required VSAN becomes operational across the trunk and its name-server and login functions recover.
- Only authorized initiators see their allowed storage targets, with unrelated hosts excluded.
Explanation
Correct Answer
B:The correct active zone now includes the initiator and target, and storage discovery succeeds. This result tests the original failure rather than reporting merely that the configuration command was accepted. Configured zones and active enforced zoning can differ until the appropriate zoneset is activated. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:The correct current target WWPN appears in FCNS and the authorized initiator discovers it. This concerns fibre channel name-server entries, not zoneset activation state.
C:The required VSAN becomes operational across the trunk and its name-server and login functions recover. This concerns VSAN trunk mismatch, not zoneset activation state.
D:Only authorized initiators see their allowed storage targets, with unrelated hosts excluded. This concerns single-initiator zoning, not zoneset activation state.
Question 147
A replacement ACI leaf remains undiscovered after connecting to the spine and giving it management power. The team is preparing a controlled production change and must preserve fabric reachability. Why is the targeted engineering response justified in this situation?
- An ACI fabric must discover and register infrastructure nodes before normal tenant policy deployment.
- Programmable-logic updates can require component reset or reload even when an unrelated software patch did not.
- ACI VMM integration maps VM networks and EPGs through the virtualized domain to appropriate fabric policy.
- ACI access policies rely on a consistent domain and attachment chain before deploying the correct encapsulation.
Explanation
Correct Answer
A:An ACI fabric must discover and register infrastructure nodes before normal tenant policy deployment. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Programmable-logic updates can require component reset or reload even when an unrelated software patch did not. This concerns epld firmware maintenance, not aci fabric discovery.
C:ACI VMM integration maps VM networks and EPGs through the virtualized domain to appropriate fabric policy. That response is associated with aci vmm association rather than the specific aci fabric discovery condition described here. For the stated failure, the preferred action is: Validate fabric discovery prerequisites, physical connectivity and node registration in APIC. Relevant evidence: Inspect fabric membership, node discovery events, infra connectivity and APIC registration details. The team is preparing a controlled production change and must preserve fabric reachability.
D:ACI access policies rely on a consistent domain and attachment chain before deploying the correct encapsulation. That response is associated with aci access policy chain rather than the specific aci fabric discovery condition described here. For the stated failure, the preferred action is: Validate fabric discovery prerequisites, physical connectivity and node registration in APIC. Relevant evidence: Inspect fabric membership, node discovery events, infra connectivity and APIC registration details. The team is preparing a controlled production change and must preserve fabric reachability.
Question 148
A new VXLAN leaf advertises local VNIs but tunnels to another leaf fail because the VTEP source loopback is missing from underlay routing. The team is preparing a controlled production change and must preserve fabric reachability. What should the engineer collect before ruling out other causes?
- Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters.
- Inspect configuration diffs, change tickets, inventory assignments and last known working backups.
- Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability.
- Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization.
Explanation
Correct Answer
C:Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability. These records help distinguish the suspected failure from a superficially similar fault before modifying production. VXLAN encapsulation depends on routable IP transport between VTEP endpoints before tenant traffic can traverse it. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect SPAN source/destination selection, capture timestamps, TCP flags and any truncation or drop counters. This concerns span packet-level diagnosis, not vxlan vtep underlay reachability.
B:Inspect configuration diffs, change tickets, inventory assignments and last known working backups. This concerns fabric configuration drift, not vxlan vtep underlay reachability.
D:Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization. This concerns netflow traffic attribution, not vxlan vtep underlay reachability.
Question 149
A SAN-boot blade fails to discover the primary boot LUN even though the fibre channel interface shows link up. Operations is validating the host before approving production workload placement. What is the best next implementation or troubleshooting step?
- Assign WWPNs from a nonoverlapping pool and validate effective per-fabric vHBA identities.
- Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs.
- Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path.
- Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies.
Explanation
Correct Answer
C:Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. SAN boot requires all of the initiator, fabric zoning, target presentation and boot policy to agree. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Assign WWPNs from a nonoverlapping pool and validate effective per-fabric vHBA identities. That response is associated with wwpn pool allocation rather than the specific san boot path policy condition described here. For the stated failure, the preferred action is: Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. Relevant evidence: Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. Operations is validating the host before approving production workload placement.
B:Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs. This concerns UCS fabric redundancy, not SAN boot path policy.
D:Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies. That response is associated with server pool qualification rather than the specific san boot path policy condition described here. For the stated failure, the preferred action is: Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. Relevant evidence: Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. Operations is validating the host before approving production workload placement.
Question 150
A fabric interconnect has never exported its current UCS configuration despite recent service-profile and policy changes. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which qualification should the change record include?
- Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic.
- A high-availability label does not guarantee there is sufficient spare capacity for concurrent outages.
- Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism.
- A host operating-system backup does not replace the UCS management configuration backup.
Explanation
Correct Answer
D:A host operating-system backup does not replace the UCS management configuration backup. UCS configuration backups retain recovery information for policies and identities and should accompany approved changes. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic. This concerns compute traffic span, not UCS management backup.
B:A high-availability label does not guarantee there is sufficient spare capacity for concurrent outages. This concerns UCS firmware change sequencing, not UCS management backup.
C:Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism. This concerns chassis power and thermal monitoring, not UCS management backup.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests