A.True. After ALTER PLUGGABLE DATABASE ... UNPLUG, CDB_PDBS.STATUS shows UNPLUGGED.

B.False. UNAVAILABLE isn’t a valid status here.

C.False. REMOVED isn’t used; UNPLUGGED persists until dropped.

D.False. DISABLED isn’t a PDB state in this context.

A.False. No checkpoint occurs with ABORT.

B.False. Instance recovery, not media recovery, is needed.

C.True. Crash recovery rolls back uncommitted changes on startup.

D.False. Files aren’t closed cleanly with ABORT.

E.True. Shutdown doesn’t roll back; recovery does.

A. Dependent indexes become UNUSABLE.False. SHRINK SPACE COMPACT does not affect index usability; only SHRINK SPACE without COMPACT may require index maintenance if CASCADE is omitted.

B. ... starting toward the end of the ORDERS segment.False. Rows are compacted toward the beginning of the segment, not the end.

C. Only queries are allowed ...False. Both queries and DML are allowed during SHRINK SPACE COMPACT as it’s an online operation.

D. The high-water mark (HWM) of ORDERS is adjusted.False. COMPACT moves rows but doesn’t adjust the HWM; the full SHRINK SPACE command is needed for HWM adjustment.

E. Queries and DML statements are allowed ...True. This is an online operation in 23ai, allowing concurrent access.

F. ... starting from the beginning of the ORDERS segment.True. Rows are moved to fill free space from the segment’s start.

A.False. Backups are via RMAN, not AMTs.

B.True. Stats collection is an AMT.

C.False. Error logging isn’t an AMT.

D.True. SPM tasks are included.

E.False. Notifications aren’t AMTs.

F.True. Segment Advisor is an AMT.

Temp UNDO, introduced in Oracle 12c and refined in 23ai, stores undo for global temporary tables (GTTs) in temporary tablespaces:

A. It permits DML on GTTs even if the database is opened read-only.False. In read-only mode, DML on GTTs is allowed regardless of temp UNDO, as GTT data is session-private, but temp UNDO doesn’t specifically enable this.

B. It reduces the amount of UNDO stored in the UNDO tablespace.True. Temp UNDO stores undo in the temporary tablespace, reducing usage of the permanent UNDO tablespace.

C. It reduces I/Os to the SYSTEM tablespace.True. By avoiding permanent undo, it reduces metadata updates in the SYSTEM tablespace related to undo management.

D. It reduces the amount of redo generated.True. Temp UNDO changes are not redo-logged to the same extent as permanent undo, minimizing redo generation.

E. It reduces I/Os to the SYSAUX tablespace.False. SYSAUX is unrelated to undo management; temp UNDO affects temporary and SYSTEM tablespaces.

A.True. DBA_EXTERNAL_LOCATIONS (or prefixed variants) shows external table data sources (e.g., file paths).

B-D.False. These views cover columns or tables but not external sources specifically.

A.False. AWR doesn’t create PDBs.

B.True. AWR stats aid migration planning (e.g., performance baselines).

C.False. AWR doesn’t convert CDB to Non-CDB.

D.False. SID management isn’t AWR’s role.

A.False. One instance can’t mount multiple DBs without multitenant.

B.True. RAC allows multiple instances to share one DB.

C.False. Same as A; not possible without CDB.

D.True. An instance can start in NOMOUNT with no DB.

E.True. Standard single-instance configuration.