โ† All 1Z0-082 Flashcard Decks

Oracle Database Monitoring and Auditing Flashcards

6 cards from real 1Z0-082 practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 6 Oracle Database Monitoring and Auditing flashcards as text
  1. Which Oracle auditing feature allows policies to audit specific rows based on column values, such as auditing access to salary data over $100,000?

    Answer: Fine-Grained Auditing (FGA)

    Fine-Grained Auditing (FGA) allows administrators to create policies that trigger audit records only when specific column values or conditions are met in a query.

  2. Which initialization parameter must be set to enable traditional (non-unified) database auditing in Oracle?

    Answer: AUDIT_TRAIL

    The AUDIT_TRAIL parameter controls whether auditing is enabled and where audit records are stored, with values such as DB, OS, XML, or NONE.

  3. When AUDIT_TRAIL is set to DB, where are standard audit records stored?

    Answer: In the SYS.AUD$ table in the database

    When AUDIT_TRAIL=DB, Oracle writes audit records to the SYS.AUD$ table, which is accessible through the DBA_AUDIT_TRAIL data dictionary view.

  4. Which data dictionary view shows audit records for DDL and DML operations performed by database users?

    Answer: DBA_AUDIT_TRAIL

    DBA_AUDIT_TRAIL is a view over SYS.AUD$ that shows all standard audit trail entries including the user, action, object, and timestamp.

  5. What is Unified Auditing introduced in Oracle 12c?

    Answer: A single consolidated audit framework that replaces all previous auditing methods with one policy-based system

    Unified Auditing consolidates standard auditing, FGA, SYS auditing, and RMAN auditing into a single framework stored in AUDSYS.AUD$UNIFIED and managed via audit policies.

  6. Which SQL statement enables auditing of SELECT operations on the HR.EMPLOYEES table for all users?

    Answer: AUDIT SELECT ON hr.employees BY ACCESS

    The AUDIT statement with the SELECT action and object name enables auditing of SELECT operations on a specific table, optionally specifying BY ACCESS or BY SESSION.