Unified auditing is enabled in your database. The HR_ADMIN and OE_ADMIN roles exist and are granted system privileges. You execute the command: SQL>CREATE AUDIT POLICY table_aud PRIVILEGES CREATE…

Question

Options

• AIt succeeds and needs to be enabled to capture all SQL statements that require either the
• BIt fails because the command does notspecify when the unified audit policy should be
• CIt succeeds and starts capturing only successful SQL statements for all users who have either
• DIt fails because system privileges cannot be granted with roles in the same audit policy.

• A
  81% (21)
• B
  4% (1)
• C
  4% (1)
• D
  12% (3)

Explanation

Option A is correct because CREATE AUDIT POLICY only defines the policy - it does not activate it. A separate AUDIT POLICY table_aud; statement is required to enable it. Once enabled, unified audit policies capture both successful and failed statements by default, for all users who hold the audited privileges either directly or through the listed roles.

B is wrong because CREATE AUDIT POLICY does not require a WHEN clause - timing/activation is handled by the separate AUDIT POLICY enable command, not the creation syntax.

C is wrong on two counts: the policy isn't capturing anything yet (not enabled), and when it is enabled, unified auditing records all executions - successful and unsuccessful - not just successful ones.

D is wrong because Oracle unified auditing explicitly supports mixing system privileges and roles in the same policy; that is a feature, not a restriction.

Memory tip: Think of it as two steps - CREATE = define the rule, AUDIT = turn it on. If a question says a policy was just created, it's always dormant until explicitly enabled.

No community discussion yet for this question.