The Implementing Cisco Data Center Core Technologies (350-601 DCCOR) (350-601)

The correct answer is B. Cisco UCS traffic monitoring is fabric-local, meaning a monitoring destination is a single physical port on one fabric interconnect, so one session cannot monitor both fabrics at the same time. Cisco documentation states that to monitor a vNIC with fabric failover enabled without losing visibility during an FI failure, you must create two monitoring sessions, one per fabric, connect two analyzers, and add the vNIC as the traffic source using the exact same session name for both sessions.

That requirement eliminates options C and D, because both try to use an analyzer on only one FI for both sessions, which violates the rule that all traffic sources and destination ports must remain on the same local fabric. Option A is also incorrect because Cisco specifically says to use the same name for both sessions when monitoring uninterrupted vNIC traffic across a fabric failover. Therefore, the only configuration that preserves monitoring during normal operation and during a fabric failover event is two same-named sessions, one per fabric, each with its own local analyzer destination.

The correct answer is B because Cisco OSPF MD5 authentication on an interface requires two specific elements: enabling message-digest authentication and defining a message-digest key. On Cisco platforms, the correct syntax is:

ip ospf authentication message-digest

ip ospf message-digest-key < key-id > md5 < encryption-type > < password >

In this question, the engineer must use MD5 and store the password using 3DES encryption, which corresponds to encryption type 3 in Cisco syntax. Therefore, ip ospf message-digest-key 2 md5 3 P@ssw01 is the valid form. The key ID can be any matching integer on both neighbors, and here it is 2.

Option A is incorrect because authentication-key is used for simple password authentication, not MD5 message-digest authentication. Option C is incorrect because ip ospf authentication md5 is not the NX-OS/IOS syntax used here; Cisco uses authentication message-digest. Option D is invalid because authentication-key does not take md5 in that format.

So the issue is resolved only by enabling message-digest authentication and configuring the MD5 key with encryption type 3, which is exactly what B does.

The correct answer is C because the requirement is to monitor the traffic sent to the server. In the diagram, the server is connected downstream through the intermediate switch, and N9K1 connects toward that path on interface Eth1/1. On Cisco NX-OS SPAN, the direction keyword is important: tx captures frames transmitted out of the selected source interface, while rx captures frames received into that interface.

Since traffic destined for the server leaves N9K1 out Eth1/1, the proper source is source interface eth1/1 tx. That mirrored traffic is then forwarded to the analyzer connected on the SPAN destination interface.

Option D is incorrect because rx on Eth1/1 would monitor traffic arriving from the downstream switch toward N9K1, not traffic being sent to the server. Option A is incorrect because Eth1/3 is on the downstream switch, not on N9K1. Option B uses an invalid interface reference for this topology.

Therefore, to capture traffic heading from N9K1 toward the server, the correct SPAN source on N9K1 is Eth1/1 in the transmit direction.

The correct answer is B because Cisco Nexus 9000 switches that support NX-OS with Linux Bash shell require a two-step process when a feature is delivered as an RPM package. First, the feature must be installed at the Linux level using the Bash shell and the yum package manager. This is done with the command:

sudo yum -y install bgp

This step installs the necessary binaries and dependencies for the BGP feature. After installation, the feature is not automatically active in NX-OS. The second step is to enable the feature within NX-OS CLI using:

feature bgp

This activates the control plane functionality and allows configuration of BGP on the switch.

Option A is incorrect because it attempts to enable the feature before installing it. Option C is invalid because feature bgp cannot be executed in Bash mode. Option D is incorrect because yum commands must be executed in the Bash shell, not in NX-OS configuration mode.

Thus, the correct workflow is install via Bash → enable via NX-OS CLI, which is exactly what option B describes.

The correct answer is C because it is the only option that satisfies all four requirements at the same time. Cisco UCS Manager documentation states that an All configuration backup is an XML file containing all system and logical configuration settings. Because it is XML, it is human-readable, which matches the operations team requirement. By contrast, a Full state backup is a binary snapshot, so it is not human-readable, and System configuration or Logical configuration alone do not include both sets of settings.

For the transport requirement, SCP is correct because Cisco UCS supports backup transfer over FTP, TFTP, SCP, or SFTP, and SCP runs over SSH/TCP, providing authenticated, secure file transfer before the actual data copy occurs. TFTP is not valid here because it uses UDP and does not provide secure identity verification. Although SFTP also uses SSH/TCP, option D fails because Full state is binary, and option A fails because System configuration does not include all logical settings. Therefore, the only fully correct combination is All configuration + SCP.

The correct answer is A. In Cisco UCS Manager, the Firmware Auto Sync Server Policy is used to keep the firmware on a server aligned with the firmware packages defined in its associated service profile or service profile template. When this policy is enabled, Cisco UCS Manager checks for firmware mismatches and can initiate the synchronization process so the server components move to the expected firmware levels. However, this behavior is still controlled and does not bypass operational safeguards. In normal Cisco UCS firmware workflows, administrator awareness and acknowledgment are required for disruptive actions, especially when activation or reboot may be necessary.

Option B is incorrect because firmware auto sync does not mean the UCS domain becomes active without the required firmware process. Option C is too absolute; a reboot depends on the component and upgrade type, and it is not the defining effect of the auto sync server policy itself. Option D is also incorrect because UCS Manager continues to provide status, faults, and reporting related to firmware operations.

So the key effect of the policy is automatic firmware synchronization, subject to administrative control and acknowledgment, which matches A.

The correct answer is D. file.

The NFSv4 (Network File System version 4) protocol is a file-level storage protocol, meaning it provides access to shared storage at the file system level rather than at the raw disk (block) level. In this model, clients interact with files and directories directly, using standard file operations such as open, read, write, and close. This aligns with the concept of NAS (Network Attached Storage), which NFS is a core part of in Cisco data center architectures.

Unlike block storage protocols such as iSCSI or Fibre Channel, which present storage as raw disk volumes that require a local file system to be created, NFS abstracts this complexity and allows multiple clients to access shared files concurrently. NFSv4 also introduces enhancements such as stateful operations, security improvements, and better locking mechanisms, making it suitable for enterprise environments.

Options A (block) and B (object) refer to different storage models, while C (inode) is an internal file system structure, not an access level. Therefore, NFSv4 operates at the file level, making D the correct answer.

The correct answer is A. NFS (Network File System).

NFS is a file-level storage protocol, which means it allows clients to access shared storage as if it were part of their local file system. This directly satisfies the requirement for “direct file-access level” mentioned in the question. Cisco documentation and data center architecture guidelines describe NFS as a simple and scalable solution that is widely used for shared storage environments, virtualization platforms, and large-scale data repositories.

NFS operates over standard IP networks, making it easy to deploy without requiring specialized storage networking hardware such as Fibre Channel fabrics. It also supports high-capacity storage systems, enabling centralized file sharing across multiple hosts efficiently.

In contrast, iSCSI, FCoE, and FCP are all block-level storage protocols. These technologies present storage to hosts as raw block devices (disks), requiring a file system to be created on top of them. They do not provide direct file-level access.

Because the question specifically asks for file-level access with simplicity and scalability, NFS is the correct and most appropriate choice.

The correct choices are A and D. In Cisco UCS, when the requirement is to aggregate links between the Fabric Interconnects and the I/O modules, the chassis discovery policy must use Link Grouping Preference = Port Channel. Cisco documents that for UCS 2200 I/O modules, selecting Port Channel causes the IOM-connected server ports to be automatically added to a port channel, which is exactly what provides link aggregation across the four 10-GbE connections per I/O module.

The second required step is D, because Cisco also states that after changing the link grouping preference, the chassis must be reacknowledged so the links are rediscovered and formed into the fabric port channel. Cisco’s UCS Manager infrastructure policy documentation explicitly notes that links can be added or removed by changing the link group preference and reacknowledging the chassis.

Options B and C do not create FI-to-IOM aggregation, and E is unrelated because unified ports are FI ports for Ethernet/FCoE or Fibre Channel flexibility, not a chassis-side requirement for this aggregation task.