A.Their data can be retrieved by using only SQL or PL/SQL.

B.You can populate them from existing data in the database by using the CREATE TABLE AS SELECT command.

C.Indexes can be created on them.

D.Their metadata and actual data are both stored outside the database.

E.DML statements cannot be used on them.

A.SELECT dept_id( INSTR(last_name, 'A'), SUM (salary) FROM employees GROUP BY dept_id;

B.SELECT dept_id, STDDEV(last_name), SUM( salary) FROM employees GROUP BV dept_id;

C.SELECT dept_id, LENGTH (last: name) , SUM(salary) FROM employees GROUP BV dept_id;

D.SELECT dept_id, MAX (last_name) . SUM(salary) FROM employees GROUP BY dept_id;

A.It is possible for child rows that have a foreign key to be deleted automatically from the child table at the time the parent row is deleted.

B.Primary key and foreign key constraints can be defined at both the column and table level.

C.The foreign key columns and parent table primary key columns must have the same names.

D.A table can have only one primary key and one foreign key.

E.A table can have only one primary key but multiple foreign keys.

F.It is possible for child rows that have a foreign key to remain in the child table at the time the parent row is deleted.

G.Only the primary key can be defined the column and table level.

A.A row whose LIST_PRICE column contains value 11235.90 would be displayed as $1,123.

B.A row whose LIST_PRICE column contains value 1123.90 would be displayed as $1,124.

C.A row whose LIST_PRICE column contains value 1123.90 would be displayed as $1,123.

D.A row whose LIST_PRICE column contains value 11235.90 would be displayed as #######.

A.SELECT dept_id, join_date, SUM(salary) FROM employees GROUP BY dept_id;

B.SELECT dept_id, MAX (AVG(salary)) FROM employees GROUP BY dept_id;

C.SELECT dept_id, AVG(NAX(salary)) FROM employees GROUP BY dept_id;

D.SELECT dept_id, join date, SUM(salary) FROM employees GROUP BY dept_id,join_date;