Which of the following activities can be performed through the RES REST APIs?

Question

Options

• AExecuting a ruleset only
• BStarting and stopping the RES server
• CDeploying new artifacts and executing rulesets
• DManaging deployed artifacts such as ruleapps. XOMs. libraries, and execute rulesets

• A
  86% (24)
• B
  7% (2)
• C
  4% (1)
• D
  4% (1)

Explanation

Option A is correct because the RES (Rule Execution Server) REST API is specifically scoped to ruleset execution - it provides an endpoint for client applications to invoke deployed rulesets and receive decision results. It is intentionally narrow in scope, acting as a runtime invocation interface, not an administration tool.

Why the distractors are wrong:

• B is incorrect because starting/stopping the RES server is a server-level administrative operation handled through the application server (e.g., WebSphere, Liberty) or its management console, not the RES REST API.
• C is incorrect because artifact deployment is handled through the Decision Center or the RES Management facilities (console/REST), not the execution-focused REST API.
• D is the most tempting distractor - managing ruleapps, XOMs, and libraries is possible via REST APIs, but through the RES Management REST API, which is a separate API from the RES execution REST API. Mixing the two up is the key trap here.

Memory tip: Think of the RES REST API as a "fire and forget" decision engine - you send inputs, it executes rules, you get results. Everything else (deploying, managing, administering) lives in different tools. If the word is management, it's not the RES REST API.

No community discussion yet for this question.