HPE2-T37 · Question #64
Which statement best describes Ansible integration with HPE OneView?
The correct answer is C. It allows provisioning physical infrastructure in minutes with a widely used cloud infrastructure. Ansible integration with HPE OneView delivers infrastructure-as-code capabilities by exposing HPE OneView's REST API through Ansible modules, letting teams define and provision physical infrastructure (servers, storage, networking) declaratively in minutes - exactly what option…
Question
Which statement best describes Ansible integration with HPE OneView?
Options
- AIt enables health monitoring of third party storage systems that normally are not supported in HPE
- BIt enables support for additional servers and HPE Synergy frames if appropriate license is
- CIt allows provisioning physical infrastructure in minutes with a widely used cloud infrastructure
- DIt allows the deployment of HPE Synergy infrastructure through a set of PowerShell scripts using
How the community answered
(45 responses)- A2% (1)
- B7% (3)
- C89% (40)
- D2% (1)
Explanation
Ansible integration with HPE OneView delivers infrastructure-as-code capabilities by exposing HPE OneView's REST API through Ansible modules, letting teams define and provision physical infrastructure (servers, storage, networking) declaratively in minutes - exactly what option C describes. Ansible is one of the most widely adopted infrastructure automation tools, making "widely used cloud infrastructure automation" the defining phrase here.
Why the distractors are wrong:
- A is wrong because the integration is not designed to extend health monitoring to unsupported third-party storage - that's an HPE OneView scope/compatibility concern, not an Ansible function.
- B is wrong because adding support for additional servers or Synergy frames is governed by HPE licensing terms, not by Ansible integration.
- D is wrong because it describes PowerShell scripts - that would apply to the HPE OneView PowerShell library, a separate tool entirely. Ansible uses YAML-based playbooks, not PowerShell.
Memory tip: Remember "Ansible = Automation in minutes with YAML" - if you see PowerShell in an Ansible answer choice, eliminate it immediately, since those are two distinct automation ecosystems.
Topics
Community Discussion
No community discussion yet for this question.