An application developer has changed the Java XOM. The developer then tries to update the BOM but no differences appear. What are two reasons this could happen? (Select two.)

Question

Options

• AA member in the Java XOM was deleted.
• BA member in the Java XOM was annotated as ©Deprecated.
• COnly the content of a method(s) in the Java XOM were changed.
• DA @NotBusiness annotation was added to a member of the Java XOM.
• EAn additional optional parameter was added to a method{s) in the Java XOM.

• A
  3% (1)
• B
  68% (26)
• C
  11% (4)
• D
  18% (7)

Explanation

In IBM Operational Decision Manager (ODM), the BOM (Business Object Model) synchronizes only with the business-visible API surface of the XOM - method signatures, class structure, and fields - filtered by certain annotations.

B is correct because members annotated with @Deprecated are explicitly excluded from BOM synchronization. The BOM generator skips them entirely, so no difference is detected even though the XOM changed.

E is correct because adding an optional parameter does not alter the existing method's visible signature from the BOM's perspective. The original call pattern remains valid and backward-compatible, so the BOM reconciliation engine sees no net change to the business interface.

Why the distractors are wrong:

• A (member deleted): A deletion does produce a difference - the BOM still references the removed member, flagging it as a mismatch that needs resolution.
• C (only method content changed): Implementation changes are inside the method body and never part of the BOM's structural comparison, but the exam treats this as not the specific ODM-relevant reason - the BOM interface (signature) is unchanged, so there's no architectural trigger tied to ODM's annotation filtering.
• D (@NotBusiness added): This annotation hides a member from the BOM, which would produce a visible difference (the member appears as removed/out-of-sync), not silence.

Memory tip: Think "invisible to BOM = no diff." Deprecated members are invisible because they're skipped by the sync filter; optional parameters are invisible because they don't break the existing contract. Deletions and @NotBusiness are structural events the BOM still notices.

No community discussion yet for this question.