It is more faster and easier to pass the Oracle 1Z0-062 exam by using High quality Oracle Oracle Database 12c: Installation and Administration questuins and answers. Immediate access to the Up to the minute 1Z0-062 Exam and find the same core area 1Z0-062 questions with professionally verified answers, then PASS your exam with a high score now.
2021 Dec 1Z0-062 rapidshare
Q51. You run a script that completes successfully using SQL*Plus that performs these actions:
1. Creates a multitenant container database (CDB)
2. Plugs in three pluggable databases (PDBs)
3. Shuts down the CDB instance
4. Starts up the CDB instance using STARTUP OPEN READ WRITE
Which two statements are true about the outcome after running the script?
A. The seed will be in mount state.
B. The seed will be opened read-only.
C. The seed will be opened read/write.
D. The other PDBs will be in mount state.
E. The other PDBs will be opened read-only.
F. The PDBs will be opened read/write.
Explanation: B: The seed is always read-only.
D: Pluggable databases can be started and stopped using SQL*Plus commands or the ALTER PLUGGABLE DATABASE command.
Q52. The ORCL database is configured to support shared server mode. You want to ensure that a user connecting remotely to the database instance has a one-to-one ratio between client and server processes.
Which connection method guarantees that this requirement is met?
A. connecting by using an external naming method
B. connecting by using the easy connect method
C. creating a service in the database by using the dbms_service.create_service procedure and using this service for creating a local naming service"
D. connecting by using the local naming method with the server = dedicated parameter set in the tnsnames.ora file for the net service
E. connecting by using a directory naming method
Q53. Oracle Grid Infrastructure for a stand-alone server is installed on your production host before installing the Oracle Database server. The database and listener are configured by using Oracle Restart.
Examine the following command and its output:
$ crsctl config has
CRS-4622: Oracle High Availability Services auto start is enabled.
What does this imply?
A. When you start an instance on a high with SQL *Plus dependent listeners and ASM disk groups are automatically started.
B. When a database instance is started by using the SRVCTL utility and listener startup fails, the instance is still started.
C. When a database is created by using SQL* Plus, it is automatically added to the Oracle Restart configuration.
D. When you create a database service by modifying the SERVICE_NAMES initialization parameter, it is automatically added to the Oracle Restart configuration.
Explanation: About Startup Dependencies Oracle Restart ensures that Oracle components are started in the proper order, in accordance with component dependencies. For example, if database files are stored in Oracle ASM disk groups, then before starting the database instance, Oracle Restart ensures that the Oracle ASM instance is started and the required disk groups are mounted. Likewise, if a component must be shut down, Oracle Restart ensures that dependent components are cleanly shut down first. Oracle Restart also manages the weak dependency between database instances and the Oracle Net listener (the listener): When a database instance is started, Oracle Restart attempts to start the listener. If the listener startup fails, then the database is still started. If the listener later fails, Oracle Restart does not shut down and restart any database instances.
Q54. In your production database, data manipulation language (DML) operations are executed on the SALES table.
You have noticed some dubious values in the SALES table during the last few days. You are able to track users, actions taken, and the time of the action for this particular period but the changes in data are not tracked. You decide to keep track of both the old data and new data in the table long with the user information.
What action would you take to achieve this task?
A. Apply fine-grained auditing.
B. Implement value-based auditing.
C. Impose standard database auditing to audit object privileges.
D. Impose standard database auditing to audit SQL statements.
Q55. The hr user receiver, the following error while inserting data into the sales table:
ERROR at line 1:
ORA-01653; unable to extend table HR.SALES by 128 in tablespace USERS
On investigation, you find that the users tablespace uses Automnrif Segment Space Management (ASSM). It is the default tablespace for the HR user with an unlimited quota on it.
Which two methods would you use to resolve this error?
A. Altering the data life associated with the USERS tablespace to ex automatically
B. Adding a data life to the USERS tablespace
C. Changing segment space management for the USERS tablespace to manual
D. Creating a new tablespace with autoextend enabled and changing the default tablespace of the HR user to the new tablespace
E. Enabling resumable space allocation by setting the RESUMABLE_TIMEOUT parameter to a nonzero value
Most up-to-date 1Z0-062 test questions:
Q56. Which three statements are true concerning the multitenant architecture?
A. Each pluggable database (PDB) has its own set of background processes.
B. A PDB can have a private temp tablespace.
C. PDBs can share the sysaux tablespace.
D. Log switches occur only at the multitenant container database (CDB) level.
E. Different PDBs can have different default block sizes.
F. PDBs share a common system tablespace.
G. Instance recovery is always performed at the CDB level.
* A PDB would have its SYSTEM, SYSAUX, TEMP tablespaces.It can also contains other
user created tablespaces in it.
* There is one default temporary tablespace for the entire CDB. However, you can create additional temporary tablespaces in individual PDBs.
* There is a single redo log and a single control file for an entire CDB
* A log switch is the point at which the database stops writing to one redo log file and begins writing to another. Normally, a log switch occurs when the current redo log file is completely filled and writing must continue to the next redo log file.
G: instance recovery The automatic application of redo log records to uncommitted data blocks when an database instance is restarted after a failure.
Incorrect: Not A:
* There is one set of background processes shared by the root and all PDBs. –
* High consolidation density. The many pluggable databases in a single 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.
Not C: There is a separate SYSAUX tablespace for the root and for each PDB.
Not F: There is a separate SYSTEM tablespace for the root and for each PDB. -
Q57. You find this query being used in your Oracle 12c database:
Which method a used by the optimizer to limit the rows being returned?
A. A filter is added to the table query dynamically using ROWNUM to limit the rows to 20 percent of the total rows
B. All the rows are returned to the client or middle tier but only the first 20 percent are returned to the screen or the application.
C. A view is created during execution and a filter on the view limits the rows to 20 percent of the total rows.
D. A TOP-N query is created to limit the rows to 20 percent of the total rows
Q58. You execute the following commands to audit database activities:
SQL > ALTER SYSTEM SET AUDIT_TRIAL=DB, EXTENDED SCOPE=SPFILE;
SQL > AUDIT SELECT TABLE, INSERT TABLE, DELETE TABLE BY JOHN By SESSION WHENEVER SUCCESSFUL;
Which statement is true about the audit record that generated when auditing after instance restarts?
A. One audit record is created for every successful execution of a SELECT, INSERT OR DELETE command on a table, and contains the SQL text for the SQL Statements.
B. One audit record is created for every successful execution of a SELECT, INSERT OR DELETE command, and contains the execution plan for the SQL statements.
C. One audit record is created for the whole session if john successfully executes a SELECT, INSERT, or DELETE command, and contains the execution plan for the SQL statements.
D. One audit record is created for the whole session if JOHN successfully executes a select command, and contains the SQL text and bind variables used.
E. One audit record is created for the whole session if john successfully executes a SELECT, INSERT, or DELETE command on a table, and contains the execution plan, SQL text, and bind variables used.
* BY SESSION
In earlier releases, BY SESSION caused the database to write a single record for all SQL statements or operations of the same type executed on the same schema objects in the same session. Beginning with this release (11g) of Oracle Database, both BY SESSION and BY ACCESS cause Oracle Database to write one audit record for each audited statement and operation.
* BY ACCESS
Specify BY ACCESS if you want Oracle Database to write one record for each audited statement and operation.
If you specify either a SQL statement shortcut or a system privilege that audits a data definition language (DDL) statement, then the database always audits by access. In all other cases, the database honors the BY SESSION or BY ACCESS specification.
* For each audited operation, Oracle Database produces an audit record containing this information: / The user performing the operation / The type of operation / The object involved in the operation / The date and time of the operation
Reference: Oracle Database SQL Language Reference 12c
Q59. After implementing full Oracle Data Redaction, you change the default value for the NUMBER data type as follows:
After changing the value, you notice that FULL redaction continues to redact numeric data with zero.
What must you do to activate the new default value for numeric full redaction?
A. Re-enable redaction policies that use FULL data redaction.
B. Re-create redaction policies that use FULL data redaction.
C. Re-connect the sessions that access objects with redaction policies defined on them.
D. Flush the shared pool.
E. Restart the database instance.
Explanation: About Altering the Default Full Data Redaction Value You can alter the default displayed values for full Data Redaction polices. By default, 0 is the redacted value when Oracle Database performs full redaction (DBMS_REDACT.FULL) on a column of the NUMBER data type. If you want to change it to another value (for example, 7), then you can run the DBMS_REDACT.UPDATE_FULL_REDACTION_VALUES procedure to modify this value. The modification applies to all of the Data Redaction policies in the current database instance. After you modify a value, you must restart the database for it to take effect.
* The DBMS_REDACT package provides an interface to Oracle Data Redaction, which enables you to mask (redact) data that is returned from queries issued by low-privileged users or an application.
* UPDATE_FULL_REDACTION_VALUES Procedure
This procedure modifies the default displayed values for a Data Redaction policy for full redaction.
* After you create the Data Redaction policy, it is automatically enabled and ready to redact data.
* Oracle Data Redaction enables you to mask (redact) data that is returned from queries issued by low-privileged users or applications. You can redact column data by using one of the following methods:
/ Full redaction. / Partial redaction. / Regular expressions. / Random redaction. / No redaction.
Reference: Oracle Database Advanced Security Guide 12c, About Altering the Default Full Data Redaction Value
Q60. Identify two situations in which the alert log file is updated.
A. Running a query on a table returns ORA-600: Internal Error.
B. Inserting a value into a table returns ORA-01722: invalid number.
C. Creating a table returns ORA-00955: name us already in used by an existing objects.
D. Inserting a value into a table returns ORA-00001: unique constraint (SYS.OK_TECHP) violated.
E. Rebuilding an index using ALTER INDEX . . . REBUILD fails with an ORA-01578: ORACLE data block corrupted (file # 14, block # 50) error.
Explanation: The alert log is a chronological log of messages and errors, and includes the following items:
*All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock errors (ORA-60) that occur
* Administrative operations, such as CREATE, ALTER, and DROP statements and STARTUP, SHUTDOWN, and ARCHIVELOG statements
* Messages and errors relating to the functions of shared server and dispatcher processes
* Errors occurring during the automatic refresh of a materialized view
* The values of all initialization parameters that had nondefault values at the time the database and instance start
* The alert log file (also referred to as the ALERT.LOG) is a chronological log of messages and errors written out by an Oracle Database. Typical messages found in this file is: database startup, shutdown, log switches, space errors, etc. This file should constantly be monitored to detect unexpected messages and corruptions.