1Z0-182 Oracle Database 23ai Administration Associate Practice Questions

The Database Writer (DBWn) process is responsible for writing dirty buffers (modified data blocks) from the database buffer cache to the physical datafiles on disk. This is a background operation that happens asynchronously to user commits. LGWR writes redo information to log files, CKPT updates file headers, and SMON performs instance recovery tasks.

The AutoTask framework is designed to automate routine maintenance activities, such as gathering optimizer statistics, running the Segment Advisor, and running the SQL Tuning Advisor. These tasks are scheduled to run automatically during predefined maintenance windows to ensure the database remains healthy and performs optimally without requiring constant manual intervention.

Oracle Data Pump Export (expdp) is the primary tool for creating logical backups of database objects and data. It can operate at various levels, including a full database, specific schemas, or individual tables. The output is a portable dump file set that can be imported into another Oracle database using Data Pump Import (impdp). RMAN performs physical backups, and SQL*Loader is for loading data into the database.

The Alert Log is the primary source for chronological information about the database's health and status. It records major events, errors, and administrative commands. In modern Oracle versions, the alert log is an XML-formatted file located within the Automatic Diagnostic Repository (ADR), which centralizes all diagnostic data. The listener log is for network connections, and redo logs are for data recovery.

To change a dynamic parameter immediately and have it persist, SCOPE=BOTH is used. This applies the change to the current running instance (memory) and also writes it to the server parameter file (SPFILE) so it will be used in subsequent startups. SCOPE=MEMORY only affects the current instance and is lost on restart. SCOPE=SPFILE only writes to the SPFILE and takes effect on the next restart.

The statement is false. The DBA_TABLESPACES view contains metadata about the tablespaces themselves, such as their names, types, and default storage parameters. To find the amount of free space, you must query views like DBA_FREE_SPACE or join DBA_DATA_FILES with DBA_FREE_SPACE.

The logical storage hierarchy in Oracle is: Tablespace -> Segment -> Extent -> Data Block. A tablespace is the largest logical unit, which contains one or more segments (e.g., a table or an index). Each segment is made up of one or more extents, which are contiguous collections of data blocks. The data block is the smallest unit of I/O.

By default, the SYS user is excluded from unified audit policies to prevent excessive audit record generation from routine administrative tasks. To include SYS actions, the AUDIT_SYS_OPERATIONS initialization parameter must be set to TRUE. The other options are syntactically incorrect or do not achieve the desired outcome; policies are not enabled with a BY SYS clause in the AUDIT statement itself.

The 'db file sequential read' wait event is typically associated with single-block I/O operations, which are characteristic of index lookups or reads from ROWID access. This indicates that the database is reading many individual blocks from disk, likely via indexes. In contrast, 'db file scattered read' is associated with multi-block reads, such as full table scans. Latch contention and log file sync waits point to different types of bottlenecks.

The SNAPSHOT COPY clause allows for the creation of a PDB clone while the source PDB remains online in read-write mode. This is possible if the underlying storage system supports storage snapshots. If snapshots are not supported, the source PDB must be in read-only mode for the duration of the clone. The other options are not valid clauses for this purpose.