Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
All Vendors
  2. Home
  3. Exams
  4. Oracle
  5. 1Z0-060

Free Oracle 1Z0-060 Exam Braindumps

Which three statements are true concerning unplugging a pluggable database (PDB)?

  1. The PDB must be open in read only mode.
  2. The PDB must be closed.
  3. The unplugged PDB becomes a non-CDB.
  4. The unplugged PDB can be plugged into the same multitenant container database (CDB)
  5. The unplugged PDB can be plugged into another CDB.
  6. The PDB data files are automatically removed from disk.

Answer(s): B,D,E

Explanation:

D: An unplugged PDB contains data dictionary tables, and some of the columns in these encode information in an endianness-sensitive way. There is no supported way to handle the conversion of such columns automatically. This means, quite simply, that an unplugged PDB cannot be moved across an endianness difference.

E (not F): To exploit the new unplug/plug paradigm for patching the Oracle version most effectively, the source and destination CDBs should share a filesystem so that the PDB’s datafiles can remain in place.
The PDB must be closed before it can be unplugged. When you unplug a PDB from a CDB, the unplugged PDB is in mounted mode. The unplug operation makes some changes in the PDB's data files to record, for example, that the PDB was successfully unplugged. Because it is still part of the CDB, the unplugged PDB is included in an RMAN backup of the entire CDB. Such a backup provides a convenient way to archive the unplugged PDB in case it is needed in the future.



Examine this command:


Which three statements are true about using an invisible column in the PRODUCTS table?

  1. The %ROWTYPE attribute declarations in PL/SQL to access a row will not display the invisible column in the output.
  2. The DESCRIBE commands in SQL *Plus will not display the invisible column in the output.
  3. Referential integrity constraint cannot be set on the invisible column.
  4. The invisible column cannot be made visible and can only be marked as unused.
  5. A primary key constraint can be added on the invisible column.

Answer(s): 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 Answers:
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.



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?

  1. All users except SYS
  2. All users except SCOTT
  3. All users except SYS and SCOTT
  4. All users except SYS, SYSTEM, and SCOTT

Answer(s): 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;



On your Oracle 12c database, you invoked SQL*Loader to load data into the EMPLOYEES table in the HR schema by issuing the following command:

$> sqlldr hr/hr@pdb table=employees

Which two statements are true regarding the command? (Choose two.)

  1. It succeeds with default settings if the EMPLOYEES table belonging to HR is already defined in the database.
  2. It fails because no SQL *Loader data file location is specified.
  3. It fails if the HR user does not have the CREATE ANY DIRECTORY privilege.
  4. It fails because no SQL *Loader control file location is specified.

Answer(s): A,C

Explanation:

Note:
* SQL*Loader is invoked when you specify the sqlldr command and, optionally, parameters that establish session characteristics.



Viewing page 10 of 55
Viewing questions 37 - 40 out of 216 questions



Post your Comments and Discuss Oracle 1Z0-060 exam prep with other Community members:

1Z0-060 Exam Discussions & Posts