Examine this list: 1. You must monitor access to email column or salary column In the employees table. 2. If any activity is detected, the action must be audited and a notification sent out by…

Question

Exhibit

Options

• AThe query will be executed, an entry will be created in the unified audit trail, and the mail will be
• BThe query will be executed, an entry will be created In FGA_LOG$ table, and the mall will be sent.
• CThe query will be executed, but no audit entry will be created nor any mail sent.
• DThe query will be executed, no audit entry will be created but the mall will be sent.

• A
  12% (3)
• B
  31% (8)
• C
  50% (13)
• D
  8% (2)

Explanation

Option C is correct because in Oracle Unified Auditing, CREATE AUDIT POLICY only defines the policy - it does not activate it. To start capturing audit events, you must separately execute AUDIT POLICY <policy_name>;. Since the question states only that the policy was "created," it was never enabled, so the SELECT executes normally but generates no audit trail entry and triggers no email handler.

Why the distractors fail:

• A is wrong because even if the policy were enabled, standard Unified Audit Policies do not support column-level handler_module callbacks - that feature belongs to Fine-Grained Auditing (DBMS_FGA.ADD_POLICY), which is a separate mechanism.
• B is wrong because FGA_LOG$ is the backing table for traditional/mixed-mode FGA, not for Unified Auditing; with Unified Auditing enabled, records go to the unified audit trail (UNIFIED_AUDIT_TRAIL), not FGA_LOG$.
• D is wrong because the email procedure is triggered by the FGA handler, which only fires when an audit event is actually captured - no audit entry means no handler invocation and no email.

Memory tip: Think of it as a two-step switch: CREATE AUDIT POLICY = install the switch, AUDIT POLICY = flip the switch. If you never flip it, nothing happens - a common Oracle exam trap distinguishing policy creation from policy enablement.

No community discussion yet for this question.