1Z0-083

Free 1Z0-083 practice questions

10 questions from our 1Z0-083 practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the 1Z0-083 practice exams

Question 1 of 10, Creating and Managing CDBs and PDBs

A DBA manually creates a new CDB with CREATE DATABASE. Which clause makes the new database a multitenant container database?

  1. ASEED FILE_NAME_CONVERT = NONE
  2. BCONTAINER = ALL
  3. CLOCAL UNDO ON
  4. DENABLE PLUGGABLE DATABASE Correct answer

Answer and explanation: ENABLE PLUGGABLE DATABASE in CREATE DATABASE creates CDB$ROOT and PDB$SEED and makes the database a CDB. CONTAINER=ALL is used for parameters, users and grants, LOCAL UNDO ON chooses the undo mode of an existing CDB definition, and SEED FILE_NAME_CONVERT only names seed files and is valid only together with ENABLE PLUGGABLE DATABASE.

Question 2 of 10, Creating and Managing CDBs and PDBs

Which view, queried from CDB$ROOT, shows the open mode and restricted status of every PDB in the current instance?

  1. ADBA_CONTAINER_DATA
  2. BDBA_PDBS
  3. CV$PDBS Correct answer
  4. DCDB_PDB_HISTORY

Answer and explanation: V$PDBS reports the per-instance open mode, restricted flag and other runtime state of each PDB. DBA_PDBS shows dictionary status such as NORMAL or UNPLUGGED rather than the open mode, CDB_PDB_HISTORY records lineage such as creation and plugging events, and DBA_CONTAINER_DATA lists which containers common users may see data for.

Question 3 of 10, Application Containers, Multitenant Security and PDB Mobility

Before plugging an unplugged PDB described by /stage/hr.xml into a new CDB, the DBA wants to know whether it is compatible. Which approach is recommended?

  1. ARun the preupgrade.jar tool against the XML manifest to list blocking issues
  2. BRun DBMS_PDB.DESCRIBE on the XML file and query DBA_PDB_HISTORY
  3. CRun DBMS_PDB.CHECK_PLUG_COMPATIBILITY and review PDB_PLUG_IN_VIOLATIONS Correct answer
  4. DPlug it in with NOCOPY and query V$PDBS for a RESTRICTED value of NO

Answer and explanation: DBMS_PDB.CHECK_PLUG_COMPATIBILITY returns whether the manifest is compatible and records details in PDB_PLUG_IN_VIOLATIONS. DESCRIBE generates a manifest from a non-CDB rather than checking one, plugging in first does the change before checking, and preupgrade.jar analyses a database for upgrade, not a manifest for plug compatibility.

Question 4 of 10, Backup Strategies, RMAN Backups and Database Duplication

Which feature lets RMAN incremental backups read only the changed blocks instead of scanning every block of each data file?

  1. ABlock change tracking Correct answer
  2. BMultisection backups
  3. CBackup optimization
  4. DUnused block compression

Answer and explanation: Block change tracking records changed blocks in a tracking file so incremental backups read only those blocks. Backup optimization skips files already backed up identically, multisection backups split large files across channels, and unused block compression skips never-used blocks but still scans the file.

Question 5 of 10, Backup Strategies, RMAN Backups and Database Duplication

A DBA connects with RMAN to SALESPDB (not to the root) and runs BACKUP DATABASE PLUS ARCHIVELOG. What is the result?

  1. AOnly the SALESPDB data files are backed up and RMAN skips archived logs with a warning
  2. BThe whole CDB is backed up because RMAN always connects to the root behind the scenes
  3. COnly the SALESPDB data files and the archived logs for that PDB's redo thread are backed up
  4. DThe command fails because archived redo logs cannot be backed up from a PDB connection Correct answer

Answer and explanation: Archived redo logs belong to the whole CDB, so they can be backed up only when connected to the root; connected to a PDB, a command that includes them is rejected. There is no per-PDB redo thread, RMAN does not silently switch to the root, and it does not skip the archived logs with a warning.

Question 6 of 10, Restore, Recovery and Flashback Technologies

The SPFILE and all control files are lost. Control file autobackups exist in a known directory outside the FRA, and the DBA knows the DBID. Which steps start the recovery?

  1. ASET DBID; STARTUP NOMOUNT (RMAN uses a dummy parameter file); RESTORE SPFILE FROM AUTOBACKUP; restart NOMOUNT; restore the control file Correct answer
  2. BSTARTUP MOUNT with the default parameter file; RESTORE CONTROLFILE FROM AUTOBACKUP; RESTORE SPFILE TO PFILE; ALTER DATABASE OPEN
  3. CRebuild the control file with CREATE CONTROLFILE RESETLOGS, then restore the SPFILE from the backup recorded in the new control file
  4. DCREATE SPFILE FROM MEMORY in a started instance, then RESTORE CONTROLFILE FROM AUTOBACKUP in MOUNT mode and recover

Answer and explanation: Without an SPFILE, RMAN can start the instance with a dummy parameter file; after SET DBID it can locate and restore the SPFILE from autobackup, then the control file. The database cannot mount without control files, CREATE SPFILE FROM MEMORY needs a running instance with the real parameters, and a recreated control file has no backup records.

Question 7 of 10, Restore, Recovery and Flashback Technologies

All control files are lost. The database is in ARCHIVELOG mode, and control file autobackup is enabled to the fast recovery area. Online redo logs are intact. Which sequence is correct?

  1. ASTARTUP MOUNT; RESTORE CONTROLFILE FROM AUTOBACKUP; RECOVER DATABASE; ALTER DATABASE OPEN
  2. BSTARTUP NOMOUNT; RESTORE CONTROLFILE FROM AUTOBACKUP; ALTER DATABASE MOUNT; RECOVER DATABASE; ALTER DATABASE OPEN RESETLOGS Correct answer
  3. CSTARTUP NOMOUNT; RESTORE DATABASE; RESTORE CONTROLFILE FROM AUTOBACKUP; ALTER DATABASE OPEN NORESETLOGS
  4. DSTARTUP NOMOUNT; CREATE CONTROLFILE REUSE NORESETLOGS from the autobackup piece; ALTER DATABASE OPEN

Answer and explanation: The instance must be started NOMOUNT to restore a control file, then mounted, recovered and opened with RESETLOGS because a backup control file was used. The database cannot mount without a control file, CREATE CONTROLFILE does not read an autobackup piece, and restoring data files is unnecessary when only the control files were lost.

Question 8 of 10, Installation, Patching, Upgrades and Oracle Restart

A 12.1 database on an old big-endian server must move to 19c on Linux with minimal effort and without an in-place upgrade. Which migration method combines the move and the version change?

  1. ADBUA on the Linux host pointing at the 12.1 Oracle home on the old server
  2. BRMAN DUPLICATE FROM ACTIVE DATABASE into a 19c Oracle home on Linux
  3. CData Pump full transportable export and import into a new 19c database Correct answer
  4. DAutoUpgrade in deploy mode run directly against the remote 12.1 server

Answer and explanation: Full transportable export/import moves user data files and metadata into a new 19c database, including across platforms with conversion. AutoUpgrade and DBUA upgrade a database in place on the host where the new Oracle home is installed, and RMAN DUPLICATE cannot convert the endian format between these platforms.

Question 9 of 10, Performance Monitoring and SQL Tuning

New plans have been captured as unaccepted in a SQL plan baseline. The DBA wants Oracle to test them and accept only those that perform better. What should be done?

  1. ADrop the baseline so that the optimizer can pick the best plan freely
  2. BRun DBMS_SPM.LOAD_PLANS_FROM_CURSOR_CACHE for the statement again
  3. CSet OPTIMIZER_USE_SQL_PLAN_BASELINES to FALSE for the instance
  4. DRun an evolve task with DBMS_SPM to verify and accept better plans Correct answer

Answer and explanation: Evolving a baseline executes unaccepted plans, compares them with accepted ones and accepts those that are better (the automatic SPM evolve task does this by default). Reloading from the cursor cache accepts plans without verification, disabling baselines removes plan stability, and dropping the baseline loses protection against regressions.

Question 10 of 10, Oracle Database 18c and 19c Enhancements

In 18c, developers want a table function whose output columns are determined at parse time from the input table they pass, so one function can process any table shape. Which feature fits?

  1. APolymorphic table functions Correct answer
  2. BSQL macros with a fixed return type
  3. CObject types with a constructor method
  4. DPipelined table functions

Answer and explanation: Polymorphic table functions determine their row shape from the arguments at parse time and can work on any input table. Pipelined table functions have a fixed return type, SQL macros were added later than 18c and are not this mechanism, and object constructors build values rather than shaping query output.