...
| Use case | Match mode | Rationale |
|---|---|---|
| Baseline configuration - NTP, AAA, logging... | Loose | Requirements are independent lines scattered across the config, only presence matters |
| Security hardening - telnet disabled, no SNMPv2, management ACLs... | Loose | Independent requirements with no meaningful ordering relative to each other |
| Firewall and ACL rules | Sequential | Rule ordering matters, such as when specific rules must precede broader rules. |
| Route-maps | Sequential | Match and set clauses must appear in a required sequence. |
| Multiline MOTD banner | Strict | The complete banner block must be present and uninterrupted |
| Interface config blocks | StrictInterface | definition, port-security, BPDU guard, and 802.1X settings must form a complete, consecutive blockValidate that a required set of interface configuration commands appears together as a consecutive block. |