OCP Security And Upgrades Practice Test 5 — 15 Questions

Question 1

In 23ai, if you want to audit 'CREATE TABLE' statements, which policy type should you use?

Accepted Answer

Unified Audit Policy. Unified Audit Policies are the modern auditing framework introduced in 12c and fully integrated in 23ai, allowing you to audit specific actions like CREATE TABLE by specifying the privilege or action in a CREATE AUDIT POLICY statement. They replace the legacy traditional audit and provide a single, consistent mechanism for capturing both standard and fine-grained audit events. Because CREATE TABLE is a standard SQL statement, a unified policy with the CREATE TABLE action (or CREATE ANY TABLE privilege) is the correct and simplest way to audit it.

Answer

Fine-Grained Auditing (FGA)

Answer

Logon Trigger

Answer

Traditional Audit

Question 2

When upgrading a database, what is a 'Flashback Database' used for?

Accepted Answer

Quick recovery after a failed upgrade. Flashback Database allows you to quickly rewind an Oracle database to a prior point in time without restoring from backup. During an upgrade, if the upgrade fails or introduces regressions, you can flash back to the guaranteed restore point created before the upgrade, returning the database to its pre-upgrade state in minutes. This is far faster than a full restore and recovery.

Answer

User authentication

Answer

Data migration

Answer

Performance tuning

Question 3

What is the best way to ensure an encrypted connection between the application server and the database?

Accepted Answer

Using Native Network Encryption. The best way to ensure an encrypted connection between the application server and the database is to use Native Network Encryption. This feature encrypts data as it travels over the network between the client and the database server, using algorithms like AES. It is configured on the database server and client via parameters such as SQLNET.ENCRYPTION_CLIENT and SQLNET.ENCRYPTION_TYPES_CLIENT, and it does not require any changes to the application. It provides a straightforward way to secure data in transit.

Answer

Using Audit Vault

Answer

Using Database Vault

Answer

Using TDE

Question 4

What is the primary role of the 'Patching' phase in an upgrade?

Accepted Answer

To apply necessary updates to the dictionary. Ensuring the binaries and the data dictionary match the desired target version.

Answer

To clear the redo logs

Answer

To reorganize the tables

Answer

To increase memory

Question 5

What is the recommended tool to apply a bundle patch to a 23ai environment?

Accepted Answer

OPatch. OPatch is the standard utility for applying patches to Oracle software.

Answer

Enterprise Manager

Answer

RMAN

Answer

AutoUpgrade

Question 6

Which view can you use to check the status of TDE wallet encryption?

Accepted Answer

V$ENCRYPTION_WALLET. V$ENCRYPTION_WALLET displays the status of the wallet used for TDE.

Answer

V$TDE_STATUS

Answer

DBA_ENCRYPTION_STATUS

Answer

DBA_WALLET

Question 7

What happens to a traditional audit record when you migrate to Unified Auditing in 23ai?

Accepted Answer

Stay in separate tables. Traditional audit records are not automatically migrated; you should clear them or archive them before switching to Unified Auditing.

Answer

Automatically converted

Answer

Deleted automatically

Answer

Merged into the Unified Trail

Question 8

Which THREE actions are part of the AutoUpgrade process?

Accepted Answer

Post-upgrade cleanup. AutoUpgrade is Oracle's utility for upgrading Oracle databases, and its workflow consists of distinct phases. Option E, pre-check analysis, is correct because AutoUpgrade runs a preupgrade analysis (via the 'analyze' mode, which invokes the preupgrade checks) to detect issues such as invalid objects, deprecated parameters, and missing prerequisites before any changes are made. Option B, upgrading the database, is correct because the core phase of AutoUpgrade is the 'deploy' mode, which performs the actual database upgrade (including running the upgrade scripts and converting the data dictionary) to the target release. Option A, post-upgrade cleanup, is correct because AutoUpgrade includes a post-upgrade phase (the 'deploy' mode also handles post-upgrade actions, and there is a separate 'finalize' step) that removes obsolete components, recompiles invalid objects, and completes time zone and other cleanup tasks. Option C, applying security patches, is not part of AutoUpgrade, since patching is handled by tools such as OPatch or the patch utilities, not by the upgrade process itself. Option D, rebuilding the OS, is not part of AutoUpgrade, as it operates entirely at the database level and does not touch the operating system.

Answer

Applying security patches

Answer

Rebuilding the OS

Question 9

Which THREE things should be checked before upgrading to 23ai?

Accepted Answer

Current patch levels. Option A (Current patch levels) is correct because Oracle requires the source database to be at a supported patch level (for example, 19c with the latest Release Update) before running the 23ai upgrade, and the upgrade utility will abort if the required patches are missing. Option B (Sufficient temporary tablespace) is correct because the upgrade process performs large sort and hash operations that need adequate TEMP space; insufficient temporary tablespace causes ORA-01652 errors and can fail the upgrade. Option C (Database backup) is correct because a full, tested backup (for example, an RMAN backup plus a guaranteed restore point) is mandatory so the database can be restored if the upgrade fails or must be rolled back. Option D (Table indexes) is not a pre-upgrade requirement, since indexes are automatically maintained and rebuilt as needed by the upgrade scripts. Option E (Application user passwords) is not checked before upgrading, as passwords are preserved in the data dictionary and are unaffected by the 23ai upgrade itself.

Answer

Table indexes

Answer

Application user passwords

Question 10

Which TWO files are modified to configure a secured listener?

Accepted Answer

listener.ora. Option A, listener.ora, is correct because it defines the listener's protocol addresses and static service registrations, and it is where you add the TCPS (TCP with SSL/TLS) protocol address and the SECURE_PROTOCOL_* / SSL_CLIENT_AUTHENTICATION parameters needed to enable a secured listener. Option E, sqlnet.ora, is correct because it holds the client/server-side Oracle Net security settings such as WALLET_LOCATION, SSL_VERSION, SSL_CIPHER_SUITES, and SSL_CLIENT_AUTHENTICATION, which the listener reads to negotiate encrypted connections. Option B, spfile.ora, is not correct because it stores instance initialization parameters, not listener or Oracle Net security configuration. Option C, init.ora, is not correct because it is a legacy instance parameter file and does not configure listener security. Option D, tnsnames.ora, is not correct because it only maps net service names to connect descriptors for clients, not the listener's secured configuration.

Answer

spfile.ora

Answer

init.ora

Answer

tnsnames.ora

Question 11

Which TWO are common audit types in Oracle?

Accepted Answer

Unified Auditing. Unified Auditing (C) is correct because it is Oracle's modern audit framework, introduced in Oracle 12c, that consolidates all audit records into a single unified audit trail stored in the AUDSYS schema and managed via CREATE AUDIT POLICY and AUDIT statements. Standard Auditing (D) is correct because it is the traditional Oracle auditing mechanism (also called traditional auditing), configured with parameters such as AUDIT_TRAIL and the AUDIT statement, and it remains a recognized audit type alongside Unified Auditing. Tablespace Auditing (A) is not a valid Oracle audit type; tablespaces are storage structures, not an auditing category. Instance Auditing (B) is not a standard Oracle audit type; auditing is configured at the database level, not as a separate 'instance' audit mode. Flashback Auditing (E) does not exist in Oracle; Flashback refers to technologies such as Flashback Query, Flashback Drop, and Flashback Database, which are unrelated to auditing.

Answer

Tablespace Auditing

Answer

Instance Auditing

Answer

Flashback Auditing

Question 12

Which THREE factors influence the duration of a database upgrade?

Accepted Answer

Number of database objects. The duration of a database upgrade is directly driven by the volume of work the upgrade engine must process, so the number of database objects (A) matters because each object (tables, indexes, constraints, procedures) must be parsed, converted, and recompiled, and more objects mean more metadata operations. System resources (B), specifically CPU and I/O throughput, determine how fast those operations execute, since an upgrade is largely CPU-bound for compilation and I/O-bound for data and log writes, so faster resources shorten the elapsed time. Database size (E) is also a primary factor because larger data volumes require more time for data conversion, index rebuilds, and log generation during the upgrade. The color of the server (C) is irrelevant since physical appearance has no bearing on performance, and the number of users (D) is not a direct factor in upgrade duration because the upgrade is typically performed with the database in a restricted or single-user mode, so concurrent user count does not affect how long the upgrade itself takes.

Answer

The color of the server

Answer

Number of users

Question 13

Which THREE tasks are performed after an upgrade is finished?

Accepted Answer

Recompile invalid objects. Post-upgrade, you must run the timezone script, recompile invalid objects, and gather dictionary statistics.

Answer

Create new users

Answer

Deinstall old version

Question 14

Which TWO components must be secured to maintain database integrity?

Accepted Answer

Data files. Data files (B) must be secured because they contain the actual database records; unauthorized modification, deletion, or corruption of these files directly destroys the accuracy and consistency of the data, which is the essence of database integrity. Backup files (C) must also be secured because they are the recovery source if data files are damaged or compromised; if backups are tampered with or corrupted, restoring the database would reintroduce bad data, so protecting them preserves integrity across recovery operations. The user manual (A) is documentation only and does not store or affect database records. System logs (D) are useful for auditing and troubleshooting but are not the database content itself, so securing them alone does not maintain data integrity. The client browser (E) is an endpoint interface, not a database component, and securing it does not protect the stored data.

Answer

User manual

Answer

System logs

Answer

Client browser

Question 15

Which THREE items are generally included in an Oracle Patch?

Accepted Answer

Security updates. An Oracle Patch is a collection of fixes applied to the Oracle software, and it generally includes security updates (B), which address known vulnerabilities such as those documented in Oracle Critical Patch Updates; bug fixes (C), which resolve defects in the Oracle binaries and code; and performance improvements (D), which optimize the database or middleware behavior. These three are standard components because Oracle bundles them into patch sets, PSUs, and CPUs to keep the software secure, stable, and efficient. Application source code (A) is not part of an Oracle Patch, since patches modify Oracle's own software, not customer applications. New hardware drivers (E) are also not included, as Oracle Patches target Oracle software components rather than operating system or hardware driver updates.

Answer

Application source code

Answer

New hardware drivers