Question 760
An administrator assumes every MDS image update is nondisruptive because the switch has redundant supervisors. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What is the strongest technical basis for the recommended action?
- FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation.
- SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints.
- Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces.
- Cisco Fabric Services can distribute feature configuration among fabric switches, subject to feature-specific rules.
Explanation
Correct Answer
B:SAN nondisruptive upgrade support depends on exact software path, hardware redundancy and active feature constraints. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:FCID addressing includes a domain component, and domain conflicts can prevent stable fabric formation. This concerns fcid and domain id stability, not mds nondisruptive upgrade planning.
C:Fibre Channel port channels bundle compatible physical links; inconsistent member configuration can suspend interfaces. This concerns fibre channel port-channel consistency, not mds nondisruptive upgrade planning.
D:Cisco Fabric Services can distribute feature configuration among fabric switches, subject to feature-specific rules. This concerns cisco fabric services distribution, not mds nondisruptive upgrade planning.
Question 761
A UCS blade chassis appears in inventory but several blades remain undiscovered after an I/O module replacement. Operations is validating the host before approving production workload placement. Which technical principle best explains the recommended response?
- The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades.
- Rolling hardware maintenance reduces service disruption only if dependent workloads can tolerate sequential host removal.
- Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path.
- A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry.
Explanation
Correct Answer
A:The blade chassis depends on a healthy IOM and fabric-interconnect management path to discover and service blades. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:Rolling hardware maintenance reduces service disruption only if dependent workloads can tolerate sequential host removal. This concerns UCS firmware change sequencing, not UCS blade chassis IOM discovery.
C:Logical dual vNIC definitions provide resilience only when each has a functioning independent physical fabric path. That response is associated with ucs fabric redundancy rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
D:A vNIC may be configured for a VLAN that the fabric and upstream trunks still do not carry. That response is associated with ucs vlan pool and template rather than the specific ucs blade chassis iom discovery condition described here. For the stated failure, the preferred action is: Check fabric-interconnect connectivity, IOM state and chassis discovery before recreating server identities. Relevant evidence: Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. Operations is validating the host before approving production workload placement.
Question 762
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. Which limitation prevents the team from overgeneralizing this result?
- Changing the entire subnet ACL is not equivalent to targeting a specific VM attribute-defined subset.
- A fallback local account needs tight protection and audit controls rather than indefinite shared use.
- Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception.
- Giving every EPG an unrestricted contract would defeat segmentation goals to restore one application.
Explanation
Correct Answer
A:Changing the entire subnet ACL is not equivalent to targeting a specific VM attribute-defined subset. 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:A fallback local account needs tight protection and audit controls rather than indefinite shared use. This concerns centralized AAA fallback, not aci microsegmentation selector.
C:Disabling DAI across the whole access VLAN would remove spoofing protection to solve a narrow exception. 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.
D:Giving every EPG an unrestricted contract would defeat segmentation goals to restore one application. 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 763
An operations team sees sporadic storage-path instability but its monitoring only polls device availability every five minutes. 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?
- A redundant fabric cannot protect traffic that was incorrectly attached to a single SAN path.
- Successful ICMP ping does not establish that iSCSI discovery or target authorization is working.
- Opening all export access to the entire subnet may bypass least privilege rather than fix the specific denial.
- A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy.
Explanation
Correct Answer
D:A green availability tile does not establish stable storage latency, fabric health or end-to-end redundancy. Topology, fabric events and time-series indicators reveal path problems hidden by simple reachability polling. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:A redundant fabric cannot protect traffic that was incorrectly attached to a single SAN path. This concerns mds epld update impact, not nexus dashboard SAN monitoring.
B:Successful ICMP ping does not establish that iSCSI discovery or target authorization is working. This concerns iscsi target discovery, not nexus dashboard SAN monitoring.
C:Opening all export access to the entire subnet may bypass least privilege rather than fix the specific denial. This concerns nfs export permissions, not nexus dashboard SAN monitoring.
Question 764
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. Which explanation most directly accounts for the required correction?
- PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery.
- EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings.
- An FHRP keeps a virtual default gateway available while members transition between active and standby roles.
- OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings.
Explanation
Correct Answer
C: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:PIM sparse mode relies on correct multicast routing state and, where applicable, an RP for shared-tree discovery. 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.
B:EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings. 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.
D:OSPFv3 neighbors communicate over IPv6 link-local addresses and require compatible protocol and area settings. This concerns ospfv3 IPv6 neighbor discovery, not first-hop gateway failover.
Question 765
An administrator imports a service-profile template and two new server identities unexpectedly request an overlapping MAC range. 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?
- Adding a VLAN only to the upstream switch does not attach it automatically to the UCS vNIC template.
- Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs.
- Changing the displayed server name does not resolve a duplicate effective network identifier.
- A high-priority label inside UCS does not guarantee every upstream switch honors that class.
Explanation
Correct Answer
C:Changing the displayed server name does not resolve a duplicate effective network identifier. UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A: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 mac pool uniqueness.
B:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. This concerns server pool qualification, not UCS mac pool uniqueness.
D:A high-priority label inside UCS does not guarantee every upstream switch honors that class. This concerns UCS network qos policy, not UCS mac pool uniqueness.
Question 766
A four-link server port-channel forwards on two members because the other members use incompatible trunk settings. The team is preparing a controlled production change and must preserve fabric reachability. Which observations would best validate the initial diagnosis?
- Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons.
- Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons.
- Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults.
- Inspect root bridge identity, port role, path cost and topology-change counters.
Explanation
Correct Answer
A:Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. These records help distinguish the suspected failure from a superficially similar fault before modifying production. LACP aggregates only compatible interfaces, and inconsistent operational settings can suspend members. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
B:Inspect peer-link state, peer-keepalive reachability, consistency checks and suspended port reasons. That response is associated with vpc peer-link recovery rather than the specific lacp member mismatch condition described here. For the stated failure, the preferred action is: Align the switchport and LACP parameters across members before attempting to force them into the bundle. Relevant evidence: Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. The team is preparing a controlled production change and must preserve fabric reachability.
C:Inspect VLAN pool allocation, AEP association, domain assignment, policy-group binding and interface faults. This concerns aci access policy chain, not lacp member mismatch.
D:Inspect root bridge identity, port role, path cost and topology-change counters. That response is associated with rstp blocked uplink rather than the specific lacp member mismatch condition described here. For the stated failure, the preferred action is: Align the switchport and LACP parameters across members before attempting to force them into the bundle. Relevant evidence: Inspect port-channel summaries, actor/partner keys, VLAN and speed settings and member suspension reasons. The team is preparing a controlled production change and must preserve fabric reachability.
Question 767
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. What caveat is critical when interpreting a successful remediation?
- Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic.
- A successful import message does not guarantee the restored configuration is current or conflict-free.
- Suppressing an alert does not remove the underlying component fault or its availability risk.
- Raising VM CPU reservations cannot override a chassis hardware thermal-protection mechanism.
Explanation
Correct Answer
D: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. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Mirroring an inactive or wrong vNIC path cannot prove what happened to the actual workload traffic. 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 successful import message does not guarantee the restored configuration is current or conflict-free. This concerns UCS restore integrity, not chassis power and thermal monitoring.
C:Suppressing an alert does not remove the underlying component fault or its availability risk. 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 768
A new C-Series rack server powers on but its management controller cannot be reached from the secure operations subnet. Operations is validating the host before approving production workload placement. Which qualification should the change record include?
- Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs.
- Successful one-time installation does not ensure the persistent boot policy has been corrected.
- A template update must not be assumed to affect just the blade presently open in the UI.
- An operating-system network driver cannot repair an isolated hardware management interface.
Explanation
Correct Answer
D:An operating-system network driver cannot repair an isolated hardware management interface. The CIMC out-of-band interface requires correctly configured management connectivity independent of the installed server operating system. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. This concerns server pool qualification, not UCS c-series cimc reachability.
B:Successful one-time installation does not ensure the persistent boot policy has been corrected. This concerns boot order and removable media, not UCS c-series cimc reachability.
C:A template update must not be assumed to affect just the blade presently open in the UI. This concerns updating service-profile templates, not UCS c-series cimc reachability.
Question 769
A SAN-boot blade fails to discover the primary boot LUN even though the fibre channel interface shows link up. Operations is validating the host before approving production workload placement. What information should be inspected before the change is applied?
- Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries.
- Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references.
- Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility.
- Inspect server inventory, qualification criteria, pool membership and association failures.
Explanation
Correct Answer
C:Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. These records help distinguish the suspected failure from a superficially similar fault before modifying production. SAN boot requires all of the initiator, fabric zoning, target presentation and boot policy to agree. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Inspect vHBA identity, SAN uplink operational state, VSAN mapping and upstream FLOGI entries. This concerns SAN connectivity from blade chassis, not SAN boot path policy.
B:Inspect WWPN pool reservations, active vHBA identities, fabric login records and zoning references. That response is associated with wwpn pool allocation rather than the specific san boot path policy condition described here. For the stated failure, the preferred action is: Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. Relevant evidence: Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. Operations is validating the host before approving production workload placement.
D:Inspect server inventory, qualification criteria, pool membership and association failures. That response is associated with server pool qualification rather than the specific san boot path policy condition described here. For the stated failure, the preferred action is: Validate the service-profile SAN boot target WWPN/LUN settings and underlying zoning/masking path. Relevant evidence: Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. Operations is validating the host before approving production workload placement.
Question 770
A new Fibre Channel host is connected to an MDS switch but never receives a fabric identifier and cannot discover targets. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What should the engineer collect before ruling out other causes?
- Inspect fcdomain status, assigned domain IDs, ISL events and active FCID allocations.
- Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments.
- Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs.
- Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events.
Explanation
Correct Answer
D:Inspect FC interface state, FLOGI database, initiator WWPN and relevant switch events. These records help distinguish the suspected failure from a superficially similar fault before modifying production. An initiator must complete fabric login and receive an FCID before normal fabric services can identify it. 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 fibre channel fabric login.
B:Inspect SAN port-channel summary, member compatibility results, link speeds and VSAN assignments. This concerns fibre channel port-channel consistency, not fibre channel fabric login.
C:Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs. This concerns fibre channel name-server entries, not fibre channel fabric login.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests