In the assigned mapping of the MX5016s storage sled what is an assignment option used for independent storage to be mapped to a compute sled?

Question

Options

• ADrive-assigned enables the MX5016s to be split among multiple compute sleds. Each compute
• BDrive-assigned enables the MXG610s to the first eight drives in the MX5016s.
• CEnclosure-assigned enables the MX5016 to be split among multiple compute sleds. Each
• DEnclosure-assigned enables the MXG610s to the first eight drives in the MX5016s.

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

Explanation

Drive-assigned is the correct assignment option because it allows individual drives within the MX5016s storage sled to be independently mapped to specific compute sleds, effectively splitting the sled's storage capacity across multiple compute sleds simultaneously - exactly what's needed for independent storage assignment.

Option B is wrong because it incorrectly introduces the MXG610s (a GPU sled) into a storage assignment scenario where only the MX5016s is relevant. Option C is a common trap - enclosure-assigned actually maps the entire enclosure as a single unit to one host, so it cannot be split among multiple compute sleds. Option D combines both errors: it uses enclosure-assigned (wrong mode) and references the MXG610s (wrong sled).

Memory tip: Think "Drive = Divide" - Drive-assigned lets you divide drives among sleds, while Enclosure-assigned keeps the whole box together as one.

No community discussion yet for this question.