Question 300
An automated UCS association binds a high-memory workload to a blade that lacks the required adapter capability. Operations is validating the host before approving production workload placement. Which test result best demonstrates restoration of the intended behavior?
- The workload profile attaches only to blades meeting the declared capacity and adapter criteria.
- The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles.
- The blade discovers the intended boot LUN and boots after a controlled restart.
- Only the approved profile scope receives the tested update, with unrelated services preserved.
Explanation
Correct Answer
A:The workload profile attaches only to blades meeting the declared capacity and adapter criteria. This result tests the original failure rather than reporting merely that the configuration command was accepted. Pool qualification policies can restrict association based on compatible server hardware characteristics. Operations is validating the host before approving production workload placement.
Incorrect Answers
B:The chassis and blades enroll in the correct domain and receive valid Intersight-managed profiles. This concerns UCS-x intersight managed mode, not server pool qualification.
C:The blade discovers the intended boot LUN and boots after a controlled restart. That response is associated with san boot path policy rather than the specific server pool qualification condition described here. For the stated failure, the preferred action is: Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies. Relevant evidence: Inspect server inventory, qualification criteria, pool membership and association failures. Operations is validating the host before approving production workload placement.
D:Only the approved profile scope receives the tested update, with unrelated services preserved. That response is associated with updating service-profile templates rather than the specific server pool qualification condition described here. For the stated failure, the preferred action is: Correct server-pool qualifications and service-profile placement criteria for the workload's hardware dependencies. Relevant evidence: Inspect server inventory, qualification criteria, pool membership and association failures. Operations is validating the host before approving production workload placement.
Question 301
An unauthorized initiator plugs into an available SAN switch port and attempts fabric login using an unapproved WWPN. A follow-up access review asks the team to validate the same boundary with a controlled negative test. What post-change observation gives the strongest evidence of success?
- Only approved device identities log in and the unauthorized initiator is denied without disrupting valid paths.
- Approved switches form the fabric while an unknown switch cannot join through the protected link.
- The administrator can inspect zone status while unauthorized zone modification is blocked and recorded.
- The operator can read faults but cannot alter fabric-wide SAN settings, with access attempts audited.
Explanation
Correct Answer
A:Only approved device identities log in and the unauthorized initiator is denied without disrupting valid paths. This result tests the original failure rather than reporting merely that the configuration command was accepted. FC port security can restrict which device WWNs are permitted to connect through designated fabric ports. A follow-up access review asks the team to validate the same boundary with a controlled negative test.
Incorrect Answers
B:Approved switches form the fabric while an unknown switch cannot join through the protected link. This concerns fabric binding membership, not fibre channel port security.
C:The administrator can inspect zone status while unauthorized zone modification is blocked and recorded. This concerns mds SAN administrative control, not fibre channel port security.
D:The operator can read faults but cannot alter fabric-wide SAN settings, with access attempts audited. This concerns UCS administrative separation, not fibre channel port security.
Question 302
A network inventory script reports only the first hundred switches even though Nexus Dashboard shows more devices. The automation change must pass a preproduction test and leave a verifiable audit trail. Which evidence set most directly tests the suspected failure?
- 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 DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs.
- Inspect API logs, resource identifiers, HTTP response history and current running object state.
Explanation
Correct Answer
A: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. The automation change must pass a preproduction test and leave a verifiable audit trail.
Incorrect Answers
B:Inspect Ansible change output, module behavior, running configurations and intended-state version control. That response is associated with ansible idempotent templates rather than the specific python api pagination condition described here. For the stated failure, the preferred action is: Implement documented pagination and response-error handling in the inventory API client. Relevant evidence: Inspect response metadata, page limits, next tokens, error responses and known inventory counts. The automation change must pass a preproduction test and leave a verifiable audit trail.
C:Inspect DHCP offers, bootstrap URL, DNS/routing, file server availability and switch console logs. That response is associated with poap bootstrap dependencies rather than the specific python api pagination condition described here. For the stated failure, the preferred action is: Implement documented pagination and response-error handling in the inventory API client. Relevant evidence: Inspect response metadata, page limits, next tokens, error responses and known inventory counts. The automation change must pass a preproduction test and leave a verifiable audit trail.
D:Inspect API logs, resource identifiers, HTTP response history and current running object state. This concerns rest api retries and idempotence, not python api pagination.
Question 303
A VXLAN VTEP can ping peers but no EVPN address-family neighbor is established and remote MAC/IP routes are absent. The team is preparing a controlled production change and must preserve fabric reachability. What should the operator avoid assuming from the observed state?
- An RP mapping correction will not compensate for broken RPF reachability to the multicast source.
- A working IPv4 OSPFv2 adjacency does not establish IPv6 OSPFv3 reachability by itself.
- Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes.
- A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly.
Explanation
Correct Answer
C:Data-plane tunnel reachability does not imply correct import or export of the tenant's EVPN routes. EVPN distributes MAC and IP reachability using MP-BGP; underlay IP reachability alone cannot populate those bindings. The team is preparing a controlled production change and must preserve fabric reachability.
Incorrect Answers
A:An RP mapping correction will not compensate for broken RPF reachability to the multicast source. That response is associated with pim multicast rendezvous point rather than the specific mp-bgp evpn route learning condition described here. For the stated failure, the preferred action is: Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane. Relevant evidence: Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. The team is preparing a controlled production change and must preserve fabric reachability.
B:A working IPv4 OSPFv2 adjacency does not establish IPv6 OSPFv3 reachability by itself. That response is associated with ospfv3 ipv6 neighbor discovery rather than the specific mp-bgp evpn route learning condition described here. For the stated failure, the preferred action is: Check the EVPN address family peering and route-type advertisements before altering the VXLAN data plane. Relevant evidence: Inspect EVPN BGP neighbor state, advertised Type-2 routes, route targets and the corresponding VNI. The team is preparing a controlled production change and must preserve fabric reachability.
D:A unicast EVPN route alone does not ensure that every broadcast frame is replicated correctly. This concerns bum replication behavior, not mp-BGP evpn route learning.
Question 304
An administrator can see one domain in Intersight but cannot create profiles for a different business unit's assigned equipment. 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?
- Successful one-time installation does not ensure the persistent boot policy has been corrected.
- An existing UCS Manager service-profile template is not automatically an Intersight server-profile resource.
- Global administrator access is unnecessary when scoped resource assignment solves the visibility issue.
- Configuring only a server profile does not establish the upstream domain-fabric configuration.
Explanation
Correct Answer
C:Global administrator access is unnecessary when scoped resource assignment solves the visibility issue. Intersight resource assignment and RBAC limit which infrastructure objects and policies an administrator can manage. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:Successful one-time installation does not ensure the persistent boot policy has been corrected. This concerns boot order and removable media, not intersight organization scope.
B:An existing UCS Manager service-profile template is not automatically an Intersight server-profile resource. This concerns UCS-x intersight managed mode, not intersight organization scope.
D:Configuring only a server profile does not establish the upstream domain-fabric configuration. This concerns intersight domain profile, not intersight organization scope.
Question 305
A new C-Series rack server powers on but its management controller cannot be reached from the secure operations subnet. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state. What should the operator avoid assuming from the observed state?
- A high-availability label does not guarantee there is sufficient spare capacity for concurrent outages.
- Configuring only a server profile does not establish the upstream domain-fabric configuration.
- An operating-system network driver cannot repair an isolated hardware management interface.
- The newest firmware for each component is not necessarily a supported combination when mixed arbitrarily.
Explanation
Correct Answer
C: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. The issue reappears on a second managed host, so the team is checking its effective profiles and hardware state.
Incorrect Answers
A:A high-availability label does not guarantee there is sufficient spare capacity for concurrent outages. This concerns UCS firmware change sequencing, not UCS c-series cimc reachability.
B:Configuring only a server profile does not establish the upstream domain-fabric configuration. This concerns intersight domain profile, not UCS c-series cimc reachability.
D:The newest firmware for each component is not necessarily a supported combination when mixed arbitrarily. This concerns UCS firmware compatibility, not UCS c-series cimc reachability.
Question 306
During an OSPF key rollover, one peer begins rejecting signed hello packets even though the links remain up. Security engineering must restore the approved service without relaxing unrelated protection. Which observations would best validate the initial diagnosis?
- Inspect switch WWN bindings, ISL neighbors, fabric membership and enforcement violation logs.
- Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters.
- Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state.
- Inspect source guard state, DHCP snooping bindings, static exceptions and ingress drop reasons.
Explanation
Correct Answer
C:Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Routing-protocol authentication needs overlapping compatible keys during a planned rollover to preserve adjacency. Security engineering must restore the approved service without relaxing unrelated protection.
Incorrect Answers
A:Inspect switch WWN bindings, ISL neighbors, fabric membership and enforcement violation logs. This concerns fabric binding membership, not routing protocol keychain rollover.
B:Inspect platform capability, MACsec session state, MKA status, cipher suite and protected traffic counters. That response is associated with macsec protection scope rather than the specific routing protocol keychain rollover condition described here. For the stated failure, the preferred action is: Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. Relevant evidence: Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state. Security engineering must restore the approved service without relaxing unrelated protection.
D: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 routing protocol keychain rollover condition described here. For the stated failure, the preferred action is: Coordinate authentication key IDs, algorithms and valid lifetimes across both peers before retiring the old key. Relevant evidence: Inspect keychain definitions, active key lifetimes, authentication error logs and neighbor state. Security engineering must restore the approved service without relaxing unrelated protection.
Question 307
An MDS operator edits the configured zoneset but a host still cannot discover the newly authorized storage target. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN. What information should be inspected before the change is applied?
- Inspect alias database, recorded target WWPNs, zones using the alias and change approvals.
- Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices.
- Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs.
- Inspect active zoneset, configured zoneset, VSAN ID and activation history.
Explanation
Correct Answer
D:Inspect active zoneset, configured zoneset, VSAN ID and activation history. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Configured zones and active enforced zoning can differ until the appropriate zoneset is activated. During the next path-failover exercise, the SAN team must confirm the same dependency on the affected VSAN.
Incorrect Answers
A:Inspect alias database, recorded target WWPNs, zones using the alias and change approvals. This concerns device alias maintenance, not zoneset activation state.
B:Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. This concerns single-initiator zoning, not zoneset activation state.
C:Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs. This concerns fibre channel name-server entries, not zoneset activation state.
Question 308
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. What should the engineer collect before ruling out other causes?
- Inspect interface-to-VSAN membership, active zonesets, fabric IDs and authorized inter-VSAN designs.
- Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries.
- Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs.
- Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links.
Explanation
Correct Answer
D:Inspect trunk allowed lists, operational VSANs, fcdomain state and VSAN-specific fabric links. These records help distinguish the suspected failure from a superficially similar fault before modifying production. 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:Inspect interface-to-VSAN membership, active zonesets, fabric IDs and authorized inter-VSAN designs. This concerns VSAN isolation, not VSAN trunk mismatch.
B:Inspect FLOGI port WWPNs, host vHBA identities, target port IDs and zoning entries. This concerns wwpn versus wwnn, not VSAN trunk mismatch.
C:Inspect FCNS database, FLOGI records, target WWPN, VSAN association and port transition logs. This concerns fibre channel name-server entries, not VSAN trunk mismatch.
Question 309
A SAN change places multiple unrelated hosts and several targets in one broad Fibre Channel zone to simplify access. A storage change board requires a traceable diagnosis before allowing further fabric changes. Which evidence set most directly tests the suspected failure?
- Inspect CFS peers, lock ownership, pending changes, feature status and activation records.
- Inspect active zoneset, configured zoneset, VSAN ID and activation history.
- Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices.
- Inspect target portal IPs, IQN access rules, CHAP policy, TCP reachability and multipath sessions.
Explanation
Correct Answer
C:Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. These records help distinguish the suspected failure from a superficially similar fault before modifying production. Tightly scoped FC zones limit which initiators can discover or communicate with designated targets. A storage change board requires a traceable diagnosis before allowing further fabric changes.
Incorrect Answers
A:Inspect CFS peers, lock ownership, pending changes, feature status and activation records. That response is associated with cisco fabric services distribution rather than the specific single-initiator zoning condition described here. For the stated failure, the preferred action is: Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone. Relevant evidence: Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. A storage change board requires a traceable diagnosis before allowing further fabric changes.
B:Inspect active zoneset, configured zoneset, VSAN ID and activation history. That response is associated with zoneset activation state rather than the specific single-initiator zoning condition described here. For the stated failure, the preferred action is: Apply a least-privilege zoning design with an individual initiator and explicitly approved target members per zone. Relevant evidence: Inspect active zone members, initiator WWPNs, target WWPNs and intended host-to-LUN access matrices. A storage change board requires a traceable diagnosis before allowing further fabric changes.
D:Inspect target portal IPs, IQN access rules, CHAP policy, TCP reachability and multipath sessions. This concerns iscsi target discovery, not single-initiator zoning.
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.
Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests