READ Free Dumps For Oracle- 1z0-898
Question ID 4558 | A developer has created a deep entity class hierarchy with many polymorphic relationships between entitles. Which inheritance strategy, as defined by the inheritanceType enumerated type, will be most performed in this scenario? |
Option A | A. Single table-per-class-hierarchy (InheritanceType.SINGLE_TABLE) |
Option B | B. Joined-subclass (inheritanceType. JOINED) |
Option C | C. Table-per-concrete-class (inheritanceType.TABLE_PER_CLASS) |
Option D | D. Polymorphic join table (inheritanceType. POLYMORPHIC_JOIN_TABLE) |
Correct Answer | A |
Question ID 4559 | A developer is creating an entity which is mapped to a table that has a primary key constraint defined on two character columns and would like to use mapping defaults as much as possible to simplify the code. |
Option A | A. Use an @id property that constructs a private field as a concatenation of two columns. |
Option B | B. Use a separate class to map those two columns and use an @idclass annotation to denote I primary key field or property in the entity. |
Option C | C. Use a separate @Embeddable class to map those two columns and use an @EmbeddedId annotation to denote a single primary key field or property in the entity. |
Option D | D. Use a separate @Embeddable class to map those two column and add two fields or properties the entity, each marked as @id, that correspond to the fields or properties in the embeddable class. |
Option E | E. Use a separate class to map those two columns. Specify that class using @Idclass annotation on the entity class. Add two fields or properties to the entity, each marked as @Id, that correspond to the fields or properties in that separate class. |
Correct Answer | C,E |