A developer has created a deep entity class hierarchy with many polymorphic relationships between entitles. Which inheritance strategy, as defined by the inheritance Type enumerated type, will be…

The correct answer is A. Single table-per-class-hierarchy (InheritanceType.SINGLE_TABLE). The Single Table per Class Hierarchy Strategy This strategy provides good support for polymorphic relationships between entities and queries that cover the entire entity class Note:Enum InheritanceType: A single table per class hierarchy. A strategy in which fields that are…

Inheritance Strategies

Question

A developer has created a deep entity class hierarchy with many polymorphic relationships between entitles. Which inheritance strategy, as defined by the inheritance Type enumerated type, will be most performed in this scenario?

Options

ASingle table-per-class-hierarchy (InheritanceType.SINGLE_TABLE)
BJoined-subclass (inheritanceType. JOINED)
CTable-per-concrete-class (inheritanceType.TABLE_PER_CLASS)
DPolymorphic join table (inheritanceType. POLYMORPHIC_JOIN_TABLE)

How the community answered

(46 responses)

A
83% (38)
B
2% (1)
C
9% (4)
D
7% (3)

Explanation

The Single Table per Class Hierarchy Strategy This strategy provides good support for polymorphic relationships between entities and queries that cover the entire entity class Note:Enum InheritanceType: A single table per class hierarchy. A strategy in which fields that are specific to a subclass are mapped to a separate table than the fields that are common to the parent class, and a join is performed to instantiate the subclass. *TABLE_PER_CLASS A table per concrete entity class. Not D: There is no such thing as inheritanceType.POLYMORPHIC_JOIN_TABLE.

Topics

#SINGLE_TABLE strategy#polymorphic relationships#inheritance performance#InheritanceType

Community Discussion

No community discussion yet for this question.

Full 1Z0-898 Practice