350-601 Exam Dumps - Implementing Cisco Data Center Core Technologies v1.1 (350-601 DCCOR)

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 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.

Cisco APIC accepts a properly structured JSON authentication payload containing an aaaUser managed object and an attributes object. The username and password must be represented as valid quoted JSON name-value pairs. Option C follows valid JSON syntax and supplies both required authentication attributes. Option A resembles a JavaScript object literal but is not valid JSON because its property names and string values are not enclosed in quotation marks. Options B and D attempt to use XML, but their element and attribute structures do not match the required APIC XML authentication format. The JSON payload is sent through an HTTP POST request to the APIC login URI. If authentication succeeds, APIC returns an aaaLogin response containing a token. That token is then presented with subsequent API requests to maintain the authenticated management session.

Option D statically associates User2’s MAC address B with Ethernet1/2 and User1’s MAC address A with Ethernet1/1 on VTEP1. Static secure MAC-address entries remain in the running and saved configuration, allowing them to persist after an interface or device restart. On VTEP2, configuring the port-security aging time as zero on Ethernet1/3 prevents the secure MAC address of the web server from aging out. Option A configures sticky learning only on Ethernet1/2 and does not preserve User1’s specific MAC address or disable aging for the server. Option B uses inactivity aging, which can still remove the server’s MAC address, and does not correctly identify both user MAC addresses. Option C enables basic port security without creating persistent MAC bindings and disables port security on the web-server interface.