The EMPLOYEES table has these columns:LAST_NAME VARCHAR2(35) SALARY NUMBER(8,2) HIRE_DATE DATEManagement wants to add a default value to the SALARY column. You plan to alter the table by using this SQL statement:ALTER TABLE EMPLOYEES MODIFY (SALARY DEFAUL

Deleting the records of employees who do not earn commission.

Increasing the commission of employee 3 by the average commission earned in department 20.

Finding the number of employees who do NOT earn commission and are working for department 20.

Inserting into the table a new employee 10 who works for department 20 and earns a commission that is equal to the commission earned by employee 3.

Creating a table called COMMISSION that has the same structure and data as the columns EMP_ID and COMMISSIONS of the EMP table.

Decreasing the commission by 150 for the employees who are working in department 30 and earning a commission of more then 800.

An error is generated.

You will have two identical tables in the HR schema with different names.

You create a table called employees in the HR schema based on you EMP table.

You create an alternative name for the employees table in the HR schema in your own schema.

 All the triggers are disabled.

 All the triggers are enabled by default.

 Enabled triggers remain enabled and disabled triggers remain disabled.

 Triggers are deleted when a Flashback Table operation is performed.

DELETE employees;

DESCRIBE employees;

ROLLBACK TO SAVEPOINT C;

GRANT SELECT ON employees TO SCOTT;

ALTER TABLE employees   SET UNUSED COLUMN sal;

Select MAX(sal)   FROM employees   WHERE department_id = 20;

a table name which has 100s of records

a table name which has 10s of records

a table name which has empty records

a table name which has 1000s of records

never use a table name

Column definitions cannot be altered to add DEFAULT values.

A change to the DEFAULT value affects only subsequent insertions to the table.

Column definitions cannot be altered to add DEFAULT values for columns with a NUMBER data type.

All the rows that have a NULL value for the SALARY column will be updated with the value 5000.

DELETE employees;

DESCRIBE employees;

ROLLBACK TO SAVE POINT C;

GRANT SELECT ON employees TO SCOTH

ALTER TABLE employees SET UNUSED COLUMN sal;

Select MAX(sal) FROM employees WHERE department _ id 20;

MERGE

INSERT

UPDATE

ADD

ENTER

You cannot enter the phone numbers for the existing employee records.

DROP USER SMITH；

DROP TABLE EMPLOYEES；

DROP TABLESPACE USERS；

ALTER TABLE SALES_REP DROP PARTITION P1；

ALTER TABLE EMPLOYEES DROP COLUMN DESIG_ID；

null lock on the row being updated

null lock on the table containing the row

ROW SHARE lock for the row being updated

ROW EXCLUSIVE lock for the row being updated

shared row-exclusive lock for the row being updated

a shareable table lock for the table containing the row

exclusive table-level lock for the table containing the row

You get an error because of a primary key violation.

The data and structure of the EMPLOYEES table are deleted.

The data in the EMPLOYEES table is deleted but not the structure.

You get an error because the statement is not syntactically correct.

You get an error because of a primary key violation.

The data and structure of the EMPLOYEES table are deleted.

The data in the EMPLOYEES table is deleted but not the structure.

You get an error because the statement is not syntactically correct.

The EMPLOYEES table will be changed to read-only mode during the shrink operation.

The indexes created on the EMPLOYEES table will need to be rebuilt after the shrink operation is over.

The shrink behavior will be cascaded to all dependent segments of the table that support a shrink operation.

Data manipulation language (DML) operations will not be possible on the EMPLOYEES table during the COMPACTION phase of the shrink operation.

if a table is not in a cluster

if a table has an active trigger

if a table has an encrypted

if a table has a column of data type LONG defined on it

if a table has a referential integrity constraint defined on it

Only the EMPLOYEES table.

Only the EMPLOYEES table and its corresponding primary key index.

The EMPLOYEES table and partition P1.

The EMPLOYEES table， IPK_EMP index， and the SALES table.

ALTER TABLE employees monitor index employee_idx_fk; 

ALTER INDEX employee_idx_fk monitoring on; 

ALTER TABLE employees monitor all indexes; 

ALTER INDEX employee_idx_fk monitoring usage; 

The data in the segment will be compacted but the high water mark will not be adjusted 

The EMPLOYEES table will be changed to read-only mode during the shrink operation 

The indexes created on the EMPLOYEES table will need to be rebuilt after the shrink operation is over

The shrink behavior will be cascaded to all dependent segments of the table that support a shrink operation 

Data manipulation language (DML) operations will not be possible on the EMPLOYEES table during the COMPACTION phase of the shrink operation

hiring employees with special talent

encouraging employees to co-operate

helping employees work independently

training employees in their special fields