ifconfig command

ifconfig command

• A. Ping
• B. Ifconfig
• C. Traceroute
• D. Nslookup

Answer: (B)

The main idea here is configuring and inspecting network interfaces on a Unix-like system. The ifconfig command is the classic tool for that task: it lets you view current interface settings (such as IP address, netmask, and broadcast), and it also lets you bring interfaces up or down or assign new addresses and related parameters. This is exactly what you use when you’re deciding how a device should connect to a network and ensuring it has the right addressing. For example, you can run ifconfig to see what’s assigned to each interface, or set things like: ifconfig eth0 192.168.1.100 netmask 255.255.255.0 up to assign an IP and activate the interface. Note that on many modern Linux systems the preferred tool is the ip command, but the idea remains the same: you’re configuring the network interface itself, not just checking connectivity. The other options test reachability (ping), show the path to a destination (traceroute), or perform DNS lookups (nslookup), which is why they aren’t the right fit for configuring interfaces.

The main idea here is configuring and inspecting network interfaces on a Unix-like system. The ifconfig command is the classic tool for that task: it lets you view current interface settings (such as IP address, netmask, and broadcast), and it also lets you bring interfaces up or down or assign new addresses and related parameters. This is exactly what you use when you’re deciding how a device should connect to a network and ensuring it has the right addressing.

For example, you can run ifconfig to see what’s assigned to each interface, or set things like: ifconfig eth0 192.168.1.100 netmask 255.255.255.0 up to assign an IP and activate the interface. Note that on many modern Linux systems the preferred tool is the ip command, but the idea remains the same: you’re configuring the network interface itself, not just checking connectivity. The other options test reachability (ping), show the path to a destination (traceroute), or perform DNS lookups (nslookup), which is why they aren’t the right fit for configuring interfaces.