Question 870
A UCS blade chassis appears in inventory but several blades remain undiscovered after an I/O module replacement. Operations is validating the host before approving production workload placement. What should the operator avoid assuming from the observed state?
- Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template.
- Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link.
- The newest firmware for each component is not necessarily a supported combination when mixed arbitrarily.
- Two vNIC objects on the same failed upstream path do not provide true physical redundancy.
Explanation
Correct Answer
B:Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link. The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template. That response is associated with ucs vlan pool and template rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
C:The newest firmware for each component is not necessarily a supported combination when mixed arbitrarily. This concerns UCS firmware compatibility, not UCS blade chassis IOM discovery.
D:Two vNIC objects on the same failed upstream path do not provide true physical redundancy. That response is associated with ucs fabric redundancy rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
Question 871
A storage host loses path visibility after a target port migration although the physical target link is healthy. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which intervention most directly addresses the stated condition?
- Check the CFS distribution scope and commit or activation workflow for the affected feature.
- Activate the intended zoneset on the correct VSAN and validate its active membership.
- 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.
Explanation
Correct Answer
C:Reconcile FCNS registrations and target identity changes before recreating the entire VSAN. The fabric name server reflects registered port identities and can reveal whether the expected target is visible. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Check the CFS distribution scope and commit or activation workflow for the affected feature. This concerns cisco fabric services distribution, not fibre channel name-server entries.
B:Activate the intended zoneset on the correct VSAN and validate its active membership. That response is associated with zoneset activation state rather than the specific fibre channel name-server entries condition described here. For the stated failure, the preferred action is: Reconcile FCNS registrations and target identity changes before recreating the entire VSAN. Relevant evidence: Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. That response is associated with device alias maintenance rather than the specific fibre channel name-server entries condition described here. For the stated failure, the preferred action is: Reconcile FCNS registrations and target identity changes before recreating the entire VSAN. Relevant evidence: Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 872
A SAN supervisor EPLD change is scheduled during peak transaction load without assessing module reload requirements. A storage change board requires a traceable diagnosis before allowing further fabric changes. What should the engineer do first to address the observed failure?
- Use the correct initiator and target port WWPNs when creating the required zone memberships.
- Align trunk allowed VSANs and verify the operational VSAN membership end to end.
- Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets.
- Determine EPLD component impact and isolate maintenance to a window with healthy alternate fabric paths.
Explanation
Correct Answer
D:Determine EPLD component impact and isolate maintenance to a window with healthy alternate fabric paths. An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Use the correct initiator and target port WWPNs when creating the required zone memberships. This concerns wwpn versus wwnn, not mds epld update impact.
B:Align trunk allowed VSANs and verify the operational VSAN membership end to end. This concerns VSAN trunk mismatch, not mds epld update impact.
C:Create and verify separate VSAN assignments for the teams' relevant FC interfaces and zonesets. This concerns VSAN isolation, not mds epld update impact.
Question 873
A compromised endpoint sends frames with another host's IP address on the same access VLAN after DHCP snooping is enabled. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What caveat is critical when interpreting a successful remediation?
- Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception.
- Enabling only an ARP inspection check may not validate every IP data packet's source identity.
- Trusting all access ports would negate the primary protection against unauthorized DHCP servers.
- Increasing OSPF dead timers does not make incompatible authentication keys acceptable.
Explanation
Correct Answer
B:Enabling only an ARP inspection check may not validate every IP data packet's source identity. IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A: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 first-hop ip/mac spoof defense.
C:Trusting all access ports would negate the primary protection against unauthorized DHCP servers. This concerns DHCP snooping trusted uplink, not first-hop ip/mac spoof defense.
D:Increasing OSPF dead timers does not make incompatible authentication keys acceptable. This concerns routing protocol keychain rollover, not first-hop ip/mac spoof defense.
Question 874
A blade's vHBA is configured but the upstream SAN fabric never sees its WWPN login. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which explanation most directly accounts for the required correction?
- The effective boot order and accessible target devices determine which source a Cisco server attempts during initialization.
- QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices.
- A blade vHBA needs an operational fabric path and correct VSAN association before a fabric login can occur.
- Unique WWPN identities let SAN switches and arrays distinguish initiators and apply zoning and masking predictably.
Explanation
Correct Answer
C:A blade vHBA needs an operational fabric path and correct VSAN association before a fabric login can occur. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:The effective boot order and accessible target devices determine which source a Cisco server attempts during initialization. This concerns c-series boot policy alignment, not SAN connectivity from blade chassis.
B:QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices. This concerns UCS network qos policy, not SAN connectivity from blade chassis.
D:Unique WWPN identities let SAN switches and arrays distinguish initiators and apply zoning and masking predictably. This concerns wwpn pool allocation, not SAN connectivity from blade chassis.
Question 875
A new Fibre Channel host is connected to an MDS switch but never receives a fabric identifier and cannot discover targets. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which explanation most directly accounts for the required correction?
- FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation.
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- An initiator must complete fabric login and receive an FCID before normal fabric services can identify it.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
Explanation
Correct Answer
C:An initiator must complete fabric login and receive an FCID before normal fabric services can identify it. 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 fabric login condition described here. For the stated failure, the preferred action is: Validate physical FC link and initiator FLOGI registration before changing storage-array masking. Relevant evidence: Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events. A storage change board requires a traceable diagnosis before allowing further fabric changes.
B:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. This concerns VSAN trunk mismatch, not fibre channel fabric login.
D:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. That response is associated with fibre channel port-channel consistency rather than the specific fibre channel fabric login condition described here. For the stated failure, the preferred action is: Validate physical FC link and initiator FLOGI registration before changing storage-array masking. Relevant evidence: Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 876
A new Fibre Channel host is connected to an MDS switch but never receives a fabric identifier and cannot discover targets. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What caveat is critical when interpreting a successful remediation?
- 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.
- Assuming that every local command is distributed automatically can leave peers inconsistent.
- Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict.
Explanation
Correct Answer
A:A target LUN mapping cannot repair a failed physical or fabric login on the initiator port. An initiator must complete fabric login and receive an FCID before normal fabric services can identify it. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric. This concerns fibre channel port-channel consistency, not fibre channel fabric login.
C:Assuming that every local command is distributed automatically can leave peers inconsistent. This concerns cisco fabric services distribution, not fibre channel fabric login.
D:Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict. This concerns fcid and domain id stability, not fibre channel fabric login.
Question 877
Intersight flags a critical adapter fault but the operations dashboard also shows an unrelated high CPU alert. Operations is validating the host before approving production workload placement. What should the operator avoid assuming from the observed state?
- Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic.
- Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link.
- Suppressing an alert does not remove the underlying component fault or its availability risk.
- Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism.
Explanation
Correct Answer
C:Suppressing an alert does not remove the underlying component fault or its availability risk. Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause. Operations is validating the host before approving production workload placement.
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 intersight alert triage.
B:Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link. This concerns UCS blade chassis IOM discovery, not intersight alert triage.
D:Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism. This concerns chassis power and thermal monitoring, not intersight alert triage.
Question 878
An MDS operator edits the configured zoneset but a host still cannot discover the newly authorized storage target. A storage change board requires a traceable diagnosis before allowing further fabric changes. What is the best next implementation or troubleshooting step?
- Activate the intended zoneset on the correct VSAN and validate its active membership.
- Check the CFS distribution scope and commit or activation workflow for the affected feature.
- Reconcile FCNS registrations and target identity changes before recreating the entire VSAN.
- Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone.
Explanation
Correct Answer
A:Activate the intended zoneset on the correct VSAN and validate its active membership. Configured zones and active enforced zoning can differ until the appropriate zoneset is activated. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:Check the CFS distribution scope and commit or activation workflow for the affected feature. This concerns cisco fabric services distribution, not zoneset activation state.
C: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 zoneset activation state condition described here. For the stated failure, the preferred action is: Activate the intended zoneset on the correct VSAN and validate its active membership. Relevant evidence: Inspect active zoneset, configured zoneset, VSAN ID and activation history. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone. That response is associated with single-initiator zoning rather than the specific zoneset activation state condition described here. For the stated failure, the preferred action is: Activate the intended zoneset on the correct VSAN and validate its active membership. Relevant evidence: Inspect active zoneset, configured zoneset, VSAN ID and activation history. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 879
A new C-Series rack server powers on but its management controller cannot be reached from the secure operations subnet. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which controlled change is most appropriate given the evidence?
- Stage and review the template relationship and scope before applying an impactful shared-policy change.
- Validate the CIMC management address, uplink, VLAN and access path before attempting OS deployment.
- 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
B:Validate the CIMC management address, uplink, VLAN and access path before attempting OS deployment. The CIMC out-of-band interface requires correctly configured management connectivity independent of the installed server operating system. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Stage and review the template relationship and scope before applying an impactful shared-policy change. This concerns updating service-profile templates, not UCS c-series cimc reachability.
C:Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. This concerns SAN boot path policy, not UCS c-series cimc reachability.
D:Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies. This concerns server pool qualification, not UCS c-series cimc reachability.
Question 880
A Python client receives HTTP 403 from NX-API even though it can reach the management address over HTTPS. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which evidence set most directly tests the suspected failure?
- Inspect command return status, payload schema, missing fields, tracebacks and data freshness.
- Inspect response status and body, user roles, NX-API feature state and endpoint documentation.
- Inspect Ansible change output, module behavior, running configurations and intended-state version control.
- Inspect Guest Shell availability, mount mappings, file locations, network access and executed command output.
Explanation
Correct Answer
B:Inspect response status and body, user roles, NX-API feature state and endpoint documentation. These records help distinguish the suspected failure from a superficially similar fault before modifying production. An HTTP 403 indicates a reachable endpoint has refused the request under its authorization controls. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Inspect command return status, payload schema, missing fields, tracebacks and data freshness. This concerns on-box python exception handling, not nx-api request authorization.
C:Inspect Ansible change output, module behavior, running configurations and intended-state version control. This concerns ansible idempotent templates, not nx-api request authorization.
D:Inspect Guest Shell availability, mount mappings, file locations, network access and executed command output. This concerns guest shell isolation, not nx-api request authorization.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests