A factory IoT team wants to install extra Python libraries on a Nexus switch without placing those packages in the NX-OS system root. Which environment is the supported place for that install?
Select an answer to reveal the explanation.
Short Explanation
You want a workshop in the garage, not a pile of parts in the living room. The guest shell is that separate Linux space, with its own packages, so the extra Python libraries stay out of the NX-OS system root. Native bash is not that sandbox.
Full Explanation
Guest shell on NX-OS is an isolated Linux environment, with its own file system and network namespace, intended for on-box tools and Python packages. Installing libraries there keeps them out of the NX-OS system root, which is what the factory asked for. The native bash shell reached with the bash feature runs in the switch's own environment. It is useful for scripts and file work, and it is not a separate package sandbox for pip libraries. POAP is a boot-time provisioning process used when a switch has no startup configuration. It can download an initial script, and it is not the ongoing place where operators add Python libraries, nor are those libraries limited to first boot. An EEM applet matches an event and runs actions such as CLI commands. It does not present a Linux package manager or a persistent guest file system for third-party libraries. Caveat: guest shell has to be enabled and given network reachability if the libraries come from an internal repository, and not every platform image includes it. Operational check: enable the guest shell, install the library inside it, and confirm the NX-OS system directories did not pick up that package.