q. 1 : what feature in oracle allows you to monitor suspicious activity on the datbase
　　
　　1. replication
　　2. auditing
　　3. monitoring
　　4. tuning
　　
　　q. 2 : auditing can be turned on by setting this parameter
　　
　　1. db_audit_trail
　　2. audit_trail
　　3. audit_db
　　4. none of the above
　　　
　　q. 3 : what are the valid values for audit_trail parameter
　　
　　1. db
　　2. os
　　3. none
　　4. all of the above
　　
　　q. 4 : where are the records stored if the following value is set in the parameter file. "audit_trail=db"
　　
　　1. database
　　2. operating system file
　　3. tape
　　4. none of the above
　　
　　q. 5 : where is the audit information written to when the audit_trail parameter is set to none
　　
　　1. parameter file
　　2. redo log
　　3. os file
　　4. audit trail is not turned on
　　
　　q. 6 : which data dictionary object holds the information about audit codes and their associated names
　　
　　1. audit_info
　　2. dba_audit_info
　　3. audit_actions
　　4. none of the above 　
　　
　　q. 7 : audit data is stored in
　　
　　1. sys.x$audit
　　2. sys.v$aud
　　3. sys.aud$
　　4. none of the above
　　
　　q. 8 : instance startup audit records are placed in
　　
　　1. alert.log
　　2. user.trc
　　3. audit_file_dest
　　4. audit_rec_dest
　　
　　q. 9 : the db is running with session audit and the audit table is full. what happens to new sessions
　　
　　1. nothing, they are not audited
　　2. new connections are not allowed
　　3. session allowed, with audit record to alert.log
　　4. none of the abvoe
　　
　　q. 10 : after audit_trail is set to none, the audit trail is disabled by
　　
　　1. restarting the database
　　2. disabling restricted mode
　　3. grant audit_trail to public
　　4. none of the above
　　　
　　answer:

　　1=>2,
　　2=>2,
　　3=>4,
　　4=>1,
　　5=>4,
　　6=>3,
　　7=>3,
　　8=>3,
　　9=>2,
　　10=>1,