READ Free Dumps For Oracle- 1z0-060
| Question ID 20785 | Examine the following command:
CREATE TABLE (prod_id number(4),
Real 27
Oracle 1z0-060 Exam
Prod_name varchar2 (20),
Category_id number(30),
Quantity_on_hand number (3) INVISIBLE);
Which three statements are true about using an invisible column in the PRODUCTS table?
|
| Option A | The %ROWTYPE attribute declarations in PL/SQL to access a row will not display the invisible column in the output.
|
| Option B | The DESCRIBE commands in SQL *Plus will not display the invisible column in the output.
|
| Option C | Referential integrity constraint cannot be set on the invisible column.
|
| Option D | The invisible column cannot be made visible and can only be marked as unused.
|
| Option E | A primary key constraint can be added on the invisible column.
|
| Correct Answer | A,B,E |
Explanation AB: You can make individual table columns invisible. Any generic access of a table does not show the invisible columns in the table. For example, the following operations do not display invisible columns in the output: * SELECT * FROM statements in SQL * DESCRIBE commands in SQL*Plus * %ROWTYPE attribute declarations in PL/SQL * Describes in Oracle Call Interface (OCI) Incorrect: Not D: You can make invisible columns visible. You can make a column invisible during table creation or when you add a column to a table, and you can later alter the table to make the same column visible. Reference: Understand Invisible Columns
| Question ID 20786 | You wish to enable an audit policy for all database users, except SYS, SYSTEM, and SCOTT.
You issue the following statements:
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYS;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYSTEM;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SCOTT;
For which database users is the audit policy now active?
|
| Option A | All users except SYS
|
| Option B | All users except SCOTT
|
| Option C | All users except sys and SCOTT
|
| Option D | All users except sys, system, and SCOTT
|
| Correct Answer | B |
Explanation If you run multiple AUDIT statements on the same unified audit policy but specify different EXCEPT users, then Oracle Database uses the last exception user list, not any of the users from the preceding lists. This means the effect of the earlier AUDIT POLICY ... EXCEPT statements are overridden by the latest AUDIT POLICY ... EXCEPT statement. Note: * The ORA_DATABASE_PARAMETER policy audits commonly used Oracle Database parameter settings. By default, this policy is not enabled. * You can use the keyword ALL to audit all actions. The following example shows how to audit all actions on the HR.EMPLOYEES table, except actions by user pmulligan. Example Auditing All Actions on a Table CREATE AUDIT POLICY all_actions_on_hr_emp_pol ACTIONS ALL ON HR.EMPLOYEES; AUDIT POLICY all_actions_on_hr_emp_pol EXCEPT pmulligan; Reference: Oracle Database Security Guide 12c, About Enabling Unified Audit Policies