What predefined user is created when provisioning an Autonomous Database (ADB) instance to which you connect to create other users and grant roles?
Correct Answer:
B
When provisioning an Autonomous Database (ADB) instance, Oracle creates a default administrative user with extensive privileges. The correct user is:
ADMIN (B): The ADMIN user is automatically created during ADB provisioning and serves as the primary administrative account. It has full privileges to manage the database, including creating users, granting roles, and performing administrative tasks (e.g., scaling, backups). For example, after provisioning an ADB via the OCI console, you'd connect as ADMIN using the password you set, then run commands like: CREATE USER analyst1 IDENTIFIED BY 'password'; GRANT CONNECT, RESOURCE TO analyst1;. This user is the entry point for initial configuration and ongoing management, authenticated via the client wallet for secure access (e.g., sqlplus admin/password@adb_high). The ADMIN user is distinct from traditional Oracle users like SYS because ADB's managed nature limits direct system-level access, funneling administration through ADMIN.
The incorrect options are:
SYS (A): In traditional Oracle databases, SYS is the superuser with ultimate control (e.g., owning the data dictionary). In ADB, however, SYS exists but is locked and inaccessible to customers due to the fully managed environment---Oracle manages system-level operations, and users connect as ADMIN instead.
DWDEV (C): There's no predefined DWDEV user in ADB. This might confuse with roles like DWROLE (for Data Warehouse developers), but no such user is created by default.
SCOTT (D): SCOTT is a sample user from older Oracle versions (with tables like EMP and DEPT), not created in ADB. It's irrelevant in this modern, managed context.
The ADMIN user's role ensures customers can manage ADB without needing Oracle's intervention, aligning with its autonomous design.
