Your customer accidentally disabled ILO functionality during a proof of concept During your next customer visit, which tool should be used to activate it?

Question

Options

• AUETI System Utilities
• BHPE InfoSight
• CiLO Web interface
• DHPEOneView

• A
  89% (31)
• B
  6% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

UEFI System Utilities (note: "UETI" in option A appears to be a typo for "UEFI") is correct because it is a local, boot-time configuration tool accessible directly on the physical server - no iLO connectivity required. Since iLO has been disabled, it cannot be reached remotely, making UEFI System Utilities the only viable path to re-enable it during an on-site visit.

Why the distractors fail:

• C (iLO Web Interface) is the classic trap answer - if iLO is disabled, the web interface is simply unreachable; you can't use iLO to fix iLO.
• D (HPE OneView) manages servers through iLO, so it also loses communication with the server once iLO is off.
• B (HPE InfoSight) is a cloud-based analytics/monitoring platform - it has no mechanism to reconfigure local server firmware settings.

Memory tip: Apply the "remote vs. local" rule. All three distractors (iLO web UI, OneView, InfoSight) are remote/network-dependent tools. When the remote management channel (iLO) is down, you must fall back to the local hardware interface - UEFI System Utilities - which works regardless of iLO state.

No community discussion yet for this question.