EX200 Manage users and groups Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Create bond interface config, then configure slave interfaces, then restart network

  Why this is correct

  Create the bond interface configuration first, e.g. /etc/sysconfig/network-scripts/ifcfg-bond0 with BONDING_OPTS='mode=1 miimon=100', then define slave interfaces such as ifcfg-eth0 and ifcfg-eth1 with MASTER=bond0 and SLAVE=yes. With this order, initscripts/NetworkManager can create bond0 and bind the slaves during a single network restart. Restarting only after both steps are complete ensures the kernel bonding driver has a usable master before the slave devices try to join it.

• ✗

  Configure slave interfaces, then create bond interface config, then restart network

  Why it's wrong here

  Configuring slave interfaces before the bond interface exists is backwards: ifcfg-eth0 can specify MASTER=bond0, but if ifcfg-bond0 is absent at boot, the bonding driver has no bond0 device to attach to, so the slaves are left unenslaved or the network script fails. Even if a later restart creates bond0, the system will not automatically reattach already-configured slaves unless the scripts process them in the correct dependency order. This sequence therefore produces a bond with zero active interfaces at the moment it is needed.

• ✗

  Restart network, then create bond interface config, then configure slave interfaces

  Why it's wrong here

  Restarting the network before any bond or slave configuration has been written simply reloads the old, unmodified configuration, so the bond never comes up in that restart. After creating the bond and slave files, you would need yet another restart to apply the changes, making the third step in this sequence useless and the network needlessly interrupted. The bond configuration would not be active until a subsequent restart, which contradicts the intended one-cycle setup.

• ✗

  Create bond interface config, then restart network, then configure slave interfaces

  Why it's wrong here

  Creating the bond config and then immediately restarting brings up an empty bond0 with no slaves, because no ifcfg-eth0/eth1 entries with MASTER=bond0 exist yet. Once the slave files are added later, simply running ifup on them may not attach them to the already-running bond, as the master is already up and the initscripts expect the bond to be configured before slaves load. You would then have to restart the network a second time, so this option defeats the goal of a clean two-step configuration.

Go deeper

Related to this question