1Z0-060 Exam Questions and Answers | Exam-Dumps.net (Page: 7)

QUESTION: 31

Which two are true concerning a multitenant container database with three pluggable database?

All administration tasks must be done to a specific pluggable database.
The pluggable databases increase patching time.
The pluggable databases reduce administration effort.
The pluggable databases are patched together.
Pluggable databases are only used for database consolidation.

Answer(s): C,E

Explanation:

The benefits of Oracle Multitenant are brought by implementing a pure deployment choice. The following list calls out the most compelling examples.
* High consolidation density. (E)
The many pluggable databases in a single multitenant container database share its memory and background processes, letting you operate many more pluggable databases on a particular platform than you can single databases that use the old architecture. This is the same benefit that schema-based consolidation brings.
* Rapid provisioning and cloning using SQL.
* New paradigms for rapid patching and upgrades. (D, not B)
The investment of time and effort to patch one multitenant container database results in patching all of its many pluggable databases. To patch a single pluggable database, you simply unplug/plug to a multitenant container database at a different Oracle Database software version.
* (C, not A) Manage many databases as one.
By consolidating existing databases as pluggable databases, administrators can manage many databases as one. For example, tasks like backup and disaster recovery are performed at the multitenant container database level.
* Dynamic between pluggable database resource management. In Oracle Database 12c, Resource Manager is extended with specific functionality to control the competition for resources between the pluggable databases within a multitenant container database.
Note:
* Oracle Multitenant is a new option for Oracle Database 12c Enterprise Edition that helps customers reduce IT costs by simplifying consolidation, provisioning, upgrades, and more. It is supported by a new architecture that allows a multitenant container database to hold many pluggable databases. And it fully complements other options, including Oracle Real Application Clusters and Oracle Active Data Guard. An existing database can be simply adopted, with no change, as a pluggable database; and no changes are needed in the other tiers of the application.

Reveal Solution Next Question

QUESTION: 32

Examine the current values for the following parameters in your database instance:

SGA_MAX_SIZE = 1024M
SGA_TARGET = 700M
DB_8K_CACHE_SIZE = 124M
LOG_BUFFER = 200M

You issue the following command to increase the value of DB_8K_CACHE_SIZE: SQL> ALTER SYSTEM SET DB_8K_CACHE_SIZE=140M;

Which statement is true?

It fails because the DB_8K_CACHE_SIZE parameter cannot be changed dynamically.
It succeeds only if memory is available from the autotuned components if SGA.
It fails because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_TARGET.
It fails because an increase in DB_8K_CACHE_SIZE cannot be accommodated within SGA_MAX_SIZE.

Answer(s): B

Reveal Solution Next Question

QUESTION: 33

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

The PDB must be open in read only mode.
The PDB must be closed.
The unplugged PDB becomes a non-CDB.
The unplugged PDB can be plugged into the same multitenant container database (CDB)
The unplugged PDB can be plugged into another CDB.
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.

Reveal Solution Next Question

QUESTION: 34

Examine this command:

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

The %ROWTYPE attribute declarations in PL/SQL to access a row will not display the invisible column in the output.
The DESCRIBE commands in SQL *Plus will not display the invisible column in the output.
Referential integrity constraint cannot be set on the invisible column.
The invisible column cannot be made visible and can only be marked as unused.
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.

Reveal Solution Next Question

QUESTION: 35

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?

All users except SYS
All users except SCOTT
All users except SYS and SCOTT
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;

Reveal Solution Next Question

Oracle 1Z0-060 Exam (page: 7) Oracle Upgrade to Database 12c Updated on: 01-Sep-2025

QUESTION: 31

Explanation:

QUESTION: 32

QUESTION: 33

Explanation:

QUESTION: 34

Explanation:

QUESTION: 35

Explanation:

Oracle 1Z0-060 Exam (page: 7)
Oracle Upgrade to Database 12c
Updated on: 01-Sep-2025