A logistics company needs an on-box tool to reach an archive server through an address and route that must not be installed in the Nexus default routing table. Which environment can hold that address in its own network namespace?
Select an answer to reveal the explanation.
Short Explanation
Give the tool its own driveway instead of painting a new arrow on the main road. You put the archive address in the guest shell network namespace so the default routing table stays untouched. A static route in the default VRF would change forwarding for the switch itself.
Full Explanation
Guest shell is an isolated Linux environment on NX-OS with its own network namespace. An address and route placed there are used by tools inside the guest shell and are not installed as routes in the switch default routing table, which is what the logistics team needs for the archive server. A static route in the default VRF is a switch forwarding entry. It is not local to one tool, and adding it would change how the Nexus itself routes, which violates the request. POAP is a day-0 process that runs when startup configuration is absent. It does not create a standing network namespace for production tools, and a separate namespace is not limited to first boot. An EEM applet matches an event and runs actions such as CLI commands. Those actions use the switch, not a private routing table and address of their own. Caveat: guest shell still needs a real path out of the switch, often tied to a VRF and an uplink, so the namespace is separate without being unreachable. Operational check: configure the guest shell address, confirm the default routing table has no archive route, and copy a file from inside the guest shell.