An application developer notices that a class in the Java Execution Object Model (XOM) contains a number of methods that should not be imported into the Business Object Model (BOM). How should the…

Question

Options

• AAdd the @NotBusiness annotation.
• BAdd the @BusinessType annotation and specify null as the business type.
• CAdd the @BusinessName annotation and do not specify a value for the annotation.
• DAdd the @ Custom Property annotation and set name of the property as import and

• A
  15% (9)
• B
  3% (2)
• C
  75% (45)
• D
  7% (4)

Explanation

Using @BusinessName without a value is the ODM (Operational Decision Manager) convention for marking a Java method as excluded from BOM publication - an empty or missing value signals to the BOM import engine that the element should be suppressed rather than mapped to a business term.

Why the distractors are wrong:

• A - @NotBusiness does not exist in the ODM annotation library; it is a fabricated option.
• B - @BusinessType controls the type mapping of a Java element in the BOM, not its visibility; setting it to null is not a valid filtering mechanism.
• D - A custom property named import is not the standard ODM mechanism for filtering BOM members, and the option itself appears incomplete, suggesting it is a distractor.

Memory tip: Think of @BusinessName as a label for the BOM. If you give a method no label (@BusinessName with no value), it has no business identity and therefore doesn't show up - "no name, no entry."

No community discussion yet for this question.