From a supported IOS XE generation, the team wants a Docker-style app to run on the Catalyst through IOx. What is the 5.5 idea?
Select an answer to reveal the explanation.
Short Explanation
The point is the app lives on the box via IOx—like a shop in the station, not a new STP knob. Image-build craft stays in Domain 4; hosting is 5.5.
Full Explanation
From a supported IOS XE generation, the 5.5 idea for a municipal Docker-style app is to host the container on the Catalyst through IOx—not to reinvent hosting as a switching feature. Official guidance allows Docker apps to be hosted as-is under IOx on supported platforms so edge monitoring and automation tools live on the civic device itself rather than only off-box.
Configuring spanning tree so Layer-2 features become the application host fails: STP is not IOx hosting and cannot substitute for CAF. Building the image only on a laptop under Domain 4 and never deploying on-box fails the task’s on-device emphasis; image craft remains Domain 4 while hosting is 5.5. Replacing IOx with a mandatory Puppet agent inside the Docker image fails both the hosting framework and this bank’s treatment of Puppet as a leftover distractor.
Exam caveat: supported IOS XE/IOx generations and storage/networking prerequisites still apply; “Docker-style on-box” does not waive IOx enablement, AppGigabitEthernet or management mapping, or flash versus SSD constraints for additional apps.
Operational check: take a supported container image for a city edge monitor, activate it under IOx on a lab Catalyst 9000, and verify it runs on-box rather than only in a laptop Docker Desktop session or as a spanning-tree “feature.”