Question 530
Two production Nexus peers have drifted in their intended interface templates after unreviewed local commands were applied. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What should the operator avoid assuming from the observed state?
- Expanding import targets indiscriminately can leak routes across security and tenancy boundaries.
- Sampled flow records may underrepresent small or short flows and do not contain every packet payload.
- An oversubscribed SPAN destination can drop mirrored frames, so a capture is not necessarily complete.
- A configuration backup alone does not prove the running state matches approved policy.
Explanation
Correct Answer
D:A configuration backup alone does not prove the running state matches approved policy. Configuration management detects and remediates unauthorized deviations rather than trusting the most recent device state. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Expanding import targets indiscriminately can leak routes across security and tenancy boundaries. This concerns mp-BGP tenant route import, not fabric configuration drift.
B:Sampled flow records may underrepresent small or short flows and do not contain every packet payload. This concerns netflow traffic attribution, not fabric configuration drift.
C:An oversubscribed SPAN destination can drop mirrored frames, so a capture is not necessarily complete. This concerns span packet-level diagnosis, not fabric configuration drift.
Question 531
A C-Series host repeatedly boots local media even though its approved UCS policy specifies a SAN boot target. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. How should the implementation be validated against the original failure?
- The server locates the approved boot target and starts consistently through planned reboots.
- Only the approved profile scope receives the tested update, with unrelated services preserved.
- The host starts from its approved production device through repeated controlled reboots.
- The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles.
Explanation
Correct Answer
A:The server locates the approved boot target and starts consistently through planned reboots. This result tests the original failure rather than reporting merely that the configuration command was accepted. The effective boot order and accessible target devices determine which source a Cisco server attempts during initialization. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
B:Only the approved profile scope receives the tested update, with unrelated services preserved. This concerns updating service-profile templates, not c-series boot policy alignment.
C:The host starts from its approved production device through repeated controlled reboots. This concerns boot order and removable media, not c-series boot policy alignment.
D:The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles. This concerns UCS-x intersight managed mode, not c-series boot policy alignment.
Question 532
An ISL trunk is up but one VSAN loses connectivity because it is missing from the allowed or operational VSAN set. 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?
- Each team's initiators and targets register only within the approved VSAN and access boundaries.
- The active zoneset contains the actual registered port WWPNs and the host discovers its target.
- The required VSAN becomes operational across the trunk and its name-server and login functions recover.
- The approved client mounts the correct export with intended read/write access and no overbroad client allowance.
Explanation
Correct Answer
C: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. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Each team's initiators and targets register only within the approved VSAN and access boundaries. This concerns VSAN isolation, not VSAN trunk mismatch.
B:The active zoneset contains the actual registered port WWPNs and the host discovers its target. This concerns wwpn versus wwnn, not VSAN trunk mismatch.
D:The approved client mounts the correct export with intended read/write access and no overbroad client allowance. This concerns nfs export permissions, not VSAN trunk mismatch.
Question 533
Two workloads reside in the same IP subnet but policy requires stricter isolation for only a tagged set of VMs. Security engineering must restore the approved service without relaxing unrelated protection. What is the best next implementation or troubleshooting step?
- Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads.
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
- Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership.
- Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters.
Explanation
Correct Answer
A:Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. That response is associated with dynamic arp inspection source of truth rather than the specific aci microsegmentation selector condition described here. For the stated failure, the preferred action is: Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. Relevant evidence: Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. Security engineering must restore the approved service without relaxing unrelated protection.
C:Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership. This concerns fabric binding membership, not aci microsegmentation selector.
D:Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. That response is associated with aci inter-epg contract rather than the specific aci microsegmentation selector condition described here. For the stated failure, the preferred action is: Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. Relevant evidence: Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. Security engineering must restore the approved service without relaxing unrelated protection.
Question 534
An administrator assumes every MDS image update is nondisruptive because the switch has redundant supervisors. A storage change board requires a traceable diagnosis before allowing further fabric changes. What is the best next implementation or troubleshooting step?
- Reconcile FCNS registrations and target identity changes before recreating the entire VSAN.
- Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning.
- Update the device alias to the authorized new WWPN and validate all zoning references before applying it.
- Run supported upgrade-path and feature-impact checks with a validated rollback plan before starting the update.
Explanation
Correct Answer
D:Run supported upgrade-path and feature-impact checks with a validated rollback plan before starting the update. SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Reconcile FCNS registrations and target identity changes before recreating the entire VSAN. This concerns fibre channel name-server entries, not mds nondisruptive upgrade planning.
B:Confirm upstream NPIV support and the NPV uplink VSAN association before modifying host zoning. This concerns npv uplink fabric services, not mds nondisruptive upgrade planning.
C:Update the device alias to the authorized new WWPN and validate all zoning references before applying it. This concerns device alias maintenance, not mds nondisruptive upgrade planning.
Question 535
A service-profile template update adds a workload VLAN but newly associated blades cannot send tagged frames for that network. Operations is validating the host before approving production workload placement. How should the implementation be validated against the original failure?
- Traffic remains available across a controlled single-fabric interruption with expected failover behavior.
- The server locates the approved boot target and starts consistently through planned reboots.
- The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface.
- Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment.
Explanation
Correct Answer
C:The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface. This result tests the original failure rather than reporting merely that the configuration command was accepted. A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Traffic remains available across a controlled single-fabric interruption with expected failover behavior. That response is associated with ucs fabric redundancy rather than the specific ucs vlan pool and template condition described here. For the stated failure, the preferred action is: Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path. Relevant evidence: Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs. Operations is validating the host before approving production workload placement.
B:The server locates the approved boot target and starts consistently through planned reboots. This concerns c-series boot policy alignment, not UCS VLAN pool and template.
D:Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment. That response is associated with ucs mac pool uniqueness rather than the specific ucs vlan pool and template condition described here. For the stated failure, the preferred action is: Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path. Relevant evidence: Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs. Operations is validating the host before approving production workload placement.
Question 536
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 controlled change is most appropriate given the evidence?
- Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context.
- Validate API responses and explicitly handle missing data before calculating health status.
- Verify the API user role, requested method and endpoint authorization before changing transport routing.
- Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems.
Explanation
Correct Answer
C:Verify the API user role, requested method and endpoint authorization before changing transport routing. 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:Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. This concerns eem syslog-triggered remediation, not nx-api request authorization.
B:Validate API responses and explicitly handle missing data before calculating health status. This concerns on-box python exception handling, not nx-api request authorization.
D:Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems. This concerns guest shell isolation, not nx-api request authorization.
Question 537
During an east-west bandwidth surge, interface counters rise but do not reveal which applications or source subnets dominate. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What should the engineer do first to address the observed failure?
- Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group.
- Enable a supported streaming telemetry subscription and validate the model paths and collector delivery.
- Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking.
- Collect and analyze supported flow telemetry from the relevant interfaces and time interval.
Explanation
Correct Answer
D:Collect and analyze supported flow telemetry from the relevant interfaces and time interval. Flow records expose traffic conversations and volume patterns that interface-level totals cannot distinguish. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Validate PIM adjacency and the consistent rendezvous-point mapping for the affected multicast group. This concerns PIM multicast rendezvous point, not netflow traffic attribution.
B:Enable a supported streaming telemetry subscription and validate the model paths and collector delivery. This concerns streaming telemetry health, not netflow traffic attribution.
C:Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking. This concerns first-hop gateway failover, not netflow traffic attribution.
Question 538
An on-box NX-OS Python maintenance script interprets a missing interface counter as zero and incorrectly reports healthy operation. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which limitation prevents the team from overgeneralizing this result?
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
- A script that runs without raising a Python exception can still produce an invalid monitoring conclusion.
- A timeout is not proof that the server failed to apply the initial request.
- Network connectivity and a valid TLS session do not imply permission for every API operation.
Explanation
Correct Answer
B:A script that runs without raising a Python exception can still produce an invalid monitoring conclusion. Automation must distinguish unavailable telemetry from a real numeric zero to avoid false success reports. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. This concerns powershell api token security, not on-box python exception handling.
C:A timeout is not proof that the server failed to apply the initial request. This concerns rest api retries and idempotence, not on-box python exception handling.
D:Network connectivity and a valid TLS session do not imply permission for every API operation. This concerns nx-api request authorization, not on-box python exception handling.
Question 539
An operator plans an EPLD firmware update during a business peak because a software patch earlier completed without traffic loss. The team is preparing a controlled production change and must preserve fabric reachability. Which evidence set most directly tests the suspected failure?
- Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements.
- Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state.
- Inspect received EVPN NLRI, route-target extended communities and the tenant VRF import policy.
- Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements.
Explanation
Correct Answer
B:Inspect the target EPLD release notes, affected module types, reload requirements and redundancy state. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Programmable-logic updates can require component reset or reload even when an unrelated software patch did not. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements. This concerns nexus issu eligibility, not epld firmware maintenance.
C:Inspect received EVPN NLRI, route-target extended communities and the tenant VRF import policy. This concerns mp-BGP tenant route import, not epld firmware maintenance.
D:Inspect deployment ownership, isolation boundaries, integration paths and workload movement requirements. This concerns hybrid cloud model classification, not epld firmware maintenance.
Question 540
Clients connected to an access switch stop receiving DHCP leases after DHCP snooping is enabled. A follow-up access review asks the team to validate the same boundary with a controlled negative test. Which controlled change is most appropriate given the evidence?
- Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings.
- Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement.
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
- Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope.
Explanation
Correct Answer
D:Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Enforce an appropriate source-binding validation feature consistent with the recorded DHCP or static bindings. This concerns first-hop ip/mac spoof defense, not DHCP snooping trusted uplink.
B:Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement. This concerns mds SAN administrative control, not DHCP snooping trusted uplink.
C:Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts. This concerns dynamic ARP inspection source of truth, not DHCP snooping trusted uplink.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests