Emergency-management change windows must configure RoCE priorities on Spectrum-X safely. What should run?
Select an answer to reveal the explanation.
Short Explanation
Terraform VLAN plans and BGP EVPN playbooks won't tune what you need here. Use Ansible playbooks built to automate those RoCE priority settings, so you keep the emergency-management change window repeatable and reversible.
Full Explanation
Emergency-management change windows that configure RoCE priorities on Spectrum-X require controlled automation with a repeatable path. Ansible playbooks that automate RoCE-related Spectrum priority settings apply those changes consistently, support review before the window, and provide a documented procedure that can be reversed or re-run if the municipal emergency fabric needs rollback. Terraform plans that provision Spectrum-X management VLAN assignments address VLAN plumbing rather than RoCE priority values, so they cannot safely configure lossless RoCE behavior during the window. Ansible playbooks that push BGP EVPN fabric configs on Spectrum switches target fabric routing instead of RoCE priority and PFC settings, so they do not meet the requirement to configure RoCE priorities safely. NetQ cloud jobs that archive Spectrum-X RoCE congestion telemetry snapshots only collect observability data and do not apply or change RoCE priority settings. Exam caveat: even automated RoCE priority changes need a tested rollback playbook and a data-plane validation step; green Ansible output alone does not prove lossless behavior under load. Operational check: peer-review the Ansible RoCE priority playbooks, run them in the emergency-management window against Spectrum-X, verify priority/PFC mappings, execute a RoCE smoke test, and keep the rollback playbook ready.