What is true about NetworkManager on a Linux system that uses its distribution's mechanisms to configure network interfaces? (Choose two.)

Question

Options

• ANetworkManager reconfigures all network interfaces to use DHCP unless they are specifically
• BNetworkManager must be explicitly enabled for each interface it should manage.
• CNetworkManager by default does not change interfaces which are already configured.
• DNetworkManager disables all interfaces which were not configured by NetworkManager.
• ENetworkManager can be configured to use the distribution's network interface configuration.

• A
  13% (7)
• B
  77% (40)
• D
  4% (2)
• E
  6% (3)

Explanation

Options B and C are correct because they accurately describe how NetworkManager coexists with a distribution's native network configuration tools (such as Red Hat's ifcfg files or Debian's /etc/network/interfaces).

B is correct: In this context, NetworkManager does not automatically assume control of every interface. Interfaces managed by the distro's own tooling are typically left alone unless explicitly handed over - for example, via NM_CONTROLLED=yes in an ifcfg file on RHEL/CentOS systems. Management must be opted into per interface.

C is correct: NetworkManager's default behavior is non-disruptive. If an interface is already configured (by the distro's init scripts, systemd-networkd, etc.), NetworkManager leaves it in its current state rather than overwriting it.

Why the distractors fail:

• A is wrong - NetworkManager does not force DHCP on all interfaces; it respects existing static configurations.
• D is wrong - NetworkManager does not disable foreign-configured interfaces; it simply ignores them.
• E is a common trap: while NM does have plugins (e.g., ifcfg-rh, ifupdown) that can read distro config files, this is not default out-of-the-box behavior - it requires deliberate configuration, making E misleading in an unqualified context.

Memory tip: Think of NetworkManager as a new roommate who won't rearrange your furniture unless you hand them the keys to each room - it's opt-in per interface, and it won't touch what was there before it arrived.

No community discussion yet for this question.