A building permits desk standardizes access switches from templates but suspects engineers applied one-off CLI. How should automation detect that drift?
Select an answer to reveal the explanation.
Short Explanation
Drift is like a stamped permit plan versus what got built on site—you have to measure the walls. Pull state through APIs and diff it to the template. Trusting vibes or burning configs every night does not find the unauthorized VLAN.
Full Explanation
Programmatic retrieval of configuration and relevant operational state enables comparison against the intended template or controller intent, surfacing CLI drift. GUI health alone does not prove configuration compliance. Ticket review without device reads misses unauthorized changes. Nightly erase is destructive and unrelated to controlled drift detection.