Examine this statement and its result: You issue this statement and then restart the database instance: Which Is true about generated audit records?

Question

Options

• AThey now Include all application context attribute values.
• BThey are now written to XML files as well as the database.
• CThey now Include SQL statements and any bind variables.
• DInformation is now populated in auds .commentstext.

• A
  79% (19)
• B
  4% (1)
• C
  4% (1)
• D
  13% (3)

Explanation

Option A is correct because when you configure a unified audit policy to include application context attributes (via the CONTEXT clause or an ADD ATTRIBUTE command) and restart the database instance, Oracle begins populating audit records with the values of those application context namespace attributes - data that was not captured before the configuration change and restart took effect.

Why the distractors are wrong:

• B is wrong because Oracle Unified Auditing writes to the AUDSYS schema (database) or OS/syslog files - not XML files; XML is not a native Oracle audit trail format for this feature.
• C is wrong because capturing bind variables requires a separate, explicit configuration (such as Fine-Grained Auditing with bind variable capture enabled); simply restarting after this type of policy change does not automatically add bind variable logging.
• D is wrong because AUDS$.COMMENTSTEXT is not a standard or relevant column affected by this configuration; this is a fabricated or misattributed detail designed to mislead.

Memory tip: Associate "application Context" with "Capturing attribute values" - whenever a question ties an audit policy change + restart to what's newly included in audit records, think context attributes going live after the restart.

No community discussion yet for this question.