A customer is considering deploying a significant number of HPE BladeSystem Gen10 servers with an HPE 3Par storage solution for a new cloud solution. You propose HPE OneView as the management…

Question

Options

• Apatch deployment for operating system and storage components
• Boperating system deployment through Image Streamer
• Cservers and storage firmware upgrades
• Dvolume presentation from the 3Par and automated zoning

• A
  4% (1)
• B
  8% (2)
• C
  12% (3)
• D
  76% (19)

Explanation

D is correct because HPE OneView has native integration with HPE 3Par storage, enabling automated volume presentation (making storage available to servers) and automated SAN zoning - eliminating manual, error-prone configuration steps that would otherwise be required at scale. This is the most compelling differentiator when a customer is deploying both BladeSystem servers and 3Par storage together.

Why the distractors are wrong:

• A (patch deployment for OS/storage): OneView handles firmware, not OS-level patching - that's the role of tools like SCCM, Ansible, or HPE iLO Amplifier Pack.
• B (OS deployment via Image Streamer): Image Streamer is a valid OneView feature, but it requires a specific HPE Synergy platform - not BladeSystem Gen10, which is what the question specifies.
• C (servers and storage firmware upgrades): OneView can manage server firmware, but 3Par storage firmware is managed through its own tools (SSMC/StoreServ Management Console), not OneView. This answer overstates OneView's scope.

Memory tip: Think "OneView = One throat to choke for servers and storage together." The integration story - automated zoning + volume presentation - is the headline feature when both BladeSystem and 3Par are in play. If the question mentions both products, the answer is almost always about their integration, not individual management tasks.

No community discussion yet for this question.