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

When a ruleset's Execution Object Model (XOM) is defined by an XML schema (.xsd file), the schema itself is embedded within the ruleset archive during the build process in Rule Designer. This self-contained ruleset archive is then deployed as part of a RuleApp to the Rule Execution Server (RES). The execution unit (XU) uses this packaged schema to understand the structure of the XML data it receives as input, enabling proper rule execution without needing an externally managed data model.

A. The deployment method is not restricted by the XOM type. RuleApps can be deployed from Rule Designer, the RES console, or through automation scripts (e.g., Ant).
B. The concept of a separately deployed and managed XOM in the Rule Execution Server console is a feature specifically for Java XOMs (JAR files), not for XML XOMs.
C. Deployment is not limited to the Rule Execution Server console. Other methods like deploying directly from Rule Designer or using Ant tasks are fully supported for all XOM types.

1. IBM Operational Decision Manager V8.10.5 Knowledge Center, "Decision Server Rules > Managing rule execution > Deploying rules > Deploying from Rule Designer > Deploying RuleApps".

Section/Content: In the description of the deployment process, it states: "If your ruleset uses an XML object model, the XSD files are automatically included in the ruleset archive." This directly supports the correct answer (D).

2. IBM Operational Decision Manager V8.10.5 Knowledge Center, "Decision Server Rules > Reference > Rule Execution Server management > XOM deployment".

Section/Content: This page details the management of XOMs in RES and explicitly states: "You can deploy a XOM to Rule Execution Server so that it can be referenced by multiple rulesets. This feature is available for Java XOMs only." This directly refutes the claim in option (B).