As the architect for a corporation, you are focused on how best to design the persistence layer of
the in-house stock inventory application. Key operations that must be supported, in addition to
insert, read, update and delete are: bulk updates and deletes, complex queries including sub
queries, JOINs and dynamic queries. Ease of development and a future-proof approach is
important, but you realize that ease of development is academic if the approach selected does
NOT meet the core technical requirements. What is the best approach to architecting the
persistence layer for the application?
A.
Use entity beans, accessed by a session bean layer to provide unit-of-work, security and
transaction semantics
B.
Use JDBC-based layer, accessed by a session bean layer to provide unit-of-work, security,
and transaction semantics
C.
Do NOT provide a logically distinct persistence layer, but rather use session beans to access
the database directly using JDBC
D.
Use a JPA-based persistence layer, accessed by a session bean layer to provide unit-ofwork, security, and transaction semantics