A customer plans to use RESTful API to deploy their rack of DL380 Gen10 systems. How does use of this protocol support the customer? (Select two.)

Question

Options

• Asupport multiple scripting languages
• BSecure remote scripting
• CAbility to run scripts against multiple servers
• DBoot via SFTP
• EBoot via HTTP

• A
  72% (38)
• C
  4% (2)
• D
  8% (4)
• E
  17% (9)

Explanation

RESTful API (specifically HPE's iLO RESTful API / Redfish standard) supports multiple scripting languages (A) because it communicates over standard HTTP using JSON-formatted data - meaning any language that can make HTTP requests (Python, PowerShell, Bash, Ruby, etc.) can interact with it without proprietary libraries. It also provides secure remote scripting (B) because all iLO RESTful API communication runs over HTTPS, encrypting credentials and payloads in transit.

Why the distractors are wrong:

• C (multiple servers): While you can loop a script across many servers, this is a scripting technique, not a feature of the REST protocol itself - it's not what REST uniquely enables.
• D (Boot via SFTP): SFTP is a file transfer protocol, completely unrelated to RESTful API management functions.
• E (Boot via HTTP): UEFI HTTP Boot is a separate firmware-level feature, not something the RESTful API protocol provides.

Memory tip: Think of REST's two core superpowers as "Any Language + Secured Channel" - REST is language-agnostic (it just speaks HTTP/JSON) and secure by default (HTTPS). The boot options (D, E) are distractors designed to confuse REST's use of HTTP as a transport with booting over HTTP, which are entirely different things.

No community discussion yet for this question.