Question 550
A new VXLAN leaf advertises local VNIs but tunnels to another leaf fail because the VTEP source loopback is missing from underlay routing. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What information should be inspected before the change is applied?
- Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events.
- Inspect root bridge identity, port role, path cost and topology-change counters.
- Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability.
- Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults.
Explanation
Correct Answer
C:Inspect loopback addresses, underlay routes, tunnel source settings and VTEP reachability. These records help distinguish the suspected failure from a superficially similar fault before modifying production. VXLAN encapsulation depends on routable IP transport between VTEP endpoints before tenant traffic can traverse it. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:Inspect VMM controller connectivity, domain association, VM port-group mapping and endpoint events. This concerns aci vmm association, not vxlan vtep underlay reachability.
B:Inspect root bridge identity, port role, path cost and topology-change counters. This concerns rstp blocked uplink, not vxlan vtep underlay reachability.
D:Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. This concerns aci access policy chain, not vxlan vtep underlay reachability.
Question 551
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 controlled change is most appropriate given the evidence?
- Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members.
- Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone.
- Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join.
- Check the CFS distribution scope and commit or activation workflow for the affected feature.
Explanation
Correct Answer
D:Check the CFS distribution scope and commit or activation workflow for the affected feature. 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:Align interface speed, VSAN mode and compatibility parameters across the intended port-channel members. This concerns fibre channel port-channel consistency, not cisco fabric services distribution.
B:Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone. This concerns single-initiator zoning, not cisco fabric services distribution.
C:Investigate Fibre Channel domain ID assignments and fabric merge requirements before allowing the ISL to join. This concerns fcid and domain id stability, not cisco fabric services distribution.
Question 552
An Intersight user has authorization to restart one lab server but can also deploy profiles to production organizations. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What should the engineer collect before ruling out other causes?
- Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs.
- Inspect UCS role privileges, organization assignments, recent actions and denied command records.
- Inspect role grants, resource-group associations, organization context and API access evidence.
- Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins.
Explanation
Correct Answer
C:Inspect role grants, resource-group associations, organization context and API access evidence. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Intersight RBAC and organizational scoping define which managed resources an operator may control. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
A:Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs. This concerns mds SAN administrative control, not intersight scoped operations.
B:Inspect UCS role privileges, organization assignments, recent actions and denied command records. This concerns UCS administrative separation, not intersight scoped operations.
D:Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. This concerns fibre channel port security, not intersight scoped operations.
Question 553
An engineer plans simultaneous firmware activation on every blade supporting a critical cluster with no evacuation plan. Operations is validating the host before approving production workload placement. Which explanation most directly accounts for the required correction?
- Rolling hardware maintenance reduces service disruption only if dependent workloads can tolerate sequential host removal.
- Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely.
- Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause.
- Physical power or cooling constraints can throttle compute even when guest metrics show no software error.
Explanation
Correct Answer
A:Rolling hardware maintenance reduces service disruption only if dependent workloads can tolerate sequential host removal. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. This concerns compute traffic span, not UCS firmware change sequencing.
C:Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause. This concerns intersight alert triage, not UCS firmware change sequencing.
D:Physical power or cooling constraints can throttle compute even when guest metrics show no software error. This concerns chassis power and thermal monitoring, not UCS firmware change sequencing.
Question 554
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. Why is the targeted engineering response justified in this situation?
- Hybrid cloud combines distinct cloud infrastructures linked to support data and application portability.
- Flow records expose traffic conversations and volume patterns that interface-level totals cannot distinguish.
- Programmable-logic updates can require component reset or reload even when an unrelated software patch did not.
- Unknown-unicast, broadcast and multicast frames require an appropriate VXLAN replication or multicast transport method.
Explanation
Correct Answer
B: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:Hybrid cloud combines distinct cloud infrastructures linked to support data and application portability. This concerns hybrid cloud model classification, not netflow traffic attribution.
C:Programmable-logic updates can require component reset or reload even when an unrelated software patch did not. This concerns epld firmware maintenance, not netflow traffic attribution.
D:Unknown-unicast, broadcast and multicast frames require an appropriate VXLAN replication or multicast transport method. This concerns bum replication behavior, not netflow traffic attribution.
Question 555
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 explanation most directly accounts for the required correction?
- Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely.
- A server and adapter firmware combination must be supported for its hardware and operating environment.
- Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause.
- Physical power or cooling constraints can throttle compute even when guest metrics show no software error.
Explanation
Correct Answer
D: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
A:Packet replication can reveal TCP and frame-level behavior that interface counters summarize only coarsely. 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.
B:A server and adapter firmware combination must be supported for its hardware and operating environment. This concerns UCS firmware compatibility, not chassis power and thermal monitoring.
C:Hardware alerts require component-level evidence; unrelated performance alarms may have a separate root cause. 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 556
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 explanation most directly accounts for the required correction?
- 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.
- An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage.
Explanation
Correct Answer
C: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:VSANs provide logical fabric separation across shared physical Fibre Channel infrastructure. This concerns VSAN isolation, not VSAN trunk mismatch.
B:Fibre Channel port WWNs identify individual interfaces used by fabric login and zoning policies. This concerns wwpn versus wwnn, not VSAN trunk mismatch.
D:An EPLD update may reset affected SAN hardware even if a previous NX-OS patch required no outage. This concerns mds epld update impact, not VSAN trunk mismatch.
Question 557
An orchestration service retries a configuration POST after timeout and produces duplicate resources on a Nexus management controller. The automation change must pass a preproduction test and leave a verifiable audit trail. What should the engineer do first to address the observed failure?
- 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.
- Check API operation semantics and implement safe read-before-create or idempotent reconciliation behavior.
- Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported.
Explanation
Correct Answer
C:Check API operation semantics and implement safe read-before-create or idempotent reconciliation behavior. Retrying non-idempotent create operations without state checks can duplicate resources after ambiguous timeouts. 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. That response is associated with on-box python exception handling rather than the specific rest api retries and idempotence condition described here. For the stated failure, the preferred action is: Check API operation semantics and implement safe read-before-create or idempotent reconciliation behavior. Relevant evidence: Inspect API logs, resource identifiers, HTTP response history and current running object state. The automation change must pass a preproduction test and leave a verifiable audit trail.
B:Verify the API user role, requested method and endpoint authorization before changing transport routing. That response is associated with nx-api request authorization rather than the specific rest api retries and idempotence condition described here. For the stated failure, the preferred action is: Check API operation semantics and implement safe read-before-create or idempotent reconciliation behavior. Relevant evidence: Inspect API logs, resource identifiers, HTTP response history and current running object state. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Replace non-idempotent imperative commands with state-aware configuration modules and diff-based validation where supported. This concerns ansible idempotent templates, not rest api retries and idempotence.
Question 558
An API workflow creates an Intersight server profile but fails because referenced policy objects belong to another inaccessible organization. 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?
- An EEM event match does not prove a remediation command is safe or authorized to execute automatically.
- Manually editing Terraform state without verifying real resources can conceal drift rather than fix it.
- Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage.
- Increasing API retry frequency cannot resolve a cross-organization authorization mismatch.
Explanation
Correct Answer
D:Increasing API retry frequency cannot resolve a cross-organization authorization mismatch. Intersight objects and their assignments must satisfy resource visibility and scope permissions. A scheduled deployment is pending, and the engineer must validate how the script handles this failure condition.
Incorrect Answers
A:An EEM event match does not prove a remediation command is safe or authorized to execute automatically. This concerns eem syslog-triggered remediation, not intersight policy automation.
B:Manually editing Terraform state without verifying real resources can conceal drift rather than fix it. This concerns terraform plan and state, not intersight policy automation.
C:Hiding a plaintext key in an obfuscated PowerShell string is not equivalent to secure secret storage. This concerns powershell api token security, not intersight policy automation.
Question 559
An unauthorized initiator plugs into an available SAN switch port and attempts fabric login using an unapproved WWPN. Security engineering must restore the approved service without relaxing unrelated protection. What is the best next implementation or troubleshooting step?
- Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities.
- Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership.
- Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement.
- Assign a scoped UCS administrative role that permits health visibility without SAN policy modification.
Explanation
Correct Answer
A:Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Enforce an approved fabric-binding policy for permitted switch identities and review authorized ISL membership. That response is associated with fabric binding membership rather than the specific fibre channel port security condition described here. For the stated failure, the preferred action is: Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. Relevant evidence: Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. Security engineering must restore the approved service without relaxing unrelated protection.
C:Replace the inherited privilege with a least-privilege SAN read/monitor role and confirm AAA enforcement. That response is associated with mds san administrative control rather than the specific fibre channel port security condition described here. For the stated failure, the preferred action is: Configure approved Fibre Channel port-security bindings and verify rejection of unregistered identities. Relevant evidence: Inspect port-security policy, learned WWPNs, interface events and attempted fabric logins. Security engineering must restore the approved service without relaxing unrelated protection.
D:Assign a scoped UCS administrative role that permits health visibility without SAN policy modification. This concerns UCS administrative separation, not fibre channel port security.
Question 560
Clients connected to an access switch stop receiving DHCP leases after DHCP snooping is enabled. Security engineering must restore the approved service without relaxing unrelated protection. What should the engineer collect before ruling out other causes?
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
- Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting.
- Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs.
- Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology.
Explanation
Correct Answer
D:Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. These records help distinguish the suspected failure from a superficially similar fault before modifying production. DHCP snooping should accept DHCP server responses from trusted paths while suppressing rogue access-port servers. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. That response is associated with first-hop ip/mac spoof defense rather than the specific dhcp snooping trusted uplink condition described here. For the stated failure, the preferred action is: Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. Relevant evidence: Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. Security engineering must restore the approved service without relaxing unrelated protection.
B:Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. This concerns centralized AAA fallback, not DHCP snooping trusted uplink.
C:Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. That response is associated with dynamic arp inspection source of truth rather than the specific dhcp snooping trusted uplink condition described here. For the stated failure, the preferred action is: Mark only the verified DHCP-server-facing interface as trusted and validate the snooping VLAN scope. Relevant evidence: Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. Security engineering must restore the approved service without relaxing unrelated protection.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests