Explanation/Reference:
A: Declarative view objects, those are view objects that don't actually specify a hard coded query. Instead
ADF creates their query at runtime, and it does it based on the data that is requested in your UI layer. This
can be a huge saver of both DB resources and network resources.
C: Just as with normal mode view objects, you can link view objects that you create in declarative SQL
mode to other view objects to form master-detail hierarchies of any complexity.
E: At runtime, when ADF Business Components works with JDBC to pass a query to the database and
retrieve the result, the mechanism to retrieve the data is the SQL query. As an alternative to creating view
objects that specify a SQL statement at design time, you can create entity-based view objects that contain
no SQL statements. This capability of the ADF Business Components design time and runtime is known as
declarative SQL mode. When the data model developer works with the wizard or editor for a view object in
declarative SQL mode, they require no knowledge of SQL. In declarative SQL mode, the view object's
metadata causes the ADF Business Components runtime to generate the SQL query statements
References: http://docs.oracle.com/cd/E37975_01/web.111240/e16182/bcquerying.htm#ADFFD1992