Which statement is true regarding creating relationships in Maximo?

Question

Options

• ARelationships are used to define business rules.
• BThey enable attributes from one object to be displayed in another.
• CRelationships eliminate the need for custom code.
• DThey are primarily used for database indexing.

• A
  8% (3)
• B
  77% (30)
• C
  13% (5)
• D
  3% (1)

Explanation

In IBM Maximo, relationships define navigational paths between objects, allowing attributes (fields) from a related object to be surfaced and displayed within another object's application - making B correct. Option A is wrong because business rules are defined separately through automation scripts, escalations, or workflow, not relationships. Option C is incorrect because relationships don't eliminate custom code needs; they're a configuration mechanism, not a replacement for scripting. Option D is off-base because indexing is a database-level concern handled in the Database Configuration application, not through relationships.

Memory tip: Think of relationships as "bridges between object islands" - they let you look across to another object and read its data, much like a JOIN in SQL that you configure without writing code. If a question mentions displaying or accessing data from another object in Maximo, relationships are the answer.

No community discussion yet for this question.