what is the most appropriate server-side component, or method to use to provide access to the configurable options stored by the e-commerce application?

You are designing an extension to an existing, high-volume Java EE-based e-commerce

application that provides enhanced customization and personalization features to users. Users
must be able to change both the content and look and feel of what they see on the home page,
add favorite items to a “My Favorites” area, and have items suggested to them by the application
based on prior purchasing behavior. All site actions participate in a new or existing transaction to
track and audit user behavior across the site for later analysis. Given these requirements, what is
the most appropriate server-side component, or method to use to provide access to the
configurable options stored by the e-commerce application?

A.
Accessing the persistence tier directly from the presentation tier (JSPs)

B.
A stateful session bean accessing a well-defined persistence tier using the DAO design
pattern.

C.
A stateless session bean accessing a well-defined persistence tier using the DAO design
pattern.

D.
A Plain Old Java Object (POJO) accessing a well-defined persistence tier using the DAO
design pattern