Official DEVCOR 5.5 names which switch family as a platform that can host applications on the device (alongside other IOx-enabled devices)?
Select an answer to reveal the explanation.
Short Explanation
Catalyst 9000 is the named mailbox on the blueprint for hosting apps—alongside other IOx-enabled devices. STP/VTP design is not the 5.5 answer.
Full Explanation
Official DEVCOR 5.5 materials name Catalyst 9000 as a platform class that can host applications on the device alongside other IOx-enabled devices. When a question asks which switch family is named for on-device hosting in this objective, Catalyst 9000 is the expected answer for municipal edge designs that want apps local to the access or distribution layer rather than only centralized in the data center.
Selecting only a random ISR story with no Catalyst 9000 option as the named host misses the switch-family naming the objective highlights for candidates. Selecting only NX-OS data-center switches as the sole correct 5.5 platform ignores the Catalyst 9000 call-out in the blueprint context. Claiming any switch works once VTP and STP are tuned, regardless of IOx support, invents a non-requirement and skips the hosting framework entirely.
Exam caveat: other IOx platforms exist in the Cisco portfolio; exam items often still want the Catalyst 9000 name. STP and VTP settings are unrelated to whether IOx application hosting is available on the box.
Operational check: verify the municipal switch bill of materials includes IOx-capable Catalyst 9000 models before promising on-box apps in an architecture review or RFP response.