Which statement is true when deploying a RuleApp archive?

Question

Options

• AA managed Java XOM in the RuleApp archive must follow a XOM versioning policy.
• BJava XOM's must always be included in RuleApp archives to guarantee version
• CResource and library versioning polices only apply when managed XOM's are present in
• DRuleApp archives must be configured from the ruleset view first to define the rulesets to

• A
  88% (29)
• B
  3% (1)
• C
  6% (2)
• D
  3% (1)

Explanation

When a Java XOM (Execution Object Model) is bundled as a managed artifact inside a RuleApp archive, IBM ODM requires it to comply with a XOM versioning policy. This ensures that the Rule Execution Server can correctly track, resolve, and manage the XOM across deployments - preventing version conflicts between rulesets and the business object model they depend on.

Why the distractors are wrong:

• B is false because Java XOMs do not have to be included in every RuleApp archive - they can be deployed separately as external (unmanaged) XOMs, with the RuleApp simply referencing them.
• C is false because versioning policies are not limited to scenarios where managed XOMs are present; they apply more broadly to resources and libraries in the deployment lifecycle.
• D is false because RuleApp archives are not required to be configured starting from the ruleset view - configuration can follow different workflows depending on the tooling and deployment approach used.

Memory tip: Think "Managed = Must follow policy." The moment you manage a XOM inside the archive (rather than keeping it external), you take ownership of its versioning - just like checking a dependency into your own repo means you're responsible for its version pinning.

No community discussion yet for this question.