Question 310
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 explanation most directly accounts for the required correction?
- An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage.
- The fabric name server reflects registered port identities and can reveal whether the expected target is visible.
- Tightly scoped FC zones limit which initiators can discover or communicate with designated targets.
- Configured zones and active enforced zoning can differ until the appropriate zoneset is activated.
Explanation
Correct Answer
A: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 fabric name server reflects registered port identities and can reveal whether the expected target is visible. This concerns fibre channel name-server entries, not mds epld update impact.
C:Tightly scoped FC zones limit which initiators can discover or communicate with designated targets. This concerns single-initiator zoning, not mds epld update impact.
D:Configured zones and active enforced zoning can differ until the appropriate zoneset is activated. This concerns zoneset activation state, not mds epld update impact.
Question 311
An operations team sees sporadic storage-path instability but its monitoring only polls device availability every five minutes. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which controlled change is most appropriate given the evidence?
- Validate NFS export authorization, client identity and supported protocol settings before altering the SAN fabric.
- Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path.
- Correlate SAN-specific health and interface telemetry in supported Nexus Dashboard or MDS monitoring tools.
- Validate physical FC link and initiator FLOGI registration before changing storage-array masking.
Explanation
Correct Answer
C:Correlate SAN-specific health and interface telemetry in supported Nexus Dashboard or MDS monitoring tools. Topology, fabric events and time-series indicators reveal path problems hidden by simple reachability polling. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Validate NFS export authorization, client identity and supported protocol settings before altering the SAN fabric. This concerns nfs export permissions, not nexus dashboard SAN monitoring.
B:Verify iSCSI discovery addresses, initiator identity, authentication and storage VLAN path. This concerns iscsi target discovery, not nexus dashboard SAN monitoring.
D:Validate physical FC link and initiator FLOGI registration before changing storage-array masking. This concerns fibre channel fabric login, not nexus dashboard SAN monitoring.
Question 312
A Linux utility installed in the NX-OS Guest Shell cannot find a file that an operator placed on a different management workstation. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. Which intervention most directly addresses the stated condition?
- Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems.
- Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context.
- Use NX-OS scheduling capability with the appropriate job definition and maintenance safeguards.
- Verify the API user role, requested method and endpoint authorization before changing transport routing.
Explanation
Correct Answer
A:Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems. Guest Shell provides a separate Linux execution environment with its own file and permission context. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
B:Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. This concerns eem syslog-triggered remediation, not guest shell isolation.
C:Use NX-OS scheduling capability with the appropriate job definition and maintenance safeguards. This concerns nx-os scheduler jobs, not guest shell isolation.
D:Verify the API user role, requested method and endpoint authorization before changing transport routing. This concerns nx-api request authorization, not guest shell isolation.
Question 313
Storage latency rises whenever a particular MDS uplink is busy, and CRC errors increase on that same port. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which qualification should the change record include?
- A storage-array firmware update is not a demonstrated cure for physical FC CRC errors.
- Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable.
- A friendly alias name is not a substitute for a correct underlying port WWPN.
- An old name-server entry for the former target port does not prove the replacement path is live.
Explanation
Correct Answer
A:A storage-array firmware update is not a demonstrated cure for physical FC CRC errors. CRC and link-level errors can indicate transport impairment rather than a storage-array performance limitation. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
B:Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable. This concerns npv uplink fabric services, not SAN port error telemetry.
C:A friendly alias name is not a substitute for a correct underlying port WWPN. This concerns device alias maintenance, not SAN port error telemetry.
D:An old name-server entry for the former target port does not prove the replacement path is live. This concerns fibre channel name-server entries, not SAN port error telemetry.
Question 314
Two production Nexus peers have drifted in their intended interface templates after unreviewed local commands were applied. The team is preparing a controlled production change and must preserve fabric reachability. Which controlled change is most appropriate given the evidence?
- Correct the L3 VNI and tenant VRF association and check EVPN route import/export on participating VTEPs.
- Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop.
- Compare actual configuration to a version-controlled golden baseline and restore approved differences through change control.
- Align the switchport and LACP parameters across members before attempting to force them into the bundle.
Explanation
Correct Answer
C:Compare actual configuration to a version-controlled golden baseline and restore approved differences through change control. Configuration management detects and remediates unauthorized deviations rather than trusting the most recent device state. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Correct the L3 VNI and tenant VRF association and check EVPN route import/export on participating VTEPs. This concerns evpn vni-to-vrf mapping, not fabric configuration drift.
B:Confirm the designated root and spanning-tree role before changing a port that is intentionally blocking a loop. This concerns rstp blocked uplink, not fabric configuration drift.
D:Align the switchport and LACP parameters across members before attempting to force them into the bundle. This concerns lacp member mismatch, not fabric configuration drift.
Question 315
Two ACI EPGs can each reach their own default gateway but permitted application traffic between them is denied. Security engineering must restore the approved service without relaxing unrelated protection. What is the best next implementation or troubleshooting step?
- Limit the user to the appropriate organization, resource group and role for the lab estate.
- Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters.
- Configure and test the approved AAA method order and protected break-glass account following change policy.
- Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads.
Explanation
Correct Answer
B:Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. ACI contracts control permitted communication between endpoint groups, separate from basic endpoint addressing. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Limit the user to the appropriate organization, resource group and role for the lab estate. This concerns intersight scoped operations, not aci inter-epg contract.
C:Configure and test the approved AAA method order and protected break-glass account following change policy. That response is associated with centralized aaa fallback rather than the specific aci inter-epg contract condition described here. For the stated failure, the preferred action is: Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. Relevant evidence: Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. Security engineering must restore the approved service without relaxing unrelated protection.
D:Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. That response is associated with aci microsegmentation selector rather than the specific aci inter-epg contract condition described here. For the stated failure, the preferred action is: Apply and validate a narrowly scoped ACI contract with the required provider-consumer relationship and filters. Relevant evidence: Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. Security engineering must restore the approved service without relaxing unrelated protection.
Question 316
A network inventory script reports only the first hundred switches even though Nexus Dashboard shows more devices. 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 DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs.
- Inspect response metadata, page limits, next tokens, error responses and known inventory counts.
- Inspect Ansible change output, module behavior, running configurations and intended-state version control.
- Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record.
Explanation
Correct Answer
B:Inspect response metadata, page limits, next tokens, error responses and known inventory counts. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Paginated REST endpoints may return only a subset of objects unless clients follow continuation information. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Inspect DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs. This concerns poap bootstrap dependencies, not python api pagination.
C:Inspect Ansible change output, module behavior, running configurations and intended-state version control. This concerns ansible idempotent templates, not python api pagination.
D:Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record. This concerns terraform plan and state, not python api pagination.
Question 317
An NX-OS switch logs an uplink failure but an EEM policy intended to notify the NOC never triggers. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition. What is the best next implementation or troubleshooting step?
- Constrain automation targets using verified site identity and a preflight plan before bulk deployment.
- Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context.
- Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems.
- Use NX-OS scheduling capability with the appropriate job definition and maintenance safeguards.
Explanation
Correct Answer
B:Validate the event detector pattern, applet registration and permitted action under the intended NX-OS context. Embedded Event Manager runs configured actions in response to matching local events and authorization constraints. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:Constrain automation targets using verified site identity and a preflight plan before bulk deployment. This concerns nexus dashboard automation scope, not eem syslog-triggered remediation.
C:Verify the Guest Shell environment, mounted paths and supported data-transfer method rather than assuming shared filesystems. This concerns guest shell isolation, not eem syslog-triggered remediation.
D:Use NX-OS scheduling capability with the appropriate job definition and maintenance safeguards. This concerns nx-os scheduler jobs, not eem syslog-triggered remediation.
Question 318
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. Which explanation most directly accounts for the required correction?
- Credential protection and least privilege reduce the impact of source-code disclosure.
- Retrying non-idempotent create operations without state checks can duplicate resources after ambiguous timeouts.
- Automation must distinguish unavailable telemetry from a real numeric zero to avoid false success reports.
- An HTTP 403 indicates a reachable endpoint has refused the request under its authorization controls.
Explanation
Correct Answer
C: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:Credential protection and least privilege reduce the impact of source-code disclosure. This concerns powershell api token security, not on-box python exception handling.
B:Retrying non-idempotent create operations without state checks can duplicate resources after ambiguous timeouts. 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.
D:An HTTP 403 indicates a reachable endpoint has refused the request under its authorization controls. 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.
Question 319
A storage host loses path visibility after a target port migration although the physical target link is healthy. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which qualification should the change record include?
- An old name-server entry for the former target port does not prove the replacement path is live.
- Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable.
- Saving a zoneset definition alone does not establish that it is the enforced active zoning policy.
- A friendly alias name is not a substitute for a correct underlying port WWPN.
Explanation
Correct Answer
A:An old name-server entry for the former target port does not prove the replacement path is live. The fabric name server reflects registered port identities and can reveal whether the expected target is visible. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
B:Turning on NPV alone does not create initiator logins if upstream NPIV is unavailable. This concerns npv uplink fabric services, not fibre channel name-server entries.
C:Saving a zoneset definition alone does not establish that it is the enforced active zoning policy. This concerns zoneset activation state, not fibre channel name-server entries.
D:A friendly alias name is not a substitute for a correct underlying port WWPN. This concerns device alias maintenance, not fibre channel name-server entries.
Question 320
A Linux workload can reach an NFS server by IP but receives access denied when mounting its application share. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which technical principle best explains the recommended response?
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
- NFS file access is controlled by network and export permissions, not Fibre Channel zoning.
Explanation
Correct Answer
D:NFS file access is controlled by network and export permissions, not Fibre Channel zoning. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. This concerns VSAN isolation, not nfs export permissions.
B:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. This concerns VSAN trunk mismatch, not nfs export permissions.
C:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. This concerns wwpn versus wwnn, not nfs export permissions.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests