A school-district lab still manages Spectrum-X with ad-hoc CLI. What modernization step should instructors teach?
Select an answer to reveal the explanation.
Short Explanation
Ad-hoc Spectrum CLI is a lab anti-pattern. Teach students to convert those one-off commands into reusable NVUE templates so Spectrum-X management finally scales.
Full Explanation
A school-district lab still managed with ad-hoc Spectrum-X CLI needs a modernization path instructors can teach repeatably. Converting ad-hoc Spectrum CLI into reusable NVUE templates captures proven commands as structured, reviewable configuration so students learn civic-grade Spectrum-X management instead of one-off console habits. That shift is the Domain 6 direction for municipal Ethernet Spectrum automation. Replicating Spectrum CLI in hand-maintained Ansible playbooks just wraps imperative commands in automation without creating structured, reviewable NVUE templates, so it still drifts and doesn't teach reusable configuration. Archiving Spectrum CLI outputs as NetQ event logs only records what happened; it doesn't convert ad-hoc commands into reusable templates or change how switches are managed. Tracking Spectrum CLI edits in shared spreadsheets is manual bookkeeping, not automation, and it blocks idempotent apply and structured review the way NVUE templates do. Exam caveat: conversion should preserve intent (interfaces, EVPN, RoCE/QoS) and be tested; a literal paste of interactive history into a template without cleanup can encode transient or unsafe commands. Operational check: capture a known-good school-district Spectrum CLI session, refactor it into NVUE templates, apply in the lab, and compare resulting switch state to the original working configuration.