Courseiva
Storage Management →hardMultiple Select

LFCS Storage Management Practice Question

A Linux administrator is configuring a new iSCSI storage target. The server has two network interfaces, eth0 and eth1, and the administrator wants to use multipath I/O (DM-Multipath) for redundancy and increased throughput. Which two steps are required to properly set up DM-Multipath for the iSCSI LUNs? (Choose two.)

⚠ Common exam trap

Many candidates confuse network bonding with multipath I/O; bonding aggregates links but does not create multiple SCSI paths, which are required for DM-Multipath to function.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Use iscsiadm to log in to the target portal on both eth0 and eth1, ensuring that each interface discovers the same LUNs.

To set up DM-Multipath for iSCSI LUNs, you must install and configure multipathd and its configuration file, and you must create multiple iSCSI sessions to the same LUNs via different network interfaces. This ensures that the multipath layer can detect and manage multiple paths. Bonding or authentication are not substitutes for multipath configuration.

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 a bonded network interface combining eth0 and eth1, and configure iSCSI to use the bond for all traffic.

    Why it's wrong here

    While bonding can provide redundancy at the network layer, it does not create multiple SCSI paths to the storage. DM-Multipath operates at the SCSI layer and requires distinct paths, typically from separate iSCSI sessions. Using a bond would present a single path to the storage, eliminating the multipath capability and reducing the benefits of DM-Multipath.

  • ✓

    Use iscsiadm to log in to the target portal on both eth0 and eth1, ensuring that each interface discovers the same LUNs.

    Why this is correct

    For DM-Multipath to provide redundancy and throughput, multiple paths to the same LUN must exist. Logging in via both network interfaces creates two separate iSCSI sessions, each seeing the same LUN, which the multipath layer can then combine. If only one interface is used, there is no multipath to manage, defeating the purpose of the configuration.

  • ✗

    Format the iSCSI LUNs with a cluster-aware filesystem such as GFS2 before enabling multipath.

    Why it's wrong here

    The filesystem type is independent of multipath configuration. DM-Multipath works at the block device layer and does not require a cluster filesystem unless the LUNs are shared among multiple nodes. For a single server, standard filesystems like ext4 or XFS are fine. Formatting before configuring multipath is also premature, as the multipath device may not yet be available.

  • ✗

    Set the iSCSI initiator name to match the target's ACL, and configure CHAP authentication for each path.

    Why it's wrong here

    While initiator naming and CHAP authentication are important for iSCSI security and access control, they are not specific steps for enabling DM-Multipath. They are part of general iSCSI setup. The question asks for steps required to set up DM-Multipath, which involve the multipath daemon and multiple sessions, not authentication details.

  • ✓

    Install and enable the multipathd service, then configure /etc/multipath.conf with the appropriate blacklist and multipath settings.

    Why this is correct

    DM-Multipath requires the multipathd daemon to be running to manage multipath devices. The /etc/multipath.conf file defines which devices to blacklist and how to group paths. Without configuring multipath.conf, the default settings may not correctly recognize the iSCSI LUNs, especially if they need specific path grouping or aliases. This step is essential for proper multipath setup.

About these practice questions

This LFCS question is part of Courseiva's 406-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Linux Foundation exam blueprint

This LFCS practice question is part of Courseiva's free Linux Foundation certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the LFCS exam.