After a bad ACL, the county cannot snapshot or roll back the physical VLAN fabric the way it rolls back a VM. Which virtual-networking property addresses that missing software lifecycle?
Select an answer to reveal the explanation.
Short Explanation
A physical ACL fabric is wet concrete—once it sets wrong, the county chips it out by hand. Virtual segments and gateways are more like documents: revise or recreate them instead of living with a frozen switch config. Printouts and Carbon Black alerts are not a rollback.
Full Explanation
Physical VLAN and ACL state is distributed across devices and is not treated as a first-class software object with an easy civic rollback. NSX-T segments, gateways, and security objects are configuration items that can be revised or recreated through the manager without rebuilding the underlay. Printed ToR configs, Carbon Black alert history, and NSX-V DLR/ESG hardware-centric designs do not provide that software lifecycle.