Which statement is true if a ruleset's XOM is based on an XML schema (.xsd file)?

Question

Options

• AThe RuleApp can only be deployed from Rule Designer.
• BA managed XOM must be deployed to execute the ruleset.
• CThe XOM can only be deployed by using the Rule Execution Server console.
• DThe XML schema is packaged as a .xom file in the ruleset archive and deployed with the

• A
  7% (2)
• B
  3% (1)
• C
  73% (22)
• D
  17% (5)

Explanation

When a ruleset's XOM is based on an XML schema (.xsd file), IBM ODM requires the schema to be deployed as a managed XOM artifact, and that managed XOM can only be deployed through the Rule Execution Server (RES) console - it cannot be bundled inside the ruleset archive or pushed via Rule Designer like a Java-based XOM can. This is because the XML schema is an external, server-managed artifact that must be registered at the RES level so the execution engine can locate it at runtime.

Why the distractors are wrong:

• A is wrong because RuleApp deployment restrictions are unrelated to whether the XOM uses an XML schema - the RuleApp itself can still be deployed from multiple tools.
• B is misleading: while a managed XOM is indeed required, it doesn't accurately capture the key constraint - how it must be deployed (only via the RES console).
• D is wrong because the XML schema is not packaged inside the ruleset archive; that's precisely the point - it must be deployed separately.

Memory tip: Think "XSD = eXternal Server Deployment." When your XOM is an .xsd file, it belongs to the eXecution Server console - it never travels inside the ruleset archive.

No community discussion yet for this question.