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.
Question 231
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. Which limitation prevents the team from overgeneralizing this result?
- Valid API credentials do not make a bulk template safe for every visible site.
- Raising a page-size value without checking API limits does not guarantee complete retrieval.
- Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location.
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
Explanation
Correct Answer
C:Automatically accepting an untrusted bootstrap image is not justified merely because DHCP supplied its location. 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:Valid API credentials do not make a bulk template safe for every visible site. 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:Raising a page-size value without checking API limits does not guarantee complete retrieval. 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.
D:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. This concerns powershell api token security, not poap bootstrap dependencies.
Question 232
An IPv6 fabric link has global IPv6 addresses but no OSPFv3 adjacency after a replacement uplink was enabled. The team is preparing a controlled production change and must preserve fabric reachability. What information should be inspected before the change is applied?
- Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets.
- Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization.
- Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI.
- Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers.
Explanation
Correct Answer
A:Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets. These records help distinguish the suspected failure from a superficially similar fault before modifying production. OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Inspect exporter/collector status, flow sample records, talker pairs and time-aligned interface utilization. This concerns netflow traffic attribution, not ospfv3 IPv6 neighbor discovery.
C:Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. That response is associated with mp-bgp evpn route learning rather than the specific ospfv3 ipv6 neighbor discovery condition described here. For the stated failure, the preferred action is: Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match. Relevant evidence: Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets. The team is preparing a controlled production change and must preserve fabric reachability.
D:Inspect neighbor state, interface area assignments, hello parameters and interface MTU on both peers. That response is associated with ospf area compatibility rather than the specific ospfv3 ipv6 neighbor discovery condition described here. For the stated failure, the preferred action is: Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match. Relevant evidence: Check IPv6 link-local addresses, OSPFv3 interface participation, area settings and protocol packets. The team is preparing a controlled production change and must preserve fabric reachability.
Question 233
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. What caveat is critical when interpreting a successful remediation?
- Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict.
- An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric.
- Assuming that every local command is distributed automatically can leave peers inconsistent.
- Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric.
Explanation
Correct Answer
A:Renaming device aliases does not resolve an underlying Fibre Channel domain ID conflict. 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
B:An ordinary Fibre Channel zone does not by itself create a separate control-plane fabric. This concerns VSAN isolation, not fcid and domain id stability.
C:Assuming that every local command is distributed automatically can leave peers inconsistent. This concerns cisco fabric services distribution, not fcid and domain id stability.
D:Forcing suspended links into service without correcting compatibility can destabilize a SAN fabric. This concerns fibre channel port-channel consistency, not fcid and domain id stability.
Question 234
A network inventory script reports only the first hundred switches even though Nexus Dashboard shows more devices. The automation change must pass a preproduction test and leave a verifiable audit trail. Which controlled change is most appropriate given the evidence?
- Validate API responses and explicitly handle missing data before calculating health status.
- Implement documented pagination and response-error handling in the inventory API client.
- Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported.
- Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP.
Explanation
Correct Answer
B:Implement documented pagination and response-error handling in the inventory API client. Paginated REST endpoints may return only a subset of objects unless clients follow continuation information. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Validate API responses and explicitly handle missing data before calculating health status. This concerns on-box python exception handling, not python api pagination.
C:Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported. That response is associated with ansible idempotent templates rather than the specific python api pagination condition described here. For the stated failure, the preferred action is: Implement documented pagination and response-error handling in the inventory API client. Relevant evidence: Inspect response metadata, page limits, next tokens, error responses and known inventory counts. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Validate the DHCP options, image/script availability and bootstrap transport path before restarting POAP. That response is associated with poap bootstrap dependencies rather than the specific python api pagination condition described here. For the stated failure, the preferred action is: Implement documented pagination and response-error handling in the inventory API client. Relevant evidence: Inspect response metadata, page limits, next tokens, error responses and known inventory counts. The automation change must pass a preproduction test and leave a verifiable audit trail.
Question 235
A UCS blade shows unexplained throttling during compute peaks despite normal guest operating-system logs. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What should the operator avoid assuming from the observed state?
- Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism.
- Suppressing an alert does not remove the underlying component fault or its availability risk.
- Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic.
- Configuring only a server profile does not establish the upstream domain-fabric configuration.
Explanation
Correct Answer
A:Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism. Physical power or cooling constraints can throttle compute even when guest metrics show no software error. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:Suppressing an alert does not remove the underlying component fault or its availability risk. This concerns intersight alert triage, not chassis power and thermal monitoring.
C:Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic. This concerns compute traffic span, not chassis power and thermal monitoring.
D:Configuring only a server profile does not establish the upstream domain-fabric configuration. This concerns intersight domain profile, not chassis power and thermal monitoring.
Question 236
A four-link server port-channel forwards on two members because the other members use incompatible trunk settings. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. Which intervention most directly addresses the stated condition?
- Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop.
- Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently.
- Align the switchport and LACP parameters across members before attempting to force them into the bundle.
- Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match.
Explanation
Correct Answer
C:Align the switchport and LACP parameters across members before attempting to force them into the bundle. LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop. This concerns rstp blocked uplink, not lacp member mismatch.
B:Restore the peer-link and validate keepalive and vPC consistency rather than forcing both peers to forward independently. This concerns vpc peer-link recovery, not lacp member mismatch.
D:Verify OSPFv3 is enabled on the intended interface and that IPv6 link-local reachability and area configuration match. This concerns ospfv3 IPv6 neighbor discovery, not lacp member mismatch.
Question 237
During an OSPF key rollover, one peer begins rejecting signed hello packets even though the links remain up. Security engineering must restore the approved service without relaxing unrelated protection. Which test result best demonstrates restoration of the intended behavior?
- The link carries encrypted authenticated traffic and rejects frames without valid link security associations.
- The adjacency remains Full across the rollover while old credentials are retired after verification.
- Spoofed source addresses are dropped while approved host traffic continues normally.
- Authorized recovery login works during a controlled AAA outage and normal centralized authentication resumes afterward.
Explanation
Correct Answer
B:The adjacency remains Full across the rollover while old credentials are retired after verification. This result tests the original failure rather than reporting merely that the configuration command was accepted. Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:The link carries encrypted authenticated traffic and rejects frames without valid link security associations. That response is associated with macsec protection scope rather than the specific routing protocol keychain rollover condition described here. For the stated failure, the preferred action is: Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. Relevant evidence: Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state. Security engineering must restore the approved service without relaxing unrelated protection.
C:Spoofed source addresses are dropped while approved host traffic continues normally. That response is associated with first-hop ip/mac spoof defense rather than the specific routing protocol keychain rollover condition described here. For the stated failure, the preferred action is: Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. Relevant evidence: Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state. Security engineering must restore the approved service without relaxing unrelated protection.
D:Authorized recovery login works during a controlled AAA outage and normal centralized authentication resumes afterward. This concerns centralized AAA fallback, not routing protocol keychain rollover.
Question 238
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. Which evidence set most directly tests the suspected failure?
- Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations.
- Inspect MDS platform release notes, EPLD package compatibility, reload dependencies and alternate paths.
- Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices.
- Inspect CFS peers, lock ownership, pending changes, feature status and activation records.
Explanation
Correct Answer
D:Inspect CFS peers, lock ownership, pending changes, feature status and activation records. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations. This concerns fcid and domain id stability, not cisco fabric services distribution.
B:Inspect MDS platform release notes, EPLD package compatibility, reload dependencies and alternate paths. This concerns mds epld update impact, not cisco fabric services distribution.
C:Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. This concerns single-initiator zoning, not cisco fabric services distribution.
Question 239
A UCS blade shows unexplained throttling during compute peaks despite normal guest operating-system logs. Operations is validating the host before approving production workload placement. Which result would best confirm that the remediation worked?
- Hardware environmental faults are resolved and sustained compute tests no longer show thermal throttling.
- Only the approved profile scope receives the tested update, with unrelated services preserved.
- A controlled capture identifies whether retransmissions coincide with drops or network reordering.
- The affected adapter fault clears after a supported fix and workload connectivity validates correctly.
Explanation
Correct Answer
A:Hardware environmental faults are resolved and sustained compute tests no longer show thermal throttling. This result tests the original failure rather than reporting merely that the configuration command was accepted. Physical power or cooling constraints can throttle compute even when guest metrics show no software error. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:Only the approved profile scope receives the tested update, with unrelated services preserved. This concerns updating service-profile templates, not chassis power and thermal monitoring.
C:A controlled capture identifies whether retransmissions coincide with drops or network reordering. That response is associated with compute traffic span rather than the specific chassis power and thermal monitoring condition described here. For the stated failure, the preferred action is: Inspect chassis power, fan and thermal faults before changing application performance settings. Relevant evidence: Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. Operations is validating the host before approving production workload placement.
D:The affected adapter fault clears after a supported fix and workload connectivity validates correctly. That response is associated with intersight alert triage rather than the specific chassis power and thermal monitoring condition described here. For the stated failure, the preferred action is: Inspect chassis power, fan and thermal faults before changing application performance settings. Relevant evidence: Inspect chassis health, power budgets, fan alarms, temperature sensors and affected blade performance. Operations is validating the host before approving production workload placement.
Question 240
Two switches exchange frames over an untrusted fiber run, and security requirements call for link-layer encryption. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which explanation most directly accounts for the required correction?
- IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses.
- DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers.
- MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms.
- Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency.
Explanation
Correct Answer
C:MACsec protects frames on a supported Ethernet link using negotiated encryption and integrity mechanisms. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:IP source validation uses trusted bindings to prevent endpoints from impersonating unassigned source addresses. This concerns first-hop ip/mac spoof defense, not MACsec protection scope.
B:DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. This concerns DHCP snooping trusted uplink, not MACsec protection scope.
D:Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. This concerns routing protocol keychain rollover, not MACsec protection scope.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests