Pass the Cisco CCNP Data Center 350-601 Questions and answers with CertsForce

An EPLD upgrade reprograms hardware logic on the selected module. The affected module must be taken out of service or reloaded while its programmable components are updated. Consequently, traffic traversing module 2 is disrupted during the operation. Other modules that are not included in the upgrade can continue forwarding traffic, subject to the platform design and availability of alternate paths. The upgrade is therefore not completely nondisruptive, but its impact is localized to the module being upgraded rather than automatically affecting every module. It is also not limited to supervisor control-plane traffic because an I/O module’s forwarding hardware is directly affected by EPLD reprogramming. Administrators should move traffic to redundant links and schedule the operation during a maintenance window before initiating the upgrade on a production Nexus switch.

Cisco UCS Manager CLI commands must follow the correct managed-object hierarchy. The engineer first enters the required fabric context with scope fabric a and creates the Fibre Channel monitoring session named FCMonitor. After creating the session, the engineer enters its Fibre Channel traffic-monitoring scope, creates the destination interface using slot 1 and port 10, and sets its administrative speed to 8 Gbps. The commit-buffer command applies the staged configuration. Option A attempts to enter the traffic-monitoring scope before establishing the appropriate fabric and session contexts. Option B never selects a fabric or creates the monitoring session. Option C issues destination-interface commands before entering the required configuration hierarchy. Therefore, only option D creates the session and destination interface in the proper UCS Manager CLI context and commits the completed configuration.

The scheduler job shown in the exhibit attempts to copy the configuration to the TFTP server through the management VRF. However, the question states that the TFTP server is reachable through the global routing table. On Cisco NX-OS, routes in the management VRF are isolated from routes in the default VRF. Consequently, specifying vrf management prevents the copy operation from following the global routing table. The job must use the default VRF, which can be achieved by removing the management-VRF specification or explicitly selecting the appropriate default routing context. The scheduler already contains a defined job and execution time, so defining the schedule again does not solve the reachability problem. Authentication is not the issue identified in the scenario, and scheduler log-file sizing has no bearing on the route used to contact the TFTP server.