Runbook action (An action is composed of multiple steps, in which of the following APIs should each step be required??)

Question

Options

• ARESTful
• BNETCONF
• COpenFlow
• DgRPC

• A
  82% (36)
• B
  2% (1)
• C
  11% (5)
• D
  5% (2)

Explanation

RESTful APIs are the correct choice for Runbook action steps because REST is the universally adopted standard for IT automation platforms - each step in a runbook maps cleanly to a stateless HTTP call (GET, POST, PUT, DELETE), making steps independently executable, composable, and interoperable across different tools and systems.

Why the distractors are wrong:

• NETCONF (B) is a protocol specifically for configuring and managing network devices (routers, switches); it's not a general-purpose automation API for runbook workflows.
• OpenFlow (C) is an SDN (Software-Defined Networking) protocol that controls network switch forwarding planes - entirely unrelated to runbook step orchestration.
• gRPC (D) is a high-performance RPC framework but requires specific generated client libraries and is not the standard interface exposed by IT automation/ITSM platforms for runbook integration.

Memory tip: Think REST = Runbook's Every-Step Standard - REST's stateless, HTTP-based design means any tool, script, or platform can call a runbook step with no special protocol knowledge, which is exactly what multi-step automation requires.

No community discussion yet for this question.