Why will a server in an environment using persistent binding maintain a constant view of its target IDs when rebooted?

Question

Options

• ABecause persistent binding retains the target ID information.
• BBecause the LU Management Service will manage the target IDs.
• CBecause the driver software remaps the SCSI target ID to the new WWNNs automatically.
• DBecause persistent binding will connect to the LU Manager and provide the target IDs.

• A
  87% (27)
• B
  6% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

Persistent binding stores a static mapping between a storage target's World Wide Name (WWN) and its assigned SCSI target ID directly in the HBA driver configuration. When the server reboots, the driver reads this saved mapping and reassigns the same target ID to the same WWN - so the server always "sees" each target at the same ID, regardless of discovery order.

Why the distractors are wrong:

• B is wrong because no such "LU Management Service" exists in this role - target ID persistence is handled by the HBA driver configuration, not a management service.
• C is wrong because it describes the problem, not the solution - without persistent binding, drivers might remap targets to different IDs on reboot; persistent binding prevents this remapping from changing.
• D is wrong for the same reason as B - persistent binding doesn't communicate with any external "LU Manager"; the binding information is stored and applied locally by the driver.

Memory tip: Focus on the word persistent - it means the binding (WWN ↔ target ID mapping) persists through reboots. The server doesn't rediscover and randomly assign; it remembers. "Persistent = permanent memory of who gets which ID."

No community discussion yet for this question.