Which statement about logical JBODs configured using HPE OneView and D3940 Storage Modules is true?

Question

Options

• AA logical JBOD cannot be created during server profile creation and must be prepared in
• BA logical JBOD lifecycle can be associated with a server profile lifecycle and drives can be
• CDifferent types of the drives can be used within & logical JBOD as long as they have the same
• DLogical JBOD functionality must be enabled on the Enclosure Group level by a storage

• A
  8% (3)
• B
  75% (27)
• C
  14% (5)
• D
  3% (1)

Explanation

Option B is correct because HPE OneView allows a logical JBOD's lifecycle to be explicitly tied to a server profile's lifecycle - meaning when the server profile is deleted, the logical JBOD (and its drives) can be configured to be automatically deleted as well, or set to persist independently. This tight integration between storage and compute lifecycle management is a core feature of OneView's composable infrastructure model.

Why the distractors are wrong:

• A is incorrect because logical JBODs can be created directly during server profile creation - they don't require separate pre-configuration.
• C is incorrect because all drives within a single logical JBOD must be of the same type (e.g., all SAS or all SSD); mixing drive types is not permitted regardless of capacity matching.
• D is incorrect because logical JBOD functionality is not enabled at the Enclosure Group level - it is managed through server profile templates and the logical enclosure configuration.

Memory tip: Think of "B for Bound" - the logical JBOD lifecycle can be bound to the server profile lifecycle. If the profile goes away, the JBOD can go with it. This mirrors how OneView treats compute and storage as a unified, composable resource rather than separate silos.

No community discussion yet for this question.