1Z0-062 · Question #134
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…
The correct answer is B. Implement value-based auditing. Value-based auditing uses database triggers to capture both the old and new values of changed data along with the user and timing information, which no other standard auditing method provides.
Question
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?
Options
- AApply fine-grained auditing.
- BImplement value-based auditing.
- CImpose standard database auditing to audit object privileges.
- DImpose standard database auditing to audit SQL statements.
How the community answered
(21 responses)- A5% (1)
- B76% (16)
- C14% (3)
- D5% (1)
Why each option
Value-based auditing uses database triggers to capture both the old and new values of changed data along with the user and timing information, which no other standard auditing method provides.
Fine-grained auditing (FGA) records who accessed or modified data and under what conditions, but it does not capture the old and new data values of the rows affected.
Value-based auditing is implemented using DML triggers (BEFORE or AFTER row-level triggers) that write both the old (:OLD) and new (:NEW) column values to a custom audit table, together with the user identity and timestamp. This approach captures the actual data content of changes, which is not possible with standard or fine-grained auditing alone.
Standard database auditing of object privileges records the action and the user but does not store the before and after data values involved in the DML operation.
Standard database auditing of SQL statements records statement execution metadata such as username and timestamp but does not capture the actual row data that was modified.
Concept tested: Value-based auditing using triggers to capture DML data changes
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/introduction-to-auditing.html
Topics
Community Discussion
No community discussion yet for this question.