Your customer added HPE Primera to HPE OneVlew and enabled volume provisioning on all storage pools. For security reasons, the customer wants to disable volume provisioning using HPE OneView on a…

Question

Options

• AThe storage pool should be removed from HPE OneView using a PowerShell script.
• BThe storage pool should be disabled using the array management tool.
• CThe storage pool state should be changed to discovered using HPE OneView.
• DThe storage pool should be marked as read-only using HPE OneView.

• A
  17% (5)
• B
  70% (21)
• C
  7% (2)
• D
  7% (2)

Explanation

Option B is correct because disabling the storage pool directly through the array's native management tool (such as HPE SSMC for Primera) restricts provisioning at the hardware/array level, which is the appropriate security-grade control. This change is then reflected in HPE OneView, effectively preventing OneView from provisioning volumes on that specific pool without disrupting the overall integration.

Option A is wrong because removing the storage pool from HPE OneView entirely is a destructive, over-broad action - and using a PowerShell script is an unnecessary workaround, not the proper method for selectively disabling provisioning.

Option C is wrong because "discovered" is a read-only awareness state that OneView assigns automatically upon detection; you cannot manually flip a managed pool back to discovered to block provisioning - that state change is not a supported security control within OneView.

Option D is wrong because HPE OneView does not offer a "mark as read-only" option for storage pools as a provisioning control mechanism; this option conflates file-system concepts with SAN storage management.

Memory tip: Think of it as "security lives at the source" - when you need to restrict something for security on a specific resource, go to the authoritative system (the array itself), not the management overlay (OneView). OneView manages; the array enforces.

No community discussion yet for this question.