최신Oracle9i program with pl/sql - 1Z0-147무료샘플문제

A. To guarantee that when a specific operation is performed, related actions are performed.

B. For centralized, global operations that should be fired for the triggering statement, regardless of which user or application issues the statement.

C. To duplicate the functionality of other triggers.

D. To replicate built-in constraints in the Oracle server such as primary key and foreign key.

A. When referencing a package procedure or function from a stand-alone procedure or function, if the package specification changes, the package body remains valid but the stand-alone procedure becomes invalid

B. When referencing a package procedure or function from a stand-alone procedure or function, If the package specification changes, the stand-alone procedure referencing a package construct as well as the package body become invalid

C. When referencing a package procedure or function from a stand-alone procedure or function, if the package body changes and the package specification does not change, the stand-alone procedure referencing a package construct remains valid.

D. When referencing a package procedure or function from a stand-alone procedure or function, if the package body changes and the package specification does not change, the stand-alone procedure referencing a package construct becomes invalid

A. A comma has been left after the STATS_EXIST_EXCEPTION exception.

B. The STATS_EXIST_EXCEPTION has not been declared as an exception.

C. The STATS_EXIST_EXCEPTION has not been declared as a number.

D. Only predefined exceptions are allowed in the EXCEPTION section.

A. DEPTREE

B. IDEPTREE

C. I_DEPT_TREE

D. INDENT_TREE

A. A database trigger is a PL/SQL block, C, or Java procedure associated with a table, view, schema, or the database.

B. A database trigger needs to be executed explicitly whenever a particular event takes place.

C. A database trigger executes implicitly whenever a particular event takes place.

D. With a schema, triggers fire for each event for all users; with a database, triggers fire for each event for that specific user.

E. A database trigger fires whenever a data event (such as DML) or system event (such as logon, shutdown) occurs on a schema or database.

A. FOR EACH ROW trigger on the AUDIT_TABLE table.

B. Statement-level trigger on the EMP table.

C. FOR EACH ROW trigger on the EMP table.

D. Statement-level trigger on the AUDIT_TABLE table.

E. FOR EACH ROW statement-level trigger on the EMPtable.

A. SELECT * FROM USER DEPENDENCIES WHERE REFERENCED_NAME = 'TABLE';

B. SELECT * FROM USER_DEPENDENCIES WHERE REFERENCED_NAME = 'PLAYER';

C. SELECT * FROM USER DEPENDENCIES WHERE REFERENCED_NAME = 'ADD_PLAYER';

D. SELECT * FROM USER_DEPENDENCIES WHERE TYPE = 'DIR';

A. It persists from user to user when the package is invoked.

B. It does not persist from session to session for the same user.

C. It persists from session to session for the same user.

D. It does not persist across transaction within a session.

E. It persists across transactions within a session.