I Think A, D. D -> If the ON COMMIT is transaction specific -> COMMIT, ROLLBACK delete rows. NOT C-> Allocation of temporal segments are done on USER TEMP TABLESPACE, at time of use table, no always in the TEMP TABLESPACE of the OWNER.

C isn't correct: By default, Oracle stores the data of the global temporary table in the default temporary tablespace of the table’s owner. But you can explicitly assign another tablespace to a global temporary table during table creation using the TABLESPACE clause https://www.oracletutorial.com/oracle-basics/oracle-global-temporary-table/

AD is correct

AD is correct

AD is correct

Option A is correct. Indexes can be created on global temporary tables, allowing for efficient data retrieval and manipulation. Option D is correct. If the ON COMMIT clause is specified as transaction-specific (ON COMMIT DELETE ROWS), all rows in the global temporary table are automatically deleted after each COMMIT or ROLLBACK statement. This ensures that the table is cleared for the next transaction.

A D are correct: D. If the ON COMMIT clause is transaction-specific, all rows in the table are deleted after each COMMIT OR ROLLBACK. ''all rows in the table are deleted'' = TRUNCATE

AC is correct D is wrong, because : The ON COMMIT clause specifies whether data in the table is transaction-specific or session-specific: The ON COMMIT DELETE ROWS clause specifies that the global temporary table is transaction-specific. It means that ORACLE TRUNCATE THE TABLE after each commit. The ON COMMIT PRESERVE ROWS clause specifies that the global temporary table is session-specific, meaning that ORACLE TRUNCATE THE TABLE when you terminate the session, not when you commit a transaction. Delete is DML, truncate is DDL

I think A,C

I think are A and C