As an Autonomous Transaction Processing (ATP) database administrator, you want to extend the storage capacity In the database. Examine this command and output from the database: What is the reason…

Question

Options

• AThe storage quota has been reached for the ATP database.
• BThe create TABLESAPECE statement is not available in ATP.
• CThere is not enough storage available in the ATP database.
• DYou must be explicitly granted the create TABLESPACE privilege in ATP.
• EDatabase Vault prevents you from executing this command.

• A
  4% (1)
• B
  4% (1)
• C
  54% (13)
• D
  17% (4)
• E
  21% (5)

Explanation

In Oracle ATP, the database is provisioned with a fixed storage allocation (e.g., 1 TB). When that allocated space is fully consumed, any operation requiring additional storage - such as creating a new tablespace - will fail with an insufficient space error, which is what the command output demonstrates. The fix is to scale up the ATP storage allocation via the OCI Console, not to adjust privileges or quotas.

Why the distractors are wrong:

• A - A storage quota is a per-user limit on how much space a schema can use (ALTER USER ... QUOTA), which is a different error entirely from the database-level space exhaustion shown here.
• B - CREATE TABLESPACE is executable in ATP by privileged users; it is not outright blocked as a statement type.
• D - The CREATE TABLESPACE privilege can be granted in ATP environments; a missing privilege would produce an ORA-01031: insufficient privileges error, not a space error.
• E - Database Vault enforces data access control policies (e.g., restricting SYS from seeing application data), not storage provisioning commands.

Memory tip: Think "ATP = Autonomous means Oracle manages the engine, but you still need to provision enough gas (storage)." If you run out of provisioned storage, go to the OCI Console and scale it up - no DDL trick will fix a hardware capacity problem.

No community discussion yet for this question.