Select Two (Multi-Select) Questions

VERIFY

Used for data integrity checks.

INSERT

Required for adding logs.

SELECT

Required for auditing.

Simplified application development

Easier data handling.

Data consistency

Relational integrity is maintained.

Native SQL support

Standard queries work.

Stores backup metadata for multiple databases.

This is a primary benefit.

Allows keeping backup history longer than the control file.

The control file is limited by CONTROL_FILE_RECORD_KEEP_TIME.

Restoring datafiles to the disk.

This is the primary restore action.

Updating the control file with file locations.

The control file is updated to reflect the restored files.

Verifying the integrity of the backup pieces.

RMAN checks the backup integrity during restore.

AI Vector Search

Simplifies AI workflows.

JSON Duality

Simplifies data mapping.

Lock-Free Reservations

Simplifies concurrency.

CONFIGURE BACKUP OPTIMIZATION ON;

Skips files that haven't changed.

CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;

Reduces I/O load by compressing data.

The RMAN CONVERT command must be used if endianness differs.

Conversion is required if moving between platforms with different endianness.

The source tablespace must be set to READ ONLY.

The tablespace must be read-only to ensure data consistency during the transfer.

The compatibility level must be at least 11.0.0.

A minimum compatibility level is required to support the transportable tablespace metadata format.

Lock-Free Reservations

Reduces contention.

Memoptimized Write

Reduces ingest latency.

Exporting the recovered table to the target database using Data Pump

Data Pump is used to import the table back into the target database.

Restoration of the tablespace containing the table to an auxiliary location

The tablespace is restored to a temporary location to extract the table.

Creation of an auxiliary instance

The command creates a temporary instance to perform the recovery.

Unified Auditing

The current, recommended audit method.

Standard Auditing

The traditional audit method.

Create the keystore

Required step.

Set WALLET_LOCATION

Required in sqlnet.ora.

Open the wallet

Must be open to encrypt.

Post-upgrade cleanup

Finalizes the upgrade.

Upgrading the database

The main action.

Pre-check analysis

Essential for identifying issues.

Number of database objects

More objects take longer to process.

System resources (CPU/IO)

Hardware limits speed.

Database size

Larger data volumes affect the upgrade time.

Helps with compliance

Required for many standards.

Protects data at rest

Primary benefit.

Current patch levels

Required for a supported path.

Sufficient temporary tablespace

Necessary for upgrade scripts.

Database backup

Mandatory for safety.

SQLNET.ENCRYPTION_TYPES_SERVER

This specifies the allowed encryption algorithms for the server.

SQLNET.ENCRYPTION_SERVER

This parameter controls the server-side encryption requirement.

listener.ora

Configures the listener endpoint.

sqlnet.ora

Configures encryption and wallet settings.

Data Guard

Provides a standby instance.

Flashback Database

Allows point-in-time recovery.

Apply the latest quarterly Release Update (RU)

Regular patching mitigates known vulnerabilities.

Use Oracle Key Vault for TDE master key management

Centralized key management is a security best practice.

Enforce strong password profiles

Password complexity is essential for preventing brute-force attacks.

OPatchAuto

Automated tool for applying RUs to grid infrastructure and database homes.

Fleet Patching and Provisioning (FPP)

An enterprise-grade tool for managing patches across many servers.

OPatch

Standard utility for applying one-off patches.