What are two effects of persistent binding? (Choose two.)

Question

Options

• APersistent binding can speed up path failover.
• BPersistent binding guarantees Command Device security.
• CPersistent binding can speed up the server boot process.
• DPersistent binding guarantees that target assignments are preserved between reboots.

Explanation

C and D are correct.

Persistent binding is a storage networking feature (common in Fibre Channel SANs) that locks an HBA port to a specific target WWPN, creating a fixed mapping between the host and storage target.

Why C is correct: During boot, an HBA normally performs a fabric login and dynamically discovers available targets, which adds time. Persistent binding pre-defines those target assignments, so discovery is skipped or accelerated - reducing overall boot time.

Why D is correct: This is the core purpose of persistent binding. Without it, device names (e.g., /dev/sda) can change between reboots as target discovery order varies. Persistent binding ensures the same target always maps to the same device identifier, providing consistency critical for database and OS volumes.

Why A is wrong: Path failover speed is governed by multipath I/O (MPIO) software, not persistent binding. In fact, rigid persistent bindings can complicate failover.

Why B is wrong: "Command Device" is a storage array management concept (used in EMC/Hitachi environments) completely unrelated to persistent binding, which only controls HBA-to-target mapping.

Memory tip: Focus on the word "persistent" - it means things stay the same. Persistent binding keeps target assignments the same across reboots (D), and since the system already knows where to connect, it boots faster (C). Everything else (failover speed, security) is handled by other technologies.

No community discussion yet for this question.