A.SELECT cust_first_name, cust_credit_limit * .05 AS DUE_AMOUNTFROM customersWHERE cust_income_level != NULLAND cust_credit_level !=NULL;

B.SELECT cust_first_name, cust_credit_limit * .05 AS DUE_AMOUNTFROM customersWHERE cust_income_level IS NOT NULLAND cust_credit_limit IS NOT NULL;

C.SELECT cust_first_name, cust_credit_limit * .05 AS DUE_AMOUNTFROM customersWHERE cust_income_level != NULLAND due_amount != NULL;

D.SELECT cust_first_name, cust_credit_limit * .05 AS DUE_AMOUNTFROM customersWHERE cust_income_level <> NULLAND due_amount <> NULL;

E.SELECT cust_first_name, cust_credit_limit * .05 AS DUE_AMOUNTFROM customersWHERE cust_income_level IS NOT NULLAND due_amount IS NOT NULL;

A.Segments can span multiple tablespsaces

B.All tablespaces may have one or more data files

C.The extents of a segment must always reside in the same datafile

D.A segment might have only one extent

E.A smallfile tablespace might be bigger than a bigfile tablespace

F.A segment can span multiple data files in some tablespaces

G.A segment's blocks can be of different sizes

A.A role can be password-protected only if it has been granted system privileges.

B.A role can be granted to other roles.

C.Roles containing object privileges can be created only by the object owner.

D.All roles belong to the SYSTEM schema.

E.Roles can be created only by SYS or SYSTEM.

A.A synonym cannot be created for a PL/SQL package

B.A synonym created by one user can refer to an object belonging to another user

C.A SEQUENCE can have a synonym

D.Any user can drop a PUBLIC synonym

E.A synonym can be available to all users

A.A full outer join returns matched and unmatched rows

B.An inner join returns matched rows

C.Outer joins can only be used between two tables per query

D.A full outer join must use Oracle syntax

E.Outer joins can be used when there are multiple join conditions on two tables

F.A left or right outer join returns only unmatched rows