Online Access Free 1Z0-898 Practice Test

A stateless session bean's business method invokes EJBContext.setRollBackOnly and receives an IllegalStateException.
Under which of these conditions could this be possible?

• A.This Is NOT possible; a stateless session bean cannot invoke EJBContext.SetRollBackOnly.
• B.The business method is marked with the NONSUPPORTED transaction attribute.
• C.The business method is marked with the MANDATORY transaction attribute.
• D.The bean has no metadata (in annotations 01 deployment descriptor) which specifies the transaction attribute for the method.

The developer wants to define a unidirectional relationship from the customer entity to the order entity and map this relationship using a foreign key mapping strategy.
Which one of the pairs of classes below correctly achieves this task?

• A.@Entity public class Customer {
  @Id int customerId;
  @OneToMany @JoinColumn (name = "CUST_ID") Set <Order> orders;
  . . .
  }
  @Entity public class order {
  @Id int orderId;
  . . .
  }
• B.@Entity public class Customer {
  @Id int customerId;
  @OneToMany (JoinColumn = @joinColumn (name = "CUST_ID") Set <Order> orders;
  . . .
  }
  @Entity public class order {
  @Id int orderId;
  . . .
  }
• C.@ Entity public class Customer {
  @Id int customerId;
  @OneToMany (JoinColumn = @JoinColumn (name = "CUST_ID"), table = ""ORDER) Set
  <Order> orders;
  . . .
  }
  @Entity public class order {
  @Id int orderId;
  . . .
  }
• D.@Entity public class Customer {
  @Id int customerId;
  @OneToMany Set <Order> orders;
  . . .
  }
  @Entity
  @JoinColumn (names = "CUST-ID", referencedColumnName = "customerId")
  public class order {
  @Id int order Id;
  . . .
  }

If a Persistence application locks entity x with a pessimistic lock, which statement is true?

• A.A separate lock statement must be called for each subclass in entity hierarchy.
• B.The Persistentprovider will lock the database row(s) that correspond to all persistent fields of properties of an instance, including element collections.
• C.Only single table per class hierarchy mapping is supported with this lock type.
• D.A Persistence provider will lock the entity relationships for which the locked entity contains the foreign key.

The developer wants to write a portable criteria query that will order the orders made by customer James Brown according to increasing quantity. Which one of the below queries correctly accomplishes that task?

• A.CriteriaBuilder cb= . . .
  CriteriaQuery<order> cq = cb.createquery<order.class>
  Root <customer, order> 0 = cq.from(customer.class);
  Join <customer, order> 0 = c.Join(customer-.orders);
  cq.where (cb.equal(c.get(customer_.name, James Brown))); cq.select(0);
  cq.orderBy (0.get (order_.quantity));
• B.CriteriaBuilder cb= . . .
  CriteriaQuery<order> cq = cb.createquery<order.class>
  Root <customer, order> 0 = cq.from(customer.class);
  Join <customer, order> 0 = c.Join(customer-.orders);
  cq.where (cb.equal(c.get(customer_.name, James Brown)));
  cq.orderBy (0.get (order_.quantity));
• C.CriteriaBuilder cb= . . .
  CriteriaQuery<order> cq = cb.createquery<order.class>
  Root <customer, order> 0 = cq.from(customer.class);
  Join <customer, order> 0 = c.Join(customer-.orders);
  cq.where (cb.equal(c.get(customer_.name, James Brown)));
  cq.orderBy (0.get (order_.quantity));
  cq.orderBy ("quantity");
• D.CriteriaBuilder cb= . . .
  CriteriaQuery<order> cq = cb.createquery<order.class>
  Root <customer, order> 0 = cq.from(customer.class);
  Join <customer, order> 0 = c.Join(customer-.orders);
  cq.where (cb.equal(c.get(customer_.name, James Brown)));
  cq.orderBy (0.get (order_.quantity));
  cq.select(0);

It a Persistence application locks entity x with a pessimistic lock, which statement is true?

• A.Persistence provider can defer obtaining the lock until the next synchronization of an entity to the database.
• B.If a lock cannot be obtained, the Persistence provider must throw an exception.
• C.A Persistence provider is not required to support the LockModeType. PESSIMISTIC_WRITE locking type.
• D.A Persistenceprovider will obtain the lock when the entity is refreshed from the database.