Question 220
An ISL trunk is up but one VSAN loses connectivity because it is missing from the allowed or operational VSAN set. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which technical principle best explains the recommended response?
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
Explanation
Correct Answer
A:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. That response is associated with vsan isolation rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. This concerns fibre channel port-channel consistency, not VSAN trunk mismatch.
D:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. That response is associated with wwpn versus wwnn rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 221
A contractor must view Nexus interface health but currently has a role that can change routing and security configuration. A follow-up access review asks the team to validate the same boundary with a controlled negative test. How should the implementation be validated against the original failure?
- The contractor can view interface health but an attempted configuration change is denied and logged.
- Authorized recovery login works during a controlled AAA outage and normal centralized authentication resumes afterward.
- Authorized static hosts pass ARP inspection while forged bindings remain blocked.
- Only the approved application ports work between the two EPGs while nonapproved flows remain blocked.
Explanation
Correct Answer
A:The contractor can view interface health but an attempted configuration change is denied and logged. This result tests the original failure rather than reporting merely that the configuration command was accepted. Role-based access control limits administrators to the commands and resources needed for their work. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
B:Authorized recovery login works during a controlled AAA outage and normal centralized authentication resumes afterward. This concerns centralized AAA fallback, not nx-os administrative RBAC.
C:Authorized static hosts pass ARP inspection while forged bindings remain blocked. This concerns dynamic ARP inspection source of truth, not nx-os administrative RBAC.
D:Only the approved application ports work between the two EPGs while nonapproved flows remain blocked. This concerns aci inter-epg contract, not nx-os administrative RBAC.
Question 222
A UCS-X chassis is physically installed but policies authored for a legacy UCS Manager workflow cannot be assigned to its server profiles. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What is the best next implementation or troubleshooting step?
- Check organization membership and resource-group scope before broadening permissions globally.
- Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status.
- Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs.
- Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies.
Explanation
Correct Answer
D:Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies. UCS-X in Intersight Managed Mode uses Intersight-defined policies and profiles rather than unmodified UCS Manager assumptions. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Check organization membership and resource-group scope before broadening permissions globally. This concerns intersight organization scope, not UCS-x intersight managed mode.
B:Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status. This concerns intersight domain profile, not UCS-x intersight managed mode.
C:Validate that fabric A and fabric B interfaces have independent working uplinks and correctly bound vNICs. This concerns UCS fabric redundancy, not UCS-x intersight managed mode.
Question 223
An administrator imports a service-profile template and two new server identities unexpectedly request an overlapping MAC range. Operations is validating the host before approving production workload placement. What is the strongest technical basis for the recommended action?
- QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices.
- A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry.
- A blade vHBA needs an operational fabric path and correct VSAN association before a fabric login can occur.
- UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning.
Explanation
Correct Answer
D:UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:QoS treatment is effective only when marking, queue allocation and congestion behavior align across involved devices. That response is associated with ucs network qos policy rather than the specific ucs mac pool uniqueness condition described here. For the stated failure, the preferred action is: Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment. Relevant evidence: Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. Operations is validating the host before approving production workload placement.
B: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 mac pool uniqueness condition described here. For the stated failure, the preferred action is: Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment. Relevant evidence: Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. Operations is validating the host before approving production workload placement.
C:A blade vHBA needs an operational fabric path and correct VSAN association before a fabric login can occur. This concerns SAN connectivity from blade chassis, not UCS mac pool uniqueness.
Question 224
After staging a server firmware upgrade, the adapter and BIOS target versions differ from the supported hardware compatibility matrix. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which evidence set most directly tests the suspected failure?
- Inspect backup type, completion logs, storage location, retention and access permissions.
- Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites.
- Inspect HCL guidance, firmware policy contents, host driver versions and maintenance impact.
- Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs.
Explanation
Correct Answer
C:Inspect HCL guidance, firmware policy contents, host driver versions and maintenance impact. These records help distinguish the suspected failure from a superficially similar fault before modifying production. A server and adapter firmware combination must be supported for its hardware and operating environment. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Inspect backup type, completion logs, storage location, retention and access permissions. This concerns UCS management backup, not UCS firmware compatibility.
B:Inspect backup timestamp, pool assignments, profile associations and supported restore-mode prerequisites. This concerns UCS restore integrity, not UCS firmware compatibility.
D:Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. This concerns UCS blade chassis IOM discovery, not UCS firmware compatibility.
Question 225
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. Which result would best confirm that the remediation worked?
- Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state.
- The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault.
- Remote VTEP addresses resolve through the underlay and encapsulated tenant frames reach the remote leaf.
- All intended links join the same logical bundle and traffic is distributed without individual member flaps.
Explanation
Correct Answer
C:Remote VTEP addresses resolve through the underlay and encapsulated tenant frames reach the remote leaf. This result tests the original failure rather than reporting merely that the configuration command was accepted. 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:Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state. This concerns vpc peer-link recovery, not vxlan vtep underlay reachability.
B:The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault. This concerns rstp blocked uplink, not vxlan vtep underlay reachability.
D:All intended links join the same logical bundle and traffic is distributed without individual member flaps. This concerns lacp member mismatch, not vxlan vtep underlay reachability.
Question 226
A Nexus access VLAN with Dynamic ARP Inspection enabled begins dropping legitimate hosts that use static addressing. Security engineering must restore the approved service without relaxing unrelated protection. What should the operator avoid assuming from the observed state?
- Changing the entire subnet ACL is not equivalent to targeting a specific VM attribute-defined subset.
- A fallback local account needs tight protection and audit controls rather than indefinite shared use.
- Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception.
- Trusting all access ports would negate the primary protection against unauthorized DHCP servers.
Explanation
Correct Answer
C:Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception. DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Changing the entire subnet ACL is not equivalent to targeting a specific VM attribute-defined subset. That response is associated with aci microsegmentation selector rather than the specific dynamic arp inspection source of truth condition described here. For the stated failure, the preferred action is: Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. Relevant evidence: Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. Security engineering must restore the approved service without relaxing unrelated protection.
B:A fallback local account needs tight protection and audit controls rather than indefinite shared use. This concerns centralized AAA fallback, not dynamic ARP inspection source of truth.
D:Trusting all access ports would negate the primary protection against unauthorized DHCP servers. That response is associated with dhcp snooping trusted uplink rather than the specific dynamic arp inspection source of truth condition described here. For the stated failure, the preferred action is: Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. Relevant evidence: Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. Security engineering must restore the approved service without relaxing unrelated protection.
Question 227
A compromised endpoint sends frames with another host's IP address on the same access VLAN after DHCP snooping is enabled. Security engineering must restore the approved service without relaxing unrelated protection. Which explanation most directly accounts for the required correction?
- DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers.
- DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding.
- IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses.
- Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency.
Explanation
Correct Answer
C:IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. That response is associated with dhcp snooping trusted uplink rather than the specific first-hop ip/mac spoof defense condition described here. For the stated failure, the preferred action is: Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings. Relevant evidence: Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. Security engineering must restore the approved service without relaxing unrelated protection.
B:DAI verifies ARP bindings using trusted information and may reject legitimate fixed-address hosts without an authorized binding. This concerns dynamic ARP inspection source of truth, not first-hop ip/mac spoof defense.
D:Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. That response is associated with routing protocol keychain rollover rather than the specific first-hop ip/mac spoof defense condition described here. For the stated failure, the preferred action is: Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings. Relevant evidence: Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. Security engineering must restore the approved service without relaxing unrelated protection.
Question 228
An ISL trunk is up but one VSAN loses connectivity because it is missing from the allowed or operational VSAN set. A storage change board requires a traceable diagnosis before allowing further fabric changes. What post-change observation gives the strongest evidence of success?
- Each team's initiators and targets register only within the approved VSAN and access boundaries.
- 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.
- The active zoneset contains the actual registered port WWPNs and the host discovers its target.
Explanation
Correct Answer
B:The required VSAN becomes operational across the trunk and its name-server and login functions recover. This result tests the original failure rather than reporting merely that the configuration command was accepted. A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Each team's initiators and targets register only within the approved VSAN and access boundaries. That response is associated with vsan isolation rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
C:Only authorized initiators see their allowed storage targets, with unrelated hosts excluded. This concerns single-initiator zoning, not VSAN trunk mismatch.
D:The active zoneset contains the actual registered port WWPNs and the host discovers its target. That response is associated with wwpn versus wwnn rather than the specific vsan trunk mismatch condition described here. For the stated failure, the preferred action is: Align trunk allowed VSANs and verify the operational VSAN membership end to end. Relevant evidence: Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Question 229
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 caveat is critical when interpreting a successful remediation?
- An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment.
- An RP mapping correction will not compensate for broken RPF reachability to the multicast source.
- Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP.
- A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly.
Explanation
Correct Answer
C:Adding an EVPN route target cannot overcome a missing underlay IP path to the remote VTEP. 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:An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment. This concerns first-hop gateway failover, not vxlan vtep underlay reachability.
B:An RP mapping correction will not compensate for broken RPF reachability to the multicast source. This concerns PIM multicast rendezvous point, not vxlan vtep underlay reachability.
D:A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly. This concerns bum replication behavior, not vxlan vtep underlay reachability.
Question 230
An on-box NX-OS Python maintenance script interprets a missing interface counter as zero and incorrectly reports healthy operation. The automation change must pass a preproduction test and leave a verifiable audit trail. What should the engineer collect before ruling out other causes?
- Inspect response status and body, user roles, NX-API feature state and endpoint documentation.
- Inspect API logs, resource identifiers, HTTP response history and current running object state.
- Inspect job definition, scheduler timetable, execution status and change-window policy.
- Inspect command return status, payload schema, missing fields, tracebacks and data freshness.
Explanation
Correct Answer
D:Inspect command return status, payload schema, missing fields, tracebacks and data freshness. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Automation must distinguish unavailable telemetry from a real numeric zero to avoid false success reports. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Inspect response status and body, user roles, NX-API feature state and endpoint documentation. That response is associated with nx-api request authorization rather than the specific on-box python exception handling condition described here. For the stated failure, the preferred action is: Validate API responses and explicitly handle missing data before calculating health status. Relevant evidence: Inspect command return status, payload schema, missing fields, tracebacks and data freshness. The automation change must pass a preproduction test and leave a verifiable audit trail.
B:Inspect API logs, resource identifiers, HTTP response history and current running object state. That response is associated with rest api retries and idempotence rather than the specific on-box python exception handling condition described here. For the stated failure, the preferred action is: Validate API responses and explicitly handle missing data before calculating health status. Relevant evidence: Inspect command return status, payload schema, missing fields, tracebacks and data freshness. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:Inspect job definition, scheduler timetable, execution status and change-window policy. This concerns nx-os scheduler jobs, not on-box python exception handling.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests