Question 250
An infrastructure engineer changes a Nexus policy directly in production and an upcoming Terraform apply attempts to revert it unexpectedly. The automation change must pass a preproduction test and leave a verifiable audit trail. What caveat is critical when interpreting a successful remediation?
- Increasing API retry frequency cannot resolve a cross-organization authorization mismatch.
- Manually editing Terraform state without verifying real resources can conceal drift rather than fix it.
- A timeout is not proof that the server failed to apply the initial request.
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
Explanation
Correct Answer
B:Manually editing Terraform state without verifying real resources can conceal drift rather than fix it. Terraform compares declared infrastructure with observed resources and can undo unmanaged changes during apply. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Increasing API retry frequency cannot resolve a cross-organization authorization mismatch. That response is associated with intersight policy automation rather than the specific terraform plan and state condition described here. For the stated failure, the preferred action is: Reconcile the approved desired configuration and actual state using plan review and controlled state management. Relevant evidence: Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:A timeout is not proof that the server failed to apply the initial request. This concerns rest api retries and idempotence, not terraform plan and state.
D:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. That response is associated with powershell api token security rather than the specific terraform plan and state condition described here. For the stated failure, the preferred action is: Reconcile the approved desired configuration and actual state using plan review and controlled state management. Relevant evidence: Inspect version-controlled declarations, current plan, state backend locks and out-of-band change record. The automation change must pass a preproduction test and leave a verifiable audit trail.
Question 251
A GPU training cluster reports reduced throughput when synchronized east-west traffic converges on a few uplinks despite healthy compute nodes. The automation change must pass a preproduction test and leave a verifiable audit trail. What caveat is critical when interpreting a successful remediation?
- Manually editing Terraform state without verifying real resources can conceal drift rather than fix it.
- Adding GPUs alone will not solve a fabric bottleneck and may increase east-west network pressure.
- An EEM event match does not prove a remediation command is safe or authorized to execute automatically.
- Increasing API retry frequency cannot resolve a cross-organization authorization mismatch.
Explanation
Correct Answer
B:Adding GPUs alone will not solve a fabric bottleneck and may increase east-west network pressure. Distributed AI jobs can be bottlenecked by data-center fabric transport when many nodes exchange bursts of data. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
A:Manually editing Terraform state without verifying real resources can conceal drift rather than fix it. This concerns terraform plan and state, not ai cluster network congestion.
C:An EEM event match does not prove a remediation command is safe or authorized to execute automatically. This concerns eem syslog-triggered remediation, not ai cluster network congestion.
D:Increasing API retry frequency cannot resolve a cross-organization authorization mismatch. This concerns intersight policy automation, not ai cluster network congestion.
Question 252
During an east-west bandwidth surge, interface counters rise but do not reveal which applications or source subnets dominate. The team is preparing a controlled production change and must preserve fabric reachability. Which limitation prevents the team from overgeneralizing this result?
- Sampled flow records may underrepresent small or short flows and do not contain every packet payload.
- An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment.
- Expanding import targets indiscriminately can leak routes across security and tenancy boundaries.
- A successful subscription does not guarantee every sensor or transient event is supported by the platform.
Explanation
Correct Answer
A:Sampled flow records may underrepresent small or short flows and do not contain every packet payload. Flow records expose traffic conversations and volume patterns that interface-level totals cannot distinguish. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:An FHRP cannot repair a host's incorrect default gateway or disconnected Layer 2 segment. This concerns first-hop gateway failover, not netflow traffic attribution.
C:Expanding import targets indiscriminately can leak routes across security and tenancy boundaries. This concerns mp-BGP tenant route import, not netflow traffic attribution.
D:A successful subscription does not guarantee every sensor or transient event is supported by the platform. This concerns streaming telemetry health, not netflow traffic attribution.
Question 253
A service-profile template update adds a workload VLAN but newly associated blades cannot send tagged frames for that network. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which test result best demonstrates restoration of the intended behavior?
- Hardware environmental faults are resolved and sustained compute tests no longer show thermal throttling.
- The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface.
- Traffic remains available across a controlled single-fabric interruption with expected failover behavior.
- Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment.
Explanation
Correct Answer
B: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. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Hardware environmental faults are resolved and sustained compute tests no longer show thermal throttling. This concerns chassis power and thermal monitoring, not UCS VLAN pool and template.
C:Traffic remains available across a controlled single-fabric interruption with expected failover behavior. This concerns UCS fabric redundancy, not UCS VLAN pool and template.
D:Every active vNIC has a unique assigned MAC and upstream learning stays stable after deployment. This concerns UCS mac pool uniqueness, not UCS VLAN pool and template.
Question 254
An Intersight user has authorization to restart one lab server but can also deploy profiles to production organizations. Security engineering must restore the approved service without relaxing unrelated protection. What should the engineer do first to address the observed failure?
- Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads.
- Limit the user to the appropriate organization, resource group and role for the lab estate.
- Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope.
- Validate DAI binding sources and configure a supported static ARP ACL or binding for the approved fixed-address hosts.
Explanation
Correct Answer
B:Limit the user to the appropriate organization, resource group and role for the lab estate. Intersight RBAC and organizational scoping define which managed resources an operator may control. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Use supported ACI microsegmentation classification and policy to distinguish the tagged workloads. This concerns aci microsegmentation selector, not intersight scoped operations.
C:Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. This concerns DHCP snooping trusted uplink, not intersight scoped operations.
D: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 intersight scoped operations.
Question 255
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 explanation most directly accounts for the required correction?
- Scheduled tasks follow time-based execution rather than requiring a spontaneous syslog event to fire.
- Shared management APIs need explicit target selection; ambiguous tags can misdirect otherwise syntactically valid changes.
- An HTTP 403 indicates a reachable endpoint has refused the request under its authorization controls.
- Guest Shell provides a separate Linux execution environment with its own file and permission context.
Explanation
Correct Answer
D: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
A:Scheduled tasks follow time-based execution rather than requiring a spontaneous syslog event to fire. This concerns nx-os scheduler jobs, not guest shell isolation.
B:Shared management APIs need explicit target selection; ambiguous tags can misdirect otherwise syntactically valid changes. This concerns nexus dashboard automation scope, not guest shell isolation.
C:An HTTP 403 indicates a reachable endpoint has refused the request under its authorization controls. This concerns nx-api request authorization, not guest shell isolation.
Question 256
A storage administrator zones a host using a node name although the fabric login is registered with a different port identifier. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. Which technical principle best explains the recommended response?
- VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure.
- Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies.
- A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic.
- NFS file access is controlled by network and export permissions, not Fibre Channel zoning.
Explanation
Correct Answer
B:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. This concerns VSAN isolation, not wwpn versus wwnn.
C:A physical Fibre Channel ISL can stay up while excluding a particular VSAN from carried fabric traffic. This concerns VSAN trunk mismatch, not wwpn versus wwnn.
D:NFS file access is controlled by network and export permissions, not Fibre Channel zoning. This concerns nfs export permissions, not wwpn versus wwnn.
Question 257
A blade has two configured vNICs, yet a failed fabric interconnect isolates all management and application traffic. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which limitation prevents the team from overgeneralizing this result?
- Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link.
- Two vNIC objects on the same failed upstream path do not provide true physical redundancy.
- Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template.
- Changing the displayed server name does not resolve a duplicate effective network identifier.
Explanation
Correct Answer
B:Two vNIC objects on the same failed upstream path do not provide true physical redundancy. Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Assigning service profiles before physical discovery is healthy cannot correct a failed IOM link. This concerns UCS blade chassis IOM discovery, not UCS fabric redundancy.
C:Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template. This concerns UCS VLAN pool and template, not UCS fabric redundancy.
D:Changing the displayed server name does not resolve a duplicate effective network identifier. This concerns UCS mac pool uniqueness, not UCS fabric redundancy.
Question 258
A data-center VLAN loses its gateway whenever the active router is rebooted even though the standby has a working SVI. The team is preparing a controlled production change and must preserve fabric reachability. What should the engineer collect before ruling out other causes?
- Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI.
- Inspect root bridge identity, port role, path cost and topology-change counters.
- Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status.
- Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces.
Explanation
Correct Answer
C:Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status. These records help distinguish the suspected failure from a superficially similar fault before modifying production. An FHRP keeps a virtual default gateway available while members transition between active and standby roles. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A: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 first-hop gateway failover condition described here. For the stated failure, the preferred action is: Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking. Relevant evidence: Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status. The team is preparing a controlled production change and must preserve fabric reachability.
B:Inspect root bridge identity, port role, path cost and topology-change counters. This concerns rstp blocked uplink, not first-hop gateway failover.
D:Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. That response is associated with pim multicast rendezvous point rather than the specific first-hop gateway failover condition described here. For the stated failure, the preferred action is: Configure and validate an appropriate first-hop redundancy group with a shared virtual gateway and healthy tracking. Relevant evidence: Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status. The team is preparing a controlled production change and must preserve fabric reachability.
Question 259
A UCS blade chassis appears in inventory but several blades remain undiscovered after an I/O module replacement. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. Which test result best demonstrates restoration of the intended behavior?
- The management controller responds from the authorized subnet and administrator login is audited.
- All expected blades appear in managed inventory without persistent IOM fault alarms.
- The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface.
- Traffic remains available across a controlled single-fabric interruption with expected failover behavior.
Explanation
Correct Answer
B:All expected blades appear in managed inventory without persistent IOM fault alarms. This result tests the original failure rather than reporting merely that the configuration command was accepted. The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:The management controller responds from the authorized subnet and administrator login is audited. This concerns UCS c-series cimc reachability, not UCS blade chassis IOM discovery.
C:The expected VLAN is present on the associated vNIC and tenant frames reach the correct upstream interface. This concerns UCS VLAN pool and template, not UCS blade chassis IOM discovery.
D:Traffic remains available across a controlled single-fabric interruption with expected failover behavior. This concerns UCS fabric redundancy, not UCS blade chassis IOM discovery.
Question 260
Two workloads reside in the same IP subnet but policy requires stricter isolation for only a tagged set of VMs. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What information should be inspected before the change is applied?
- Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs.
- Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts.
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
- Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules.
Explanation
Correct Answer
B:Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Microsegmentation can classify subsets of endpoints beyond broad subnet grouping and apply finer-grained controls. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. This concerns dynamic ARP inspection source of truth, not aci microsegmentation selector.
C:Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. This concerns first-hop ip/mac spoof defense, not aci microsegmentation selector.
D:Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. This concerns aci inter-epg contract, not aci microsegmentation selector.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests