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.
Explanation:
https://books.google.com.pk/books?id=TD5eibhYyd8C&pg=PA236&lpg=PA236&dq=oracle+auditing+keep+track+of+both+the+old+data+and+new+data+in+the+table+long+with+the+user
+information&source=bl&ots=buMRdjIEkm&sig=tHCTXUPVSd1eFJZFcr2lkEifvo&hl=en&sa=X&redir_esc=y#v=onepage&q=oracle%20auditing%20keep%20track%
20of%20both%20the%20old%20data%20and%20new%20data%20in%20the%20table%20long%20with%20the
%20user%20information&f=false
B I guess
B
value-based auditing is not auditing but just a trigger. Fine-grained auditing is the correct answer