What happens to the new DML operations in this scenario?

View the Exhibit and examine the undo tablespace attributes. Your database instance is
experiencing a large volume of transactions from non-DBA users in the last one hour. The undo
tablespace NDOTBS1 is full with transactions and no transaction was committed more than one
hour ago. The database has two more undo tablespaces.
What happens to the new DML operations in this scenario?

A.
The DML commands will fail

B.
The undo data generated by the DML is stored in one of the two other undo tablespace

C.
The undo data generated by the DML will overwrite the extents that contain committed undo
data

D.
The undo data generated by the DML is stored in the SYSTEM undo segment of the SYSTEM
tablespace

Explanation:
Tablespaces in the Preconfigured Database (continued)
TEMP:Your temporary tablespace is used when you execute a SQL statement that requires the
creation of temporary segments (such as a large sort or the creation of an index). Just as each
user is assigned a default tablespace for storing created data objects, each user is assigned a
temporary tablespace. The best practice is to define a default temporary tablespace for the

database, which is assigned to all newly created users unless otherwise specified. In the
preconfigured database, the TEMP tablespace is specified as the default temporary tablespace.
This means that if no temporary tablespace is specified when the user account is created. Oracle
Database assigns this tablespace to the user.
UNDOTBS1: This is the undo tablespace used by the database server to store undo information.
If a database uses Automatic Undo Management, it must have exactly one active undo tablespace
per instance at any given time. This tablespace is created at database creation time.
USERS:This tablespace is used to store permanent user objects and data. In the preconfigured
database, the USERS tablespace is the default tablespace for all objects created by nonsystem
users. For the SYS and SYSTEM users (the system users), the default permanent tablespace
remains SYSTEM.
EXAMPLE:This tablespace contains the sample schema* that can be installed when you create
the database. The sample schemas provide a common platform for examples. Oracle
documentation and courseware contain examples based on the sample schemas.
Note:To simplify administration, it is common to have a tablespace for indexes alone.