Free Cisco 350-601 Practice Exam with Questions & Answers | Set: 11

The correct answer is C: time start daily 3:00 because of how the Cisco NX-OS scheduler syntax is structured. In NX-OS, when defining a scheduler schedule, the correct format to execute a job at a recurring time includes the keyword start, which specifies when the job should begin execution. Cisco documentation for NX-OS scheduler clearly defines that recurring jobs must be configured using the format:

scheduler schedule name < name >

job name < job-name >

time start daily < hh:mm >

The keyword start is mandatory when defining periodic execution. Without it, the command is syntactically incomplete or invalid in NX-OS.

Option A (time daily 3:00) is incorrect because it omits the required start keyword. Options B and D specify weekly execution, not daily, and therefore do not meet the requirement of running the job every day.

Thus, time start daily 3:00 ensures that the backup job runs automatically every day at 3:00 a.m., aligning exactly with the requirement in the question and Cisco NX-OS scheduler configuration standards.

The correct answer is D. A modular Cisco Nexus 9000 Series switch is designed with redundant supervisor capabilities, which allows the platform to perform an In-Service Software Upgrade (ISSU) with minimal or no traffic disruption when the hardware, software release, and features all meet ISSU compatibility requirements. The modular architecture supports stateful control-plane switchover and coordinated module upgrade behavior, which is the key difference from a typical nonmodular or fixed-form-factor switch.

This is why option D is correct: the modular platform can maintain forwarding while the supervisors transition during the upgrade process. By contrast, option A is backwards, because modular chassis are the platforms most associated with nondisruptive upgrade capability. Option B

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 D. From the exhibit, N5K-1 has interface Vlan100 in VRF WEB with IP 10.1.1.1/24 for Server 1’s gateway, and interface Vlan150 in VRF WEB with IP 192.168.1.1/30 toward N5K-2. On N5K-2, interface Vlan200 has IP 172.16.1.1/24 for Server 2’s gateway, and interface Vlan150 has IP 192.168.1.2/30 as the routed transit link back to N5K-1. The exhibit also shows that N5K-2 already has a static route pointing to Server 1’s host/subnet via 192.168.1.1, but N5K-1 only has a route for 172.16.1.0 that is not placed in VRF WEB. Because Server 1’s SVI belongs to VRF WEB, N5K-1 needs a route inside that same VRF toward Server 2’s subnet through 192.168.1.2. Without that VRF-specific route, traffic sourced from Server 1 cannot be forwarded correctly to Server 2. The other options do not solve the Layer 3 reachability problem between the two VRF-connected subnets.

Po12

Vlan

Vfc1

Po12