In your production database, data manipulation language (DML) operations are executed on the
SALES table. You have noticed some dubious values in the SALES table during the last few days. You
are able to track users, actions taken, and the time of the action for this particular period but the
changes in data are not tracked. You decide to keep track of both the old data and new data in the
table long with the user information. What action would you take to achieve this task?
A.
Apply fine-grained auditing.
B.
Implement value-based auditing.
C.
Impose standard database auditing to audit object privileges.
D.
Impose standard database auditing to audit SQL statements.
When a user inserts, updates, or deletes data from a table with the appropriate trigger attached, the trigger works in the background to copy audit information to a table that is designed to contain the audit information.
Value-based auditing – its audit trigger code must be executed each time the insert, update, or delete operation occurs.
When a user is connected to the corresponding trigger table, insert, update, or delete data, triggers the background copy information to the audit table contains audit information.
Because the audit trigger code in each insert, update, or delete operation must be performed, so when using value-based audit, performance decline is relatively large.
Performance decrease depends on the efficiency of the trigger code. Only in the case of insufficient information captured by standard database audit, the audit was based values.
Based on the value of the audit carried out by the user or third-party code.
Oracle DB provides can be used to build PL / SQL construct a value system based on the audit.
A key part of the audit is based on the value of audit trigger, which is a simple to capture auditing information constructed in PL / SQL triggers.
Value-based auditing extends database auditing by capturing the actual values that are changed. Value-based auditing leverages database triggers (event-driven PL/SQL constructs).