Question 890
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. Which qualification should the change record include?
- Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption.
- An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines.
- Assigning an endpoint group cannot substitute for fabric-node discovery and registration.
- Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool.
Explanation
Correct Answer
C:Assigning an endpoint group cannot substitute for fabric-node discovery and registration. 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
A:Calling an image upgrade ISSU does not guarantee zero packet loss or no feature-specific disruption. This concerns nexus issu eligibility, not aci fabric discovery.
B:An existing VLAN alone does not establish the correct EPG placement for migrating virtual machines. 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:Editing the tenant's routing policy cannot fix an unattached physical-domain VLAN pool. 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 891
An operations team sees sporadic storage-path instability but its monitoring only polls device availability every five minutes. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which observations would best validate the initial diagnosis?
- Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments.
- Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations.
- Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events.
- Inspect SAN fabric health, interface utilization, link events, VSAN membership and path timelines.
Explanation
Correct Answer
D:Inspect SAN fabric health, interface utilization, link events, VSAN membership and path timelines. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Topology, fabric events and time-series indicators reveal path problems hidden by simple reachability polling. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. This concerns fibre channel port-channel consistency, not nexus dashboard SAN monitoring.
B:Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations. This concerns fcid and domain id stability, not nexus dashboard SAN monitoring.
C:Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events. This concerns fibre channel fabric login, not nexus dashboard SAN monitoring.
Question 892
A new Nexus switch starts Power On Auto Provisioning but stalls after DHCP because the boot image URL is unreachable. The automation change must pass a preproduction test and leave a verifiable audit trail. What is the best next implementation or troubleshooting step?
- Constrain automation targets using verified site identity and a preflight plan before bulk deployment.
- Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported.
- Implement documented pagination and response-error handling in the inventory API client.
- Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP.
Explanation
Correct Answer
D:Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP. POAP bootstrap depends on correct discovery and reachable provisioning artifacts, not DHCP completion alone. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A: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 poap bootstrap dependencies condition described here. For the stated failure, the preferred action is: Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP. Relevant evidence: Inspect DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs. The automation change must pass a preproduction test and leave a verifiable audit trail.
B:Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported. This concerns ansible idempotent templates, not poap bootstrap dependencies.
C:Implement documented pagination and response-error handling in the inventory API client. That response is associated with python api pagination rather than the specific poap bootstrap dependencies condition described here. For the stated failure, the preferred action is: Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP. Relevant evidence: Inspect DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs. The automation change must pass a preproduction test and leave a verifiable audit trail.
Question 893
A storage administrator must inspect FC zoning health but an inherited MDS role grants access to fabric-wide reconfiguration. Security engineering must restore the approved service without relaxing unrelated protection. What is the strongest technical basis for the recommended action?
- FC port security can restrict which device WWNs are permitted to connect through designated fabric ports.
- Role-based access control limits administrators to the commands and resources needed for their work.
- Fabric binding controls which fabric switches are allowed to join trusted SAN connections.
- Storage network RBAC limits configuration actions independently of physical access to SAN switches.
Explanation
Correct Answer
D:Storage network RBAC limits configuration actions independently of physical access to SAN switches. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. That response is associated with fibre channel port security rather than the specific mds san administrative control condition described here. For the stated failure, the preferred action is: Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement. Relevant evidence: Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs. Security engineering must restore the approved service without relaxing unrelated protection.
B:Role-based access control limits administrators to the commands and resources needed for their work. This concerns nx-os administrative RBAC, not mds SAN administrative control.
C:Fabric binding controls which fabric switches are allowed to join trusted SAN connections. That response is associated with fabric binding membership rather than the specific mds san administrative control condition described here. For the stated failure, the preferred action is: Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement. Relevant evidence: Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs. Security engineering must restore the approved service without relaxing unrelated protection.
Question 894
Latency-sensitive storage traffic shares uplinks with a large backup flow and drops rise during congestion. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What information should be inspected before the change is applied?
- Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables.
- Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps.
- Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites.
- Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries.
Explanation
Correct Answer
B:Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps. These records help distinguish the suspected failure from a superficially similar fault before modifying production. QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. This concerns UCS mac pool uniqueness, not UCS network qos policy.
C:Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites. This concerns UCS restore integrity, not UCS network qos policy.
D:Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries. This concerns SAN connectivity from blade chassis, not UCS network qos policy.
Question 895
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. Which evidence set most directly tests the suspected failure?
- Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns.
- Inspect server inventory, qualification criteria, pool membership and association failures.
- Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance.
- Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state.
Explanation
Correct Answer
D:Inspect adapter health, fault codes, service-profile inventory, event chronology and firmware state. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect capture-point support, vNIC policy, frame timestamps, queue counters and retransmission patterns. This concerns compute traffic span, not intersight alert triage.
B:Inspect server inventory, qualification criteria, pool membership and association failures. This concerns server pool qualification, not intersight alert triage.
C:Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. This concerns chassis power and thermal monitoring, not intersight alert triage.
Question 896
Fabric merges after a switch replacement intermittently disrupt paths because two switches have a conflicting principal domain assignment. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which result would best confirm that the remediation worked?
- The target feature configuration is consistent on all intended switches with an auditable committed state.
- Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths.
- The initiator appears in FLOGI with an FCID and can proceed to authorized name-server discovery.
- All expected FC interfaces are active members and fabric traffic remains available after a link failure.
Explanation
Correct Answer
B:Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths. This result tests the original failure rather than reporting merely that the configuration command was accepted. FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:The target feature configuration is consistent on all intended switches with an auditable committed state. This concerns cisco fabric services distribution, not fcid and domain id stability.
C:The initiator appears in FLOGI with an FCID and can proceed to authorized name-server discovery. This concerns fibre channel fabric login, not fcid and domain id stability.
D:All expected FC interfaces are active members and fabric traffic remains available after a link failure. This concerns fibre channel port-channel consistency, not fcid and domain id stability.
Question 897
A hypervisor installation leaves a virtual media image first in a UCS boot policy, causing repeated setup after power cycles. Operations is validating the host before approving production workload placement. Which observations would best validate the initial diagnosis?
- Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs.
- Inspect server inventory, qualification criteria, pool membership and association failures.
- Inspect effective boot order, mapped virtual media state and host boot history.
- Inspect parent templates, derived profiles, policy inheritance and pending association changes.
Explanation
Correct Answer
C:Inspect effective boot order, mapped virtual media state and host boot history. These records help distinguish the suspected failure from a superficially similar fault before modifying production. A persistent virtual-media boot entry can supersede the production storage or disk target on later restarts. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. This concerns UCS blade chassis IOM discovery, not boot order and removable media.
B:Inspect server inventory, qualification criteria, pool membership and association failures. That response is associated with server pool qualification rather than the specific boot order and removable media condition described here. For the stated failure, the preferred action is: Restore the intended production boot-device order and detach temporary install media from the active policy. Relevant evidence: Inspect effective boot order, mapped virtual media state and host boot history. Operations is validating the host before approving production workload placement.
D:Inspect parent templates, derived profiles, policy inheritance and pending association changes. That response is associated with updating service-profile templates rather than the specific boot order and removable media condition described here. For the stated failure, the preferred action is: Restore the intended production boot-device order and detach temporary install media from the active policy. Relevant evidence: Inspect effective boot order, mapped virtual media state and host boot history. Operations is validating the host before approving production workload placement.
Question 898
A SAN supervisor EPLD change is scheduled during peak transaction load without assessing module reload requirements. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which result would best confirm that the remediation worked?
- Post-update EPLD versions are correct and tested host multipath failover retains service during planned disruption.
- The target feature configuration is consistent on all intended switches with an auditable committed state.
- Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths.
- All expected FC interfaces are active members and fabric traffic remains available after a link failure.
Explanation
Correct Answer
A:Post-update EPLD versions are correct and tested host multipath failover retains service during planned disruption. This result tests the original failure rather than reporting merely that the configuration command was accepted. An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:The target feature configuration is consistent on all intended switches with an auditable committed state. This concerns cisco fabric services distribution, not mds epld update impact.
C:Domain IDs become unique and stable, fabric merge completes and attached initiators retain valid paths. This concerns fcid and domain id stability, not mds epld update impact.
D:All expected FC interfaces are active members and fabric traffic remains available after a link failure. This concerns fibre channel port-channel consistency, not mds epld update impact.
Question 899
A blade has two configured vNICs, yet a failed fabric interconnect isolates all management and application traffic. Operations is validating the host before approving production workload placement. Which technical principle best explains the recommended response?
- Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path.
- Physical power or cooling constraints can throttle compute even when guest metrics show no software error.
- A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry.
- The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades.
Explanation
Correct Answer
A:Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:Physical power or cooling constraints can throttle compute even when guest metrics show no software error. This concerns chassis power and thermal monitoring, not UCS fabric redundancy.
C:A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry. That response is associated with ucs vlan pool and template rather than the specific ucs fabric redundancy condition described here. For the stated failure, the preferred action is: Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs. Relevant evidence: Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding. Operations is validating the host before approving production workload placement.
D:The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. That response is associated with ucs blade chassis iom discovery rather than the specific ucs fabric redundancy condition described here. For the stated failure, the preferred action is: Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs. Relevant evidence: Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding. Operations is validating the host before approving production workload placement.
Question 900
An unauthorized initiator plugs into an available SAN switch port and attempts fabric login using an unapproved WWPN. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which technical principle best explains the recommended response?
- Storage network RBAC limits configuration actions independently of physical access to SAN switches.
- FC port security can restrict which device WWNs are permitted to connect through designated fabric ports.
- Fabric binding controls which fabric switches are allowed to join trusted SAN connections.
- MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms.
Explanation
Correct Answer
B:FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Storage network RBAC limits configuration actions independently of physical access to SAN switches. This concerns mds SAN administrative control, not fibre channel port security.
C:Fabric binding controls which fabric switches are allowed to join trusted SAN connections. This concerns fabric binding membership, not fibre channel port security.
D:MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms. This concerns MACsec protection scope, not fibre channel port security.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests