Identify three situations in which you would NOT be able to drop a tablespace. (Choose three.)

A tablespace being online is not a barrier to dropping it; Oracle allows DROP TABLESPACE on online tablespaces as long as no other blocking conditions exist.

A tablespace that contains data can still be dropped by using the INCLUDING CONTENTS clause, so the mere presence of segments with data is not an absolute restriction.

A tablespace designated as the default permanent tablespace for the database cannot be dropped because Oracle would have no valid target for new user segment creation. You must first reassign the default permanent tablespace to another tablespace before dropping it.

If objects in a tablespace are currently involved in open, uncommitted transactions, Oracle cannot drop the tablespace because doing so would destroy the data blocks still in use by those active transactions, causing data corruption.

Oracle protects undo data that is still needed to support a rollback of an uncommitted transaction. Dropping the tablespace while this undo is in use would make it impossible to roll back the pending transaction, violating ACID guarantees.