300-615 · Question #53
Refer to the exhibit. Partial configuration from N9K-1 and N9K-2 is included. The client has two WANs connected. WAN-1 is for normal business-day activities. WAN-2 is for server backups during…
The correct answer is D. The applet called "Backup" must include an action to remove the current static route. Option D is correct because the "Backup" EEM applet adds a static route for WAN-2 at 1:00 a.m., but the existing static route via WAN-1 remains in the routing table. Since both routes coexist (likely with equal administrative distance), traffic continues to prefer WAN-1 rather…
Question
Refer to the exhibit. Partial configuration from N9K-1 and N9K-2 is included. The client has two WANs connected. WAN-1 is for normal business-day activities. WAN-2 is for server backups during nonworking hours of 1:00 a.m. to 5:00 a.m. daily. The client says that at the scheduled time for backup, the data center server failed to use the WAN-2 link to back up the servers to the cloud backup system. What is the solution to this problem?
Exhibits
Options
- AThe event timer must be written in epoch time format.
- BThe Cisco Nexus switch must be configured with one applet because a configuration with two
- CThe Cron entry must be configured without double quotes.
- DThe applet called "Backup" must include an action to remove the current static route.
How the community answered
(33 responses)- A9% (3)
- B3% (1)
- C3% (1)
- D85% (28)
Explanation
Option D is correct because the "Backup" EEM applet adds a static route for WAN-2 at 1:00 a.m., but the existing static route via WAN-1 remains in the routing table. Since both routes coexist (likely with equal administrative distance), traffic continues to prefer WAN-1 rather than shifting to WAN-2. The applet must first remove the WAN-1 static route before (or alongside) adding the WAN-2 route to force traffic onto the correct link.
Why the distractors fail:
- A is wrong because EEM cron entries use standard Unix cron format (five-field: minute, hour, day, month, weekday), not epoch time.
- B is wrong because NX-OS EEM fully supports multiple applets - one to activate WAN-2 at 1:00 a.m. and another to restore WAN-1 at 5:00 a.m. is a valid and common design.
- C is wrong because NX-OS EEM requires double quotes around the cron expression (e.g.,
cron-entry "0 1 * * *"); removing them causes a syntax error.
Memory tip: Think swap, not add - switching WAN paths with static routes requires a two-step action: remove the old route, then install the new one. If you only add, the original route wins and nothing changes.
Community Discussion
No community discussion yet for this question.