A customer is expanding their blade based infrastructure managed by HPE OneView with an HPE Synergy platform. The customer is familiar with HPE OneView and wants to know if the same management…

Question

Options

• AHPE Synergy can be managed using the same HPE OneView instance that is used to manage
• BHPE Synergy can be managed using HPE OneView as long as a separate, dedicated HPE
• CHPE Synergy can be managed by HPE Composer, which is running an embedded version of the
• DHPE Synergy must be managed with HPE Systems Insight Manager

• A
  5% (2)
• B
  93% (37)
• D
  3% (1)

Explanation

Option B is correct because HPE Synergy requires its own separate, dedicated HPE OneView appliance (called HPE Composer) - you cannot simply add Synergy frames to an existing OneView instance managing traditional BladeSystem infrastructure. The good news for the customer is that since Composer is built on OneView, their existing OneView knowledge and management procedures transfer directly.

Why the distractors are wrong:

• A is wrong because Synergy cannot share the same existing OneView instance with other managed environments - a dedicated instance is mandatory, even though the procedures are the same.
• C is misleading: while it's technically true that HPE Composer runs an embedded version of OneView, framing it as a separate product called "Composer" obscures the key point the customer needs - that their OneView skills still apply.
• D is wrong because HPE Systems Insight Manager (SIM) is a legacy monitoring tool and has no role in managing HPE Synergy composable infrastructure.

Memory tip: Think of HPE Composer as "OneView in a dedicated box just for Synergy." Same software, same skills - just its own dedicated home. The rule is: one Synergy environment = one dedicated OneView/Composer instance.

No community discussion yet for this question.