1 : what feature in oracle allows you to monitor suspicious activity on the datbase
- X$ r: D% u$ t9 |) U& |0 i8 A
1 X$ G6 A% v4 Y: `# z( B 1. replication * ]' P& ?# L" b- s/ ^' R% y: c# V
2. auditing
/ V1 S3 Y; S \6 K7 @% R0 l; I 3. monitoring
/ m- Q+ I' w& E' N. |7 K { 4. tuning ' |; [) {/ R4 g
4 X: \: U' Z; s$ s* L
q. 2 : auditing can be turned on by setting this parameter ) ^+ i* R/ S. J `$ |, A6 U1 o
3 l* A P( G8 ?4 G/ r Y
1. db_audit_trail
; P, |! L( _ X0 T9 H) b0 C1 z 2. audit_trail - `2 U5 V) R" `7 s( H R
3. audit_db
v6 G: L: k& Y' w; j 4. none of the above
3 O; V5 p% v! F
5 O0 e/ B# A# B: @$ Y4 [ q. 3 : what are the valid values for audit_trail parameter - w8 N0 S3 \# j# ?: [
. f. R. b2 D5 P4 P
1. db
2 g; p7 m; T) b8 `* T7 u9 b 2. os
. P. B( X/ D0 Y+ g4 Z! v 3. none
& w/ {. ?) x4 b$ J: b; I 4. all of the above
& e9 u" ?; q) I% u6 Z 0 |; p- r K# |# W- N
q. 4 : where are the records stored if the following value is set in the parameter file. "audit_trail=db" $ Q6 q s- x3 n6 x$ w( j1 p9 ]
; T* l5 l6 M1 L! O$ q; {. g
1. database
9 {1 R( S: D; X6 }; _) }$ ` 2. operating system file ' j' o6 i# \+ }% \
3. tape # V# P. _5 J% u! F
4. none of the above 8 t9 r' D+ B/ m. n. S, `
- t, h7 s( v& q% v
q. 5 : where is the audit information written to when the audit_trail parameter is set to none 7 J8 p h6 s# [. ] f/ j+ j+ h
' t* k- p8 v! [# u) l6 o3 b7 e
1. parameter file
& M. S4 C, t4 }( K; n- P 2. redo log
1 o5 e; u. X8 O6 Y6 d. B6 J6 s- ? 3. os file 2 w3 d* E) {* l; w" i' W
4. audit trail is not turned on
0 h5 u: g9 I7 J ; s5 X1 w' O, F" b
q. 6 : which data dictionary object holds the information about audit codes and their associated names
3 N+ y* b( _5 l1 ?( f
. }/ q- [/ E' v' ]# ~* G/ K 1. audit_info 0 K- _% z2 }) D, }
2. dba_audit_info
2 W4 h9 T, m" m' g5 n 3. audit_actions + o( _( o% |2 e
4. none of the above ; \3 n" u& w0 J9 E1 Q& z2 O
4 X$ N4 t) Y, _
q. 7 : audit data is stored in
! D( {& w7 H7 H1 A% m( ] % r- \1 [, b! g1 z9 I. u
1. sys.x$audit 5 z m1 s8 q2 R) m% P( v
2. sys.v$aud ' F% c$ S/ k8 @, E! j6 L# [
3. sys.aud$
1 O+ r. [6 @6 _+ b 4. none of the above
# n1 ?# E9 K1 F5 R! S% n ; v0 P3 u; y) |. _/ s/ a
q. 8 : instance startup audit records are placed in
9 }& H/ K' A3 @' x
; W+ H0 w9 ^% v0 Y7 N! N" L4 c 1. alert.log
' j2 j. g8 ~* w 2. user.trc ; _: h$ F9 W2 X( k- C/ C
3. audit_file_dest
$ Y5 l) a( ]8 n; ^7 K0 c 4. audit_rec_dest
8 [ Z& B( k% S. u d
2 P" w* S1 x# ?& k, ^( I2 X q. 9 : the db is running with session audit and the audit table is full. what happens to new sessions
5 S! ]0 Y8 \) R
|, f0 q8 u; i9 g$ C; o5 C 1. nothing, they are not audited $ `9 {0 O7 e9 ~
2. new connections are not allowed
0 g' B6 u3 I& g$ y- L8 k2 y 3. session allowed, with audit record to alert.log
' s; f$ q/ B% _$ ? 4. none of the abvoe
( [# H r3 J+ J! L6 Y/ a: C
7 c% C( n0 c1 f- U; `) H! o2 q q. 10 : after audit_trail is set to none, the audit trail is disabled by ; w' S# ~8 J4 B7 A6 K
" ^3 e- x! o i+ I% n
1. restarting the database $ |6 B8 @6 h1 E
2. disabling restricted mode 4 |2 x& N4 W( m4 a) H: B, K1 l
3. grant audit_trail to public
4 k1 H) X) { {8 n) L d" n$ Y 4. none of the above
, Y/ }! p$ L- d6 E% t 5 ~, g2 T h! D6 h+ v
answer: - [' I1 ] _( x6 K' A( R! @# Z
$ a3 h) U) l3 s# K$ N
1=>2, 3 ?/ H1 j0 d9 V' n5 _/ A4 V' k
2=>2,
8 A5 y$ r, L' L% K 3=>4, ; P$ @ I- _3 x; s' l* T$ F
4=>1, $ y6 ^* x3 c7 @/ U! Q3 K( @# i& ^0 @6 q
5=>4,
- T2 F' N( e7 V: i6 P. u7 N2 b 6=>3, ) b c, H- M% K4 \+ J
7=>3,
" P) q; [1 w: ~2 }' \ 8=>3, . f' L5 [3 R6 [' Y
9=>2,
$ H7 u5 z4 E. l, V 10=>1, |
发表于 2012-8-4 14:01:27
