A company wants to use ODM rules for a graphical user interface (GUI) validation. They want to use rules to validate forms filled out by customers. The rules would validate user input and answers to…

Question

Options

• AImplement a REST rule service in the XML format.
• BImplement a HTDS rule session to handle the request and response web service call.
• CUse an EJB rule session to handle changing the state of objects in working memory.
• DUse an asynchronous ruleset execution and an observer to end the execution or catch

• A
  85% (40)
• B
  4% (2)
• C
  2% (1)
• D
  9% (4)

Explanation

Option A is correct because a REST rule service is the natural fit for web-based GUI validation - REST calls can be made asynchronously from browser-side JavaScript (e.g., via fetch or XMLHttpRequest), allowing the user to continue navigating the site while the ODM engine processes the request in the background.

Why the distractors are wrong:

• B (HTDS): Hosted Transparent Decision Service uses SOAP/WSDL, a heavier, synchronous protocol ill-suited for lightweight, modern web form validation.
• C (EJB rule session): EJB sessions are heavyweight Java EE components designed for server-side stateful/stateless logic, not for browser-accessible GUI integration.
• D (Asynchronous ruleset execution + observer): This pattern is designed for complex, long-running batch rule executions - overkill for simple form validation, and it adds unnecessary infrastructure complexity.

Memory tip: Think "REST = web-friendly." Any time a question involves browser-based UI, user-facing web forms, or the need for non-blocking HTTP calls to ODM, REST is the integration pattern to reach for. If you see SOAP, EJB, or internal observer patterns, those are server/enterprise signals - not GUI signals.

No community discussion yet for this question.