nerdexam
Oracle

1Z0-060 · Question #166

You enabled an audit policy by issuing the following statements: SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SCOTT; SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SYS, SYSTEM; For which database users…

The correct answer is B. SYS and SYSTEM, but not SCOTT F. Both successful and failed executions. Issuing a second AUDIT POLICY statement for the same policy with a new BY clause replaces the prior user list, and without a WHENEVER clause Oracle audits both successful and failed executions by default.

New Features for Security

Question

You enabled an audit policy by issuing the following statements:

SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SCOTT; SQL> AUDIT POLICY ORA_DATABASE_PARAMETER BY SYS, SYSTEM; For which database users and for which executions is the audit policy now active? (Choose two.)

Options

  • ASCOTT, SYS and SYSTEM
  • BSYS and SYSTEM, but not SCOTT
  • CSCOTT, but not SYS and SYSTEM
  • DOnly for successful executions
  • EOnly for failed executions
  • FBoth successful and failed executions

How the community answered

(39 responses)
  • A
    10% (4)
  • B
    82% (32)
  • D
    3% (1)
  • E
    5% (2)

Why each option

Issuing a second AUDIT POLICY statement for the same policy with a new BY clause replaces the prior user list, and without a WHENEVER clause Oracle audits both successful and failed executions by default.

ASCOTT, SYS and SYSTEM

SCOTT is no longer audited because the second AUDIT POLICY BY SYS, SYSTEM statement replaced the original BY SCOTT clause, removing SCOTT from the active audit configuration.

BSYS and SYSTEM, but not SCOTTCorrect

In Oracle unified auditing, when AUDIT POLICY is issued a second time for the same policy with a new BY clause, it supersedes the previous BY clause; the initial statement auditing SCOTT is replaced by the second statement specifying SYS and SYSTEM, so only those two users remain active for that policy.

CSCOTT, but not SYS and SYSTEM

The second AUDIT POLICY statement superseded the first, so SCOTT is excluded from auditing and only SYS and SYSTEM are active.

DOnly for successful executions

Oracle unified auditing does not restrict coverage to successful executions only unless WHENEVER SUCCESSFUL is explicitly specified in the AUDIT statement.

EOnly for failed executions

Oracle unified auditing does not restrict coverage to failed executions only unless WHENEVER NOT SUCCESSFUL is explicitly specified in the AUDIT statement.

FBoth successful and failed executionsCorrect

When an AUDIT POLICY statement omits the WHENEVER SUCCESSFUL or WHENEVER NOT SUCCESSFUL clause, Oracle unified auditing defaults to capturing both successful and failed executions for the specified users.

Concept tested: Oracle unified audit policy user scope and default execution coverage

Source: https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dbseg/configuring-audit-policies.html

Topics

#unified auditing#audit policy#ORA_DATABASE_PARAMETER#user-specific auditing

Community Discussion

No community discussion yet for this question.

Full 1Z0-060 Practice