Question 500
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 information should be inspected before the change is applied?
- Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts.
- Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs.
- Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules.
- Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting.
Explanation
Correct Answer
C:Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. 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.
B:Inspect role definitions, AAA authorization, zone management privileges and administrative audit logs. This concerns mds SAN administrative control, not aci inter-epg contract.
D:Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. 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.
Question 501
A UCS-X chassis is physically installed but policies authored for a legacy UCS Manager workflow cannot be assigned to its server profiles. Operations is validating the host before approving production workload placement. Which controlled change is most appropriate given the evidence?
- Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path.
- Check organization membership and resource-group scope before broadening permissions globally.
- Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status.
- Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies.
Explanation
Correct Answer
D:Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies. UCS-X in Intersight Managed Mode uses Intersight-defined policies and profiles rather than unmodified UCS Manager assumptions. Operations is validating the host before approving production workload placement.
Incorrect Answers
A:Configure an authorized traffic mirror or supported capture point to observe the affected vNIC path. This concerns compute traffic span, not UCS-x intersight managed mode.
B:Check organization membership and resource-group scope before broadening permissions globally. That response is associated with intersight organization scope rather than the specific ucs-x intersight managed mode condition described here. For the stated failure, the preferred action is: Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies. Relevant evidence: Inspect connected domain registration, Intersight inventory, firmware compatibility and target policy types. Operations is validating the host before approving production workload placement.
C:Assign the approved domain profile with its LAN/SAN uplink policies and verify deployment status. That response is associated with intersight domain profile rather than the specific ucs-x intersight managed mode condition described here. For the stated failure, the preferred action is: Manage the chassis through its supported Intersight Managed Mode domain and compatible server-profile policies. Relevant evidence: Inspect connected domain registration, Intersight inventory, firmware compatibility and target policy types. Operations is validating the host before approving production workload placement.
Question 502
A Nexus switch upgrade has been described as nondisruptive, but the running hardware and target image are not confirmed as ISSU compatible. The team is preparing a controlled production change and must preserve fabric reachability. Which observations would best validate the initial diagnosis?
- 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.
- Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements.
- Inspect subscription configuration, sensor paths, timestamps, drop counters and collector ingestion.
Explanation
Correct Answer
C:Inspect current and target release, hardware support matrix, upgrade-impact output and application requirements. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Nondisruptive software upgrade support is platform, topology and image-path dependent and must be verified. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:Inspect HSRP or VRRP group IDs, virtual IPs, priorities, tracking and peer status. This concerns first-hop gateway failover, not nexus issu eligibility.
B:Inspect PIM neighbors, RP mapping, join state and reverse-path-forwarding interfaces. This concerns PIM multicast rendezvous point, not nexus issu eligibility.
D:Inspect subscription configuration, sensor paths, timestamps, drop counters and collector ingestion. This concerns streaming telemetry health, not nexus issu eligibility.
Question 503
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. What information should be inspected before the change is applied?
- Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables.
- Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps.
- Inspect HCL guidance, firmware policy contents, host driver versions and maintenance impact.
- Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs.
Explanation
Correct Answer
A:Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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
B:Inspect vNIC QoS policies, DCB settings if applicable, interface queue drops and upstream class maps. This concerns UCS network qos policy, not UCS mac pool uniqueness.
C:Inspect HCL guidance, firmware policy contents, host driver versions and maintenance impact. This concerns UCS firmware compatibility, not UCS mac pool uniqueness.
D:Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs. This concerns UCS VLAN pool and template, not UCS mac pool uniqueness.
Question 504
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. Which observations would best validate the initial diagnosis?
- Inspect role grants, resource-group associations, organization context and API access evidence.
- Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology.
- Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs.
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
Explanation
Correct Answer
A: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. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
B:Inspect DHCP snooping trust configuration, VLAN enrollment, packet drops and server uplink topology. This concerns DHCP snooping trusted uplink, not intersight scoped operations.
C:Inspect DAI drop counters, DHCP snooping binding table, static host assignments and ARP inspection logs. This concerns dynamic ARP inspection source of truth, not intersight scoped operations.
D:Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons. This concerns first-hop ip/mac spoof defense, not intersight scoped operations.
Question 505
An automated UCS association binds a high-memory workload to a blade that lacks the required adapter capability. 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?
- A template update must not be assumed to affect just the blade presently open in the UI.
- An FC link up indication alone cannot prove that the boot LUN is authorized and reachable.
- Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs.
- A unique server serial number does not replace unique Fibre Channel initiator identifiers.
Explanation
Correct Answer
C:Manual association to an incompatible blade may bypass placement intent without satisfying hardware needs. Pool qualification policies can restrict association based on compatible server hardware characteristics. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:A template update must not be assumed to affect just the blade presently open in the UI. This concerns updating service-profile templates, not server pool qualification.
B:An FC link up indication alone cannot prove that the boot LUN is authorized and reachable. This concerns SAN boot path policy, not server pool qualification.
D:A unique server serial number does not replace unique Fibre Channel initiator identifiers. This concerns wwpn pool allocation, not server pool qualification.
Question 506
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 observations would best validate the initial diagnosis?
- Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding.
- Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs.
- Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs.
- Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility.
Explanation
Correct Answer
C:Inspect IOM link state, chassis faults, discovery status and fabric interconnect logs. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect vNIC fabric bindings, uplink port channels, failover policy and upstream switch forwarding. This concerns UCS fabric redundancy, not UCS blade chassis IOM discovery.
B:Inspect effective vNIC templates, VLAN object assignments, LAN uplink trunk allowances and fault logs. This concerns UCS VLAN pool and template, not UCS blade chassis IOM discovery.
D:Inspect service-profile boot targets, FLOGI, active zones, array masking and target LUN visibility. This concerns SAN boot path policy, not UCS blade chassis IOM discovery.
Question 507
An ACI endpoint attaches to a leaf interface but never receives its expected VLAN encapsulation because the domain is not bound to the access policy chain. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. What post-change observation gives the strongest evidence of success?
- After maintenance, all required components report the intended EPLD versions and forwarding passes health checks.
- The target encapsulation is programmed on the intended port and endpoint learning succeeds.
- Virtual endpoints are learned in the intended EPG and their traffic follows its applied contracts.
- The leaf appears as a registered healthy fabric member with the expected role and adjacency.
Explanation
Correct Answer
B:The target encapsulation is programmed on the intended port and endpoint learning succeeds. This result tests the original failure rather than reporting merely that the configuration command was accepted. ACI access policies rely on a consistent domain and attachment chain before deploying the correct encapsulation. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:After maintenance, all required components report the intended EPLD versions and forwarding passes health checks. This concerns epld firmware maintenance, not aci access policy chain.
C:Virtual endpoints are learned in the intended EPG and their traffic follows its applied contracts. This concerns aci vmm association, not aci access policy chain.
D:The leaf appears as a registered healthy fabric member with the expected role and adjacency. This concerns aci fabric discovery, not aci access policy chain.
Question 508
An administrator imports a service-profile template and two new server identities unexpectedly request an overlapping MAC range. Operations is validating the host before approving production workload placement. What is the best next implementation or troubleshooting step?
- Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment.
- Validate backup age, identity-pool effects and restore prerequisites before applying the saved configuration.
- Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path.
- Review UCS QoS classes and upstream priority handling across the entire network path.
Explanation
Correct Answer
A:Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment. UCS identity pools must avoid reuse because overlapping MAC addresses can cause Layer 2 instability and confusing endpoint learning. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:Validate backup age, identity-pool effects and restore prerequisites before applying the saved configuration. This concerns UCS restore integrity, not UCS mac pool uniqueness.
C:Align the vNIC template VLAN membership and upstream VLAN allowance across the chosen fabric path. That response is associated with ucs vlan pool and template rather than the specific ucs mac pool uniqueness condition described here. For the stated failure, the preferred action is: Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment. Relevant evidence: Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. Operations is validating the host before approving production workload placement.
D:Review UCS QoS classes and upstream priority handling across the entire network path. That response is associated with ucs network qos policy rather than the specific ucs mac pool uniqueness condition described here. For the stated failure, the preferred action is: Separate the relevant MAC pool ranges and confirm all instantiated identities are unique before attachment. Relevant evidence: Inspect MAC pool definitions, reservations, effective vNIC addresses and upstream MAC tables. Operations is validating the host before approving production workload placement.
Question 509
A helpdesk operator needs to review UCS server faults but accidentally receives access to modify global SAN policies. Security engineering must restore the approved service without relaxing unrelated protection. Which observations would best validate the initial diagnosis?
- Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts.
- Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting.
- Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules.
- Inspect UCS role privileges, organization assignments, recent actions and denied command records.
Explanation
Correct Answer
D:Inspect UCS role privileges, organization assignments, recent actions and denied command records. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Compute management RBAC should separate routine inspection from high-impact infrastructure changes. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Inspect VM attributes, uSeg EPG selectors, endpoint placement and resulting enforced contracts. This concerns aci microsegmentation selector, not UCS administrative separation.
B:Inspect TACACS+ reachability, AAA method lists, local credentials and access accounting. This concerns centralized AAA fallback, not UCS administrative separation.
C:Inspect EPG bindings, contracts, subject filters, provider-consumer association and zoning rules. This concerns aci inter-epg contract, not UCS administrative separation.
Question 510
A server access network contains a deliberate redundant Layer 2 path, and one uplink is discarding frames under RSTP. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence. How should the implementation be validated against the original failure?
- The identified path issue is reproduced in telemetry and resolved with measurable service recovery.
- The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault.
- Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state.
- All intended links join the same logical bundle and traffic is distributed without individual member flaps.
Explanation
Correct Answer
B:The intended root remains stable, the active forwarding path operates and the redundant link converges after a fault. This result tests the original failure rather than reporting merely that the configuration command was accepted. RSTP prevents Layer 2 loops by assigning port roles and discarding redundant paths when necessary. A second maintenance window is approaching, and the engineer must confirm the same failure mode using current device evidence.
Incorrect Answers
A:The identified path issue is reproduced in telemetry and resolved with measurable service recovery. This concerns nexus dashboard fabric visibility, not rstp blocked uplink.
C:Peer-link adjacency and vPC consistency return healthy, and affected ports resume forwarding without a dual-active state. This concerns vpc peer-link recovery, not rstp blocked uplink.
D:All intended links join the same logical bundle and traffic is distributed without individual member flaps. This concerns lacp member mismatch, not rstp blocked uplink.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests