A. If a lock cannot be obtained, the Persistence provider must throw an exception.

B. Persistence provider can defer obtaining the lock until the next synchronization of an entity to the database.

C. A Persistenceprovider will obtain the lock when the entity is refreshed from the database.

D. A Persistence provider is not required to support the LockModeType. PESSIMISTIC_WRITE locking type.

A. LockModeType. PESSIMISTIC_READ is the synonym of the LockModeType.REA

B. This operation will force serialization among transactions attempting to read the entity data.

C. If the application later updates the entity, and the changes are flushed to the database, the lock will be converted to an exclusive lock.

D. This operation will result in a TransactionRolledbackException if the lock cannot be obtained.

A. Use an @id property that constructs a private field as a concatenation of two columns.

B. 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.

C. 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.

D. 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.

E. 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.

A. The bean has no metadata (in annotations 01 deployment descriptor) which specifies the transaction attribute for the method.

B. The business method is marked with the NONSUPPORTED transaction attribute.

C. The business method is marked with the MANDATORY transaction attribute.

D. This Is NOT possible; a stateless session bean cannot invoke EJBContext.SetRollBackOnly.

A. CriteriaBuilder cb = ...
CriteriaQuery<Customer> cq = cb.createquery(customer.class)
Root<Customer> c = cq.from(Customer.class);
Join<Customer, Order> o = c.join(Customer__.orders);
cq.select(c).distinct(true);
Subquery<Double> sq = cq.subquery(Double.class);
Root<Order> subo = cq.correlate(o);
sq.select(cb.max(subo.get(Order_.totalPrice)));
cq.where(cb.equal(o.get(Order_.totalPrice), cb.all(sq)));

B. CriteriaBuilder cb = ...
Criteria Query <Customer> cq = cb.create Query (Customer.class);
Root<Customer> c = cq.from(Customer.class);
Join<Customer, Order> o = c.join(Customer__.orders);
cq.select(c).distinct(true);
Subquery<Double> sq = cq.subquery(Double.class);
Root<Order> subo = cq.correlate(o);
sq.select(cb.max(subo.get(Order_.totalPrice)));
cq.where(cb.equal(o.get(Order_.totalPrice), cb.all(sq)));

C. CriteriaBuilder cb = ...
CriteriaQuery<Customer> cq = cb.createQuery(Customer.class);
Root<Customer> c = cq.from(Customer.class);
Join<Customer, Order> o = c.join(Customer_.orders);
cq.select(c).distinct(true);
Subquery<Double> sq = cq.subquery(Double.class);
Root<Order> subo = sq.from(Order.class);
sq. select (ci: . max ( subo . get (Order_ . Total Price) ) ) ;
cq.where(sq.all(o.gei(Order_.totalPrice)));

D. CriteriaBuilder cb = ...
CriteriaQuery<Customer> cq = cb.cteateQuery(Customer.class);
Root<Customer> c = cq.from(Customer.class);
Join<Customer, Order> o = c.join(Customer__.orders);
cq.select(c).distinct(true);
Subquery<Double> sq = cq.subquery(Double.class);
Root<Order> subo = cq.correlate(o);
sq.select(cb.max(subo.get(Order_.totalPrice)));
cq.where(cb.equal(o.get(Order_.totalPrice), cb.all(sq)));

A. Table-per-concrete-class (inheritanceType.TABLE_PER_CLASS)

B. Single table-per-class-hierarchy (InheritanceType.SINGLE_TABLE)

C. Polymorphic join table (inheritanceType. POLYMORPHIC_JOIN_TABLE)

D. Joined-subclass (inheritanceType. JOINED)

A. A new persistence context begins when a new JTA transaction begins.

B. A new persistence context begins when the entity manager is invoked in the context of a resource-local transaction.

C. A new persistence context begins when the entity manager is invoked in the context o\ transaction.

D. A new persistence context begins when the entity manager is created.