What interface is traditionally used for configuring network services both locally and remotely?

The command-line interface (CLI) is traditionally used for configuring network services both locally and remotely due to its efficiency and powerful capabilities. CLI provides direct access to system commands and configurations, allowing for granular control over network devices and services. Network administrators can execute scripts, manage configurations, and automate tasks more easily through the CLI compared to graphical user interfaces.

The CLI is particularly favorable in environments where speed and remote access are critical since it requires significantly less bandwidth than graphical interfaces and can be accessed via simple terminal emulators over protocols like SSH. This makes it a preferred choice for configuring network services in various scenarios, from on-site management to remote support.

Other interfaces, such as a graphical user interface (GUI), while user-friendly, may not offer the same level of control or efficiency, especially for advanced configurations. REST interfaces are generally used for web-based management of services and APIs rather than direct device configuration. SNMP (Simple Network Management Protocol) serves more for monitoring and management purposes rather than explicit configuration tasks. Thus, the CLI stands as the most versatile and widely adopted method for network configuration tasks.