CCNA Security And Upgrades Questions

Using Oracle Key Vault, enforcing password complexity, and applying the latest Release Updates are core hardening practices.

The Pre-Upgrade Information Tool (preupgrade.jar) is mandatory for evaluating the source database.

The listener.ora file must be configured with the SSL_CLIENT_AUTHENTICATION and WALLET_LOCATION parameters.

AutoUpgrade performs fixups automatically, but you can also run them manually using the pre-upgrade fixup scripts.

The data dictionary will be inconsistent, and many objects will be invalid, leading to database failure.

It is critical to take a full backup of the database before applying any patches.

Database Vault Realms are specifically designed to restrict access to data by privileged users.

DRCP reduces the memory footprint of a database by pooling server processes.

SQL*Plus, EM, and the Oracle Security Dashboard are standard management tools.

The data files and the backup files must be secured to prevent tampering.

Database Vault restricts access to application data by privileged users like SYS.

Use a Unified Audit Policy with the 'WHEN' clause to filter the user and the 'OBJECT' clause for the table.

OPatch, OPatchAuto, and Fleet Patching and Provisioning (FPP) are the standard methods for patching Oracle databases.

The Pre-Upgrade Information Tool (preupgrade.jar) is the standard method for identifying parameter incompatibilities.

Data Guard and Flashback Database are key for availability and recovery.

A wallet stores sensitive credentials like passwords and encryption keys.

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

Transportable Tablespaces combined with Data Guard or GoldenGate typically offers the lowest downtime.

Insufficient space, incorrect permissions, or already running processes are common blockers.

A keystore (wallet) is required to hold the master encryption key for TDE.

V$ENCRYPTED_TABLESPACES shows the encryption status of all tablespaces in the database.

CREATE AUDIT POLICY policy_name ACTIONS ALL BY APP_USER is the correct syntax for auditing all actions by a specific user.

Data masking permanently obscures sensitive data in a non-production environment.

listener.ora and sqlnet.ora are both typically involved in network security configuration.

The AutoUpgrade tool provides a job monitor output in the log file directory.

The command is 'java -jar autoupgrade.jar -config <config_file>'.

SQLNET.ENCRYPTION_SERVER and SQLNET.ENCRYPTION_TYPES_SERVER are the primary parameters for configuring server-side network encryption.

Unified Auditing provides a single, unified audit trail for all audit records from various sources.

TDE provides security for data at rest and helps with regulatory compliance.

Flashback Database allows you to quickly revert to a point-in-time if the upgrade fails.

Patches typically contain bug fixes, security updates, and performance improvements.

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

System resources, disk space, and patch levels are critical checks.

Configuring Native Network Encryption (NNE) or TLS on the listener ensures encrypted traffic.

DBMS_COMPARISON requires a database link between the source and target databases.

Unified audit records are stored in a secure table in the SYSTEM tablespace.

AutoUpgrade uses a configuration file in a specific text-based key-value format (cfg file).

AutoUpgrade handles the Pre-check, Upgrade, and Post-upgrade phases.

AUDIT_UNIFIED_POLICIES shows the policies defined in the database.

You can use a login trigger to check the program name (e.g., 'sqlplus.exe') and reject connections.

The sqlnet.ora file contains the WALLET_LOCATION parameter that must be updated.

The number of objects, the amount of data, and system resources all impact performance.

Checking the log files and querying the dictionary version are standard verification methods.

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

ADMINISTER KEY MANAGEMENT SET KEY IDENTIFIED BY 'password' WITH BACKUP rotates the master key, which is a metadata-only operation for TDE tablespaces.

The PASSWORD_VERIFY_FUNCTION clause in the CREATE PROFILE statement allows for custom verification logic.

Ensuring the binaries and the data dictionary match the desired target version.

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

TCPS (TCP with SSL/TLS) is required for encrypted listener communication.

The 'NOAUDIT POLICY' command is used to disable a policy.

The AUDIT_ADMIN role is required for managing unified audit policies and data.

Unified and traditional audit trails can both be active, though it is not recommended.

Unified auditing is enabled by default in some configurations and is the replacement for standard auditing.

A physical standby database is required to perform a rolling upgrade using transient logical standby or switchover methods.

In a rolling upgrade, the standby instance is patched first, then a switchover is performed, and finally the former primary is patched.

The AutoUpgrade .cfg file uses the 'target_home' parameter.

A Unified Audit Policy for system events or actions is used.

Setting the location, creating the wallet, and opening the wallet are the required steps.

The keystore, the master key, and the database instance itself are the components.

Standard and Unified auditing are the two primary types.