Sample questions
Cisco DCCOR / CCNP Data Center Core 350-601 practice questions
Refer to the exhibit. The interface fc1/1 is configured as an E_port. The connected switch also has an E_port configured. However, the interface shows an 'init' state. What is the most likely cause?
Exhibit
Refer to the exhibit. <config> interface fc1/1 switchport mode E switchport speed 16000 no shutdown </config>
Trap 1: The domain ID is not configured on either switch.
Domain IDs are assigned automatically or manually but are not required for E_port to come up.
Trap 2: The port VSAN on the local interface is different from the remote.
ISLs can carry multiple VSANs; VSAN mismatch does not prevent E_port initialization.
Trap 3: The remote switch interface is not configured as a trunk.
Trunk mode is not required for E_port; E_port is a type of trunk port.
- A
The domain ID is not configured on either switch.
Why wrong: Domain IDs are assigned automatically or manually but are not required for E_port to come up.
- B
The speed on the remote switch interface is set to 8000 Mbps.
E_ports require matching speed settings to establish a link.
- C
The port VSAN on the local interface is different from the remote.
Why wrong: ISLs can carry multiple VSANs; VSAN mismatch does not prevent E_port initialization.
- D
The remote switch interface is not configured as a trunk.
Why wrong: Trunk mode is not required for E_port; E_port is a type of trunk port.
Refer to the exhibit. After applying this configuration, the engineer activates the zoneset with 'zoneset activate name ZONESET1 vsan 10'. The host with pwwn 10:00:00:00:c9:aa:bb:01 can communicate with the target with pwwn 10:00:00:00:c9:aa:bb:02. However, the host reports that it cannot see a third target with pwwn 10:00:00:00:c9:aa:bb:03. What is the most likely reason?
Exhibit
Refer to the exhibit. <config> zone name ZONE1 vsan 10 member pwwn 10:00:00:00:c9:aa:bb:01 member pwwn 10:00:00:00:c9:aa:bb:02 zoneset name ZONESET1 vsan 10 member ZONE1 </config>
Trap 1: The third target is in a different VSAN.
The exhibit shows all members in VSAN 10; the target is likely in the same VSAN.
Trap 2: The zone name is case-sensitive and does not match.
The zone name in the exhibit is ZONE1; if the configuration matches, case is not an issue.
Trap 3: The zoneset was not activated successfully.
The activation command was executed; it would have generated an error if it failed.
- A
The third target is in a different VSAN.
Why wrong: The exhibit shows all members in VSAN 10; the target is likely in the same VSAN.
- B
The third target is not a member of ZONE1.
Zoning restricts access; only members of the same zone can communicate.
- C
The zone name is case-sensitive and does not match.
Why wrong: The zone name in the exhibit is ZONE1; if the configuration matches, case is not an issue.
- D
The zoneset was not activated successfully.
Why wrong: The activation command was executed; it would have generated an error if it failed.
A network engineer is troubleshooting a slow backup performance between a backup server and a tape library connected via FC. The backup server is connected to a Cisco MDS switch at 8 Gbps, and the tape library is connected at 4 Gbps. The backup job is using hardware compression. Which factor is most likely limiting performance?
Trap 1: Insufficient buffer credits on the MDS switch
Buffer credits affect long-distance links, not speed-limited performance.
Trap 2: Hardware compression on the tape library
Compression reduces data, improving performance, not limiting it.
Trap 3: Half-duplex mode on the FC link
FC always operates in full-duplex mode.
- A
Port speed mismatch between the server and tape library
The slower device (4 Gbps) determines the link speed.
- B
Insufficient buffer credits on the MDS switch
Why wrong: Buffer credits affect long-distance links, not speed-limited performance.
- C
Hardware compression on the tape library
Why wrong: Compression reduces data, improving performance, not limiting it.
- D
Half-duplex mode on the FC link
Why wrong: FC always operates in full-duplex mode.
A data center engineer is deploying a new application on Cisco UCS Manager. The application requires consistent low-latency access to storage. The engineer decides to use SAN boot from a Fibre Channel SAN. Which configuration change is necessary on the UCS service profile to enable SAN boot?
Trap 1: Enable VIF (Virtual Interface) on the vHBA
VIF is used in FCoE NPV mode, not for SAN boot.
Trap 2: Configure a QoS policy for the vHBA
QoS policy does not enable SAN boot.
Trap 3: Set the vNIC to use dynamic MAC address
Dynamic MAC is for LAN, not SAN boot.
- A
Enable VIF (Virtual Interface) on the vHBA
Why wrong: VIF is used in FCoE NPV mode, not for SAN boot.
- B
Configure a QoS policy for the vHBA
Why wrong: QoS policy does not enable SAN boot.
- C
Set the vNIC to use dynamic MAC address
Why wrong: Dynamic MAC is for LAN, not SAN boot.
- D
Assign a persistent WWPN to the vHBA
Persistent WWPN ensures the SAN target recognizes the server.
Which TWO are valid methods to configure a Cisco UCS service profile for stateless computing? (Choose two.)
Trap 1: Use boot from SAN to store OS images
Boot from SAN is a stateless boot method, not a configuration method.
Trap 2: Assign persistent WWPNs to vHBAs
Persistent WWPNs provide identity but are not a configuration method for stateless computing.
Trap 3: Configure local storage on the blade
Local storage introduces state; stateless uses SAN boot.
- A
Create a service profile from a template
A derived template inherits settings that can be updated centrally.
- B
Use boot from SAN to store OS images
Why wrong: Boot from SAN is a stateless boot method, not a configuration method.
- C
Assign persistent WWPNs to vHBAs
Why wrong: Persistent WWPNs provide identity but are not a configuration method for stateless computing.
- D
Configure local storage on the blade
Why wrong: Local storage introduces state; stateless uses SAN boot.
- E
Update the service profile template and re-apply to existing profiles
This propagates configuration changes without touching the hardware.
A data center engineer notices that a UCS B-Series blade server is failing to boot from a SAN LUN that is correctly mapped to the server's WWPN. The SAN switch shows that the LUN is accessible and the zone is configured correctly. The UCS Manager shows the server's vNIC is associated with a vHBA that has the correct WWPN, but the server's BIOS does not list the Fibre Channel boot target. Which configuration is most likely missing?
Trap 1: The SAN connectivity policy is missing the Fibre Channel uplink…
SAN connectivity policies define uplink ports but not boot targets.
Trap 2: The vNIC/vHBA placement policy is incorrectly set to 'Express' mode.
Placement policies affect adapter placement, not boot.
Trap 3: A QoS policy is not applied to the vHBA.
QoS policies affect traffic prioritization, not boot.
- A
The SAN connectivity policy is missing the Fibre Channel uplink pinning.
Why wrong: SAN connectivity policies define uplink ports but not boot targets.
- B
The vNIC/vHBA placement policy is incorrectly set to 'Express' mode.
Why wrong: Placement policies affect adapter placement, not boot.
- C
A QoS policy is not applied to the vHBA.
Why wrong: QoS policies affect traffic prioritization, not boot.
- D
The boot policy is not defined or not attached to the service profile.
UCS B-Series requires a boot policy to specify the boot order and target LUN.
Refer to the exhibit. An administrator updates template-B but its associated profile SP2 shows 'unassigned'. The administrator wants SP2 to reflect the changes. What should be done first?
Exhibit
Refer to the exhibit. UCS-A /org # show service-profile Name Assoc-State Oper-SrcTempl -------------- -------------- -------------- SP1 associated template-A SP2 unassigned template-B SP3 associated template-A SP4 associated template-C UCS-A /org # show service-profile template Name Type Oper-State --------------- --------- ----------- template-A initial enabled template-B updating enabled template-C initial enabled
Trap 1: Disable and re-enable template-B
Disabling does not associate profiles.
Trap 2: Wait for the automatic association to occur
Automatic association does not happen.
Trap 3: Rebind all profiles to template-B
Only unassociated profiles need binding.
- A
Disable and re-enable template-B
Why wrong: Disabling does not associate profiles.
- B
Wait for the automatic association to occur
Why wrong: Automatic association does not happen.
- C
Associate SP2 with template-B using the 'bind' operation
Binding creates the link between profile and template.
- D
Rebind all profiles to template-B
Why wrong: Only unassociated profiles need binding.
Refer to the exhibit. An engineer applies this QoS policy to a Cisco Nexus 9000 switch in a data center. After applying the policy, storage traffic (iSCSI) is experiencing high latency and occasional drops. The engineer verifies that the iSCSI traffic is not matching the 'BulkData' class. What is the most likely cause of the issue?
Exhibit
Refer to the exhibit.
<config>
<system>
<qos>
<class-map name="BulkData">
<match qos-group="5"/>
</class-map>
<policy-map name="DataCenter">
<class name="BulkData">
<set qos-group="5"/>
<bandwidth percent="30"/>
</class>
<class class-default>
<bandwidth percent="70"/>
</class>
</policy-map>
</qos>
</system>
</config>Trap 1: The policy-map is applied at the system level, but iSCSI traffic is…
iSCSI falls into class-default, but that doesn't cause drops; the lack of priority does.
Trap 2: The bandwidth percent for class-default is too low, causing iSCSI…
While 70% may be sufficient, the primary issue is lack of priority, not bandwidth starvation.
Trap 3: The class-map 'BulkData' does not match the correct traffic because…
Matching on qos-group is valid; the issue is not about matching.
- A
The policy-map does not specify a priority queue for latency-sensitive traffic.
iSCSI requires low latency; without a priority queue, it competes with other traffic.
- B
The policy-map is applied at the system level, but iSCSI traffic is not classified under any class-map.
Why wrong: iSCSI falls into class-default, but that doesn't cause drops; the lack of priority does.
- C
The bandwidth percent for class-default is too low, causing iSCSI to be starved.
Why wrong: While 70% may be sufficient, the primary issue is lack of priority, not bandwidth starvation.
- D
The class-map 'BulkData' does not match the correct traffic because the match statement uses qos-group instead of dscp.
Why wrong: Matching on qos-group is valid; the issue is not about matching.
A network engineer is troubleshooting a VXLAN EVPN problem where some endpoints are not reachable. The output of 'show bgp l2vpn evpn' shows Type-3 routes but no Type-2 routes for a specific VNI. What should the engineer check?
Trap 1: The route-target import/export is misconfigured.
Route-target misconfiguration would affect all route types, not just Type-2, and would be seen in other VNIs.
Trap 2: BGP session is not established.
If the BGP session were down, no EVPN routes (including Type-3) would be present.
Trap 3: The VNI is not configured under the NVE interface.
If the VNI were not under NVE, Type-3 routes (IMET) would also not be generated for that VNI.
- A
The route-target import/export is misconfigured.
Why wrong: Route-target misconfiguration would affect all route types, not just Type-2, and would be seen in other VNIs.
- B
BGP session is not established.
Why wrong: If the BGP session were down, no EVPN routes (including Type-3) would be present.
- C
The VNI is not configured under the NVE interface.
Why wrong: If the VNI were not under NVE, Type-3 routes (IMET) would also not be generated for that VNI.
- D
The VLAN corresponding to the VNI has no active ports.
Type-2 routes carry MAC/IP information. Without active ports in the VLAN, no MACs are learned, so no Type-2 routes are advertised.
A financial services firm has deployed Cisco UCS C-Series rack servers running VMware vSphere 7.0. They use Cisco Intersight for management. Recently, a critical application server (Server-A) became unresponsive. The Intersight dashboard shows the server's health status as 'Warning' with a firmware compliance alert: the server's Cisco Integrated Management Controller (CIMC) firmware version is 4.0(1a), while the Intersight firmware baseline is 4.2(1c). The server is running ESXi 7.0u2 on a local datastore. The storage is provided by a Cisco MDS switch via Fibre Channel. The server has two 10GbE uplinks to the fabric interconnect. The engineer notices that the vCenter Server cannot communicate with Server-A, and all VMs on that host are isolated. The engineer suspects the issue is related to the firmware mismatch. What is the most appropriate first step to resolve this issue while minimizing downtime?
Trap 1: Check vCenter logs to determine why communication failed.
Diagnostic step only; does not resolve the firmware mismatch.
Trap 2: Reinstall ESXi on Server-A to ensure a clean operating system.
Reinstalling ESXi does not address the firmware mismatch and may cause extended downtime.
Trap 3: Change the Intersight firmware baseline to match the current CIMC…
This resolves the alert but bypasses needed firmware updates and may lead to instability.
- A
Check vCenter logs to determine why communication failed.
Why wrong: Diagnostic step only; does not resolve the firmware mismatch.
- B
Reinstall ESXi on Server-A to ensure a clean operating system.
Why wrong: Reinstalling ESXi does not address the firmware mismatch and may cause extended downtime.
- C
Upgrade the CIMC firmware on Server-A from 4.0(1a) to 4.2(1c) using Intersight's firmware update capability.
Directly upgrades the firmware to the compliant version, resolving the underlying issue.
- D
Change the Intersight firmware baseline to match the current CIMC version (4.0(1a)).
Why wrong: This resolves the alert but bypasses needed firmware updates and may lead to instability.
A large enterprise is using Cisco UCS Manager to manage a chassis with 8 B-Series blades. The environment uses a combination of Ethernet and Fibre Channel traffic. The UCS fabric interconnect (FI) is configured in end-host mode with two uplinks to the core network. Recently, the engineering team deployed a new service profile for a high-performance computing workload that requires 40Gbps Ethernet per vNIC and 16Gbps Fibre Channel per vHBA. The server has two vNICs and two vHBAs. After deployment, the server's OS shows only 10Gbps connectivity on each vNIC. The engineer checks UCS Manager and sees that the vNIC templates are set to '10 Gbps' and the vHBA templates are set to '16 Gbps' but the actual link speed for vNICs is only 10Gbps. The fabric interconnect ports are configured as 40Gbps uplinks. The engineer has verified that the server adapter supports 40Gbps. What is the most likely cause of the speed mismatch?
Trap 1: The fabric interconnect uplinks are configured as 40Gbps, but the…
The uplinks are correct; the issue is at the vNIC template level, not the physical uplinks.
Trap 2: The server's adapter policy is set to 'Windows' mode, which limits…
Adapter policies affect the number of queues and capabilities, not the link speed.
Trap 3: The QoS policy applied to the vNIC limits the bandwidth to 10Gbps.
QoS policies shape traffic but do not change the negotiated link speed.
- A
The fabric interconnect uplinks are configured as 40Gbps, but the port channel is not configured correctly, causing speed negotiation to fail.
Why wrong: The uplinks are correct; the issue is at the vNIC template level, not the physical uplinks.
- B
The vNIC template used in the service profile specifies a requested speed of '10 Gbps' instead of '40 Gbps'.
The vNIC template's speed setting determines the allocated speed; it must be set to 40Gbps.
- C
The server's adapter policy is set to 'Windows' mode, which limits Ethernet speeds to 10Gbps.
Why wrong: Adapter policies affect the number of queues and capabilities, not the link speed.
- D
The QoS policy applied to the vNIC limits the bandwidth to 10Gbps.
Why wrong: QoS policies shape traffic but do not change the negotiated link speed.
A storage network engineer is designing a Fibre Channel SAN with two Cisco MDS switches in a single VSAN. The design requires that if one switch fails, the storage traffic continues to flow without manual intervention. Which two technologies should be implemented?
Trap 1: NPV
NPV reduces domain IDs but does not provide redundancy.
Trap 2: VSAN trunking
VSAN trunking allows multiple VSANs over a single link, not switch redundancy.
Trap 3: IVR
IVR is for inter-VSAN routing, not redundancy within a single VSAN.
- A
NPV
Why wrong: NPV reduces domain IDs but does not provide redundancy.
- B
Port channels
Port channels provide link redundancy but not switch-level redundancy.
- C
VSAN trunking
Why wrong: VSAN trunking allows multiple VSANs over a single link, not switch redundancy.
- D
IVR
Why wrong: IVR is for inter-VSAN routing, not redundancy within a single VSAN.
- E
Fibre Channel multipathing
Multipathing provides multiple paths between hosts and storage, enabling automatic failover.
A company is deploying FCoE in their data center. The design includes a Cisco Nexus 9000 switch with FEX modules. The storage team insists on using dedicated FCoE VLANs. Which best practice should be followed to ensure lossless behavior for FCoE traffic?
Trap 1: Configure traffic shaping on FCoE interfaces
Traffic shaping can introduce jitter and is not recommended for FCoE.
Trap 2: Use the same VLAN for FCoE and IP traffic to reduce VLAN count
FCoE should be on a dedicated VLAN to isolate lossless traffic.
Trap 3: Disable flow control on all interfaces
Flow control is needed for lossless operation.
- A
Configure traffic shaping on FCoE interfaces
Why wrong: Traffic shaping can introduce jitter and is not recommended for FCoE.
- B
Use the same VLAN for FCoE and IP traffic to reduce VLAN count
Why wrong: FCoE should be on a dedicated VLAN to isolate lossless traffic.
- C
Disable flow control on all interfaces
Why wrong: Flow control is needed for lossless operation.
- D
Enable PFC on the switch for the FCoE VLAN
PFC provides lossless behavior for the CoS used by FCoE.
Which THREE statements about Cisco UCS Manager automation using XML API are correct? (Choose three.)
Trap 1: The API uses SNMP for configuration changes.
The API uses XML over HTTP/HTTPS, not SNMP.
Trap 2: The UCS Manager XML API uses RESTful JSON format.
It uses XML, not JSON.
- A
Operations can be made idempotent by using the 'dn' (distinguished name) to specify the exact object.
Idempotency is achieved by targeting specific objects.
- B
The XML API is based on a management information model (MIT) similar to ACI.
UCS Manager uses a MIT similar to ACI.
- C
The API uses XML for both request and response payloads.
It is an XML-based API.
- D
The API uses SNMP for configuration changes.
Why wrong: The API uses XML over HTTP/HTTPS, not SNMP.
- E
The UCS Manager XML API uses RESTful JSON format.
Why wrong: It uses XML, not JSON.
A company has two Cisco MDS 9700 switches in a dual-fabric SAN. Each fabric has its own set of storage arrays and hosts. The company wants to enable selective communication between specific devices in Fabric A and Fabric B without merging the fabrics. Which Cisco technology should be used?
Trap 1: FCIP
FCIP is used to connect remote Fibre Channel fabrics over IP networks.
Trap 2: NPV
NPV is used to simplify edge switch configuration, not for inter-fabric communication.
Trap 3: Port channels
Port channels provide increased bandwidth and redundancy on a single link, not inter-fabric routing.
- A
FCIP
Why wrong: FCIP is used to connect remote Fibre Channel fabrics over IP networks.
- B
NPV
Why wrong: NPV is used to simplify edge switch configuration, not for inter-fabric communication.
- C
IVR
IVR enables selective communication between devices in different VSANs while keeping fabrics separate.
- D
Port channels
Why wrong: Port channels provide increased bandwidth and redundancy on a single link, not inter-fabric routing.
An engineer is designing an automation solution for a large data center with multiple Cisco UCS Manager domains. Which approach best ensures idempotent configuration operations?
Trap 1: Writing imperative Python scripts that execute CLI commands
Imperative scripts may not be idempotent unless carefully designed.
Trap 2: Directly calling UCS Manager XML API using POST requests
Without state tracking, operations may not be idempotent.
Trap 3: Using SNMP to set configuration parameters
SNMP is not idempotent and not suitable for configuration.
- A
Writing imperative Python scripts that execute CLI commands
Why wrong: Imperative scripts may not be idempotent unless carefully designed.
- B
Using a declarative automation tool like Ansible with idempotent modules
Declarative tools ensure the desired state is achieved regardless of current state.
- C
Directly calling UCS Manager XML API using POST requests
Why wrong: Without state tracking, operations may not be idempotent.
- D
Using SNMP to set configuration parameters
Why wrong: SNMP is not idempotent and not suitable for configuration.
A storage administrator reports that an FC initiator cannot log in to the SAN. The FC switch shows the following on the interface connected to the initiator: 'VSAN 100, State: Offline'. Which action should be taken to resolve the issue?
Trap 1: Create a zone including the initiator and target
Zoning does not affect link state; it controls device visibility.
Trap 2: Change the interface VSAN to match the initiator
The interface is already in VSAN 100 as shown by the state.
Trap 3: Increase the number of buffer credits on the interface
Buffer credits are not configured per port; they are negotiated between ports.
- A
Create a zone including the initiator and target
Why wrong: Zoning does not affect link state; it controls device visibility.
- B
Change the interface VSAN to match the initiator
Why wrong: The interface is already in VSAN 100 as shown by the state.
- C
Increase the number of buffer credits on the interface
Why wrong: Buffer credits are not configured per port; they are negotiated between ports.
- D
Configure port speed manually on the switch interface
Forcing the port speed can stop flapping and bring the link online.
A Cisco MDS switch has the above configuration on two 16 Gbps FC interfaces. An engineer connects an initiator to fc1/2 and a target to fc1/1. The initiator cannot discover the target. What is the most likely cause?
Exhibit
Refer to the exhibit. interface fc1/1 switchport mode E switchport rate-mode dedicated no shutdown interface fc1/2 switchport mode F switchport rate-mode shared no shutdown
Trap 1: The fc1/2 interface is configured as an F-port but the initiator…
F-port is correct for a single initiator; FL-port is for arbitrated loop.
Trap 2: The fc1/1 interface is configured as dedicated rate-mode but the…
Rate-mode affects bandwidth allocation, not device discovery.
Trap 3: The fc1/2 interface is configured as shared rate-mode which…
Shared rate-mode is allowed on F-ports.
- A
The fc1/2 interface is configured as an F-port but the initiator requires an FL-port.
Why wrong: F-port is correct for a single initiator; FL-port is for arbitrated loop.
- B
The fc1/1 interface is configured as dedicated rate-mode but the target expects shared.
Why wrong: Rate-mode affects bandwidth allocation, not device discovery.
- C
The fc1/2 interface is configured as shared rate-mode which prevents F-port operation.
Why wrong: Shared rate-mode is allowed on F-ports.
- D
The fc1/1 interface is configured as an E-port but is connected to a storage target.
An E-port is for inter-switch links; the target should be connected to an F-port.
Refer to the exhibit. An automation script queries the Cisco Nexus 9000 using the NX-API JSON format and receives the above output. The script is designed to validate that interface Eth1/1 is in access mode with VLAN 100. However, the script reports a failure. What is the most likely reason?
Exhibit
Refer to the exhibit.
{
"totalCount": "1",
"imdata": [
{
"l1PhysIf": {
"attributes": {
"id": "Eth1/1",
"adminSt": "up",
"descr": "To-Server",
"mtu": "1500",
"switchportMode": "access",
"accessVlan": "100"
}
}
}
]
}Trap 1: The JSON output is malformed and cannot be parsed.
The JSON is valid.
Trap 2: The interface is administratively down.
The output shows 'adminSt': 'up'.
Trap 3: The JSON output is missing the 'switchportMode' field.
The output includes 'switchportMode'.
- A
The script uses strict type checking, and the values are returned as strings instead of integers.
JSON returns numbers as strings in this context; a type mismatch causes failure.
- B
The JSON output is malformed and cannot be parsed.
Why wrong: The JSON is valid.
- C
The interface is administratively down.
Why wrong: The output shows 'adminSt': 'up'.
- D
The JSON output is missing the 'switchportMode' field.
Why wrong: The output includes 'switchportMode'.
A data center engineer is designing a storage network for a virtualized environment with 100 hosts and 50 storage arrays. Each host requires 4 Gbps of bandwidth to storage, and each storage array provides 8 Gbps. All devices use 16 Gbps FC links. What is the minimum number of 16 Gbps FC links required to support the total bandwidth demand without oversubscription?
Trap 1: 50
50 links would provide 800 Gbps, which is double the requirement.
Trap 2: 200
200 links are excessive for the bandwidth requirement.
Trap 3: 100
100 links are more than needed; demand is 400 Gbps.
- A
50
Why wrong: 50 links would provide 800 Gbps, which is double the requirement.
- B
200
Why wrong: 200 links are excessive for the bandwidth requirement.
- C
100
Why wrong: 100 links are more than needed; demand is 400 Gbps.
- D
25
25 links provide 400 Gbps of bandwidth (16 Gbps each) to meet total demand.
A large enterprise is deploying a new storage network for a VMware vSphere cluster with 200 VMs. The cluster uses vSphere 7 with vVols and requires a SAN that supports 16 Gbps FC. The storage team wants to use a Cisco MDS 9148S switch and has configured two VSANs: VSAN 100 for production and VSAN 200 for backup. The backup server is connected to VSAN 200. After the deployment, the backup administrator reports that backup jobs from the backup server to the storage array are failing. The storage array is connected to both VSANs via a single FC interface configured in 'auto' mode. The backup server is connected to an F-port in VSAN 200. The storage array's interface shows 'trunking' enabled and is in 'up' state. What is the most likely cause of the backup failure?
Trap 1: Move the backup server to VSAN 100 to match the production storage.
The backup server is intended to be in VSAN 200; moving it would not fix the underlying trunking issue.
Trap 2: Change the storage array interface to 'F' mode to force it to be in…
Changing to F mode would limit the array to one VSAN, but the array needs to be in both VSANs.
Trap 3: Disable trunking on the storage array interface to prevent VSAN…
Trunking is required for the array to be in multiple VSANs; disabling it would cause loss of connectivity to one VSAN.
- A
Configure the MDS switch interface connected to the storage array as a trunk port and ensure VSAN 200 is in the allowed list.
This allows the array to be in both VSANs and ensures the backup server can communicate with the array.
- B
Move the backup server to VSAN 100 to match the production storage.
Why wrong: The backup server is intended to be in VSAN 200; moving it would not fix the underlying trunking issue.
- C
Change the storage array interface to 'F' mode to force it to be in a single VSAN.
Why wrong: Changing to F mode would limit the array to one VSAN, but the array needs to be in both VSANs.
- D
Disable trunking on the storage array interface to prevent VSAN mismatch.
Why wrong: Trunking is required for the array to be in multiple VSANs; disabling it would cause loss of connectivity to one VSAN.
A network engineer is implementing automated configuration management using Cisco NSO (Network Services Orchestrator). The team wants to ensure that any configuration changes made directly on the devices (out-of-band) are detected and reconciled. Which NSO feature should be used?
Trap 1: Configuration Database (CDB) snapshots
CDB stores configurations but does not detect out-of-band changes.
Trap 2: Service model templates
Service models define services, not detection of out-of-band changes.
Trap 3: Rollback and recovery mechanism
Rollback is used after changes are made.
- A
Configuration Database (CDB) snapshots
Why wrong: CDB stores configurations but does not detect out-of-band changes.
- B
Fast-map synchronization
Fast-map syncs device configurations with NSO and detects drift.
- C
Service model templates
Why wrong: Service models define services, not detection of out-of-band changes.
- D
Rollback and recovery mechanism
Why wrong: Rollback is used after changes are made.
Which TWO statements about Cisco NX-API are correct? (Choose two.)
Trap 1: NX-API uses SSH for transport.
NX-API uses HTTP/HTTPS, not SSH.
Trap 2: NX-API only supports GET requests.
NX-API supports POST, GET, PUT, DELETE.
Trap 3: NX-API is only available on Nexus 3000 series switches.
NX-API is available on Nexus 9000, 7000, 3000 series.
- A
NX-API uses SSH for transport.
Why wrong: NX-API uses HTTP/HTTPS, not SSH.
- B
NX-API only supports GET requests.
Why wrong: NX-API supports POST, GET, PUT, DELETE.
- C
NX-API uses HTTP/HTTPS as the transport protocol.
NX-API is a RESTful API over HTTP/HTTPS.
- D
NX-API is only available on Nexus 3000 series switches.
Why wrong: NX-API is available on Nexus 9000, 7000, 3000 series.
- E
NX-API can output data in XML and JSON formats.
NX-API supports both XML and JSON.
Refer to the exhibit. An automation script is used to configure a new VLAN 40 on Eth1/2 trunk. The script sends the following NX-API command: 'switchport trunk allowed vlan add 40'. After execution, the engineer runs 'show running-config interface eth1/2' and sees that the trunk allowed VLAN list shows '10,20,30,40'. However, the automation script logs indicate success for adding VLAN 40, but the running config does not show the change. What is the most likely issue?
Exhibit
Refer to the exhibit. interface Eth1/1 description Server-Connection switchport mode access switchport access vlan 100 spanning-tree port type edge no shutdown interface Eth1/2 description Trunk-to-Core switchport mode trunk switchport trunk allowed vlan 10,20,30 spanning-tree port type network no shutdown
Trap 1: The command syntax is incorrect; 'add' is not a valid keyword.
The 'add' keyword is valid for adding VLANs to the allowed list.
Trap 2: The script actually removed the existing VLANs and replaced them…
The running config shows the list includes all VLANs, so it was not replaced.
Trap 3: The NX-API command was sent to the wrong interface.
The command targeted Eth1/2, and the running config shows that interface.
- A
The command syntax is incorrect; 'add' is not a valid keyword.
Why wrong: The 'add' keyword is valid for adding VLANs to the allowed list.
- B
The engineer is viewing a different switch or the configuration was reverted by another process.
The running config shows the change, so the issue is likely that the engineer is looking at the wrong device or the config was changed after.
- C
The script actually removed the existing VLANs and replaced them with only VLAN 40.
Why wrong: The running config shows the list includes all VLANs, so it was not replaced.
- D
The NX-API command was sent to the wrong interface.
Why wrong: The command targeted Eth1/2, and the running config shows that interface.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.