Oracle 1z0-068 Oracle Database 12c: RAC and Grid Infrastructure Administration Exam Practice Test

using Shared GNS for the leaf nodes and local GNS for the hub nodes in a Flex Cluster

using Shared GNS running on another cluster

using Shared GNS for the hub nodes and local GNS for the leaf nodes in a Flex Cluster

creation of a new GNS for this cluster

using DHCP to assign Node Virtual IP addresses for nodes in the cluster

Use cat /etc/oracle/ocr.loc to view the location of the OCR if stored in ASM.

Use ocrcheck command to view the location of the OCR only if stored in a file system.

Use crsctl querry css votedisk to view the location of voting files if stored in ASM.

Use the ls command in the asmcmd utility to view the location of voting files if stored in ASM.

Use crsctl query css votedisk to view the location of voting files if stored in a file system.

Use cat /etc/oracle/olr.loc to view the location of the OCR and OLR if stored on a file system.

Audit information gathered by each cluster node can be consolidated into the unified ACFS audit trail.

acfsutil audit archive must be used to archive audit files that are larger than 10MB.

acfsutil audit init must be run by a system administrator.

acfsutil audit purge can be run by an audit manager.

acfsutil audit read marks audit files to indicate that it is safe to purge them.

You must create a Grid Management Repository database.

You must enable the Name Server Cache Daemon (NSCD).

A DHCP service on the private network for the cluster is required to allocate virtual IP addresses for HAIP.

Each cluster node must have at least two network interface cards,

DNS must be configured to delegate name resolution for the cluster subdomain to the cluster.

A DHCP service on the public network for the cluster is required to allocate virtual IP addresses as required by the cluster.

an operating system version

a version of Oracle database server used in Real Application Cluster (RAC) databases

software required to configure nodes at startup

the GPnP software

a file system version used for the software to be installed

a version of Automatic Storage Management (ASM) used for the cluster

The host name in the tnsnames entry must be changed if nodes are added or removed from the Cluster.

Clients using EZConnect can benefit from connect time load balancing because the tnsnames entry refers to a SCAN listener.

Client connection requests are automatically balanced across all IP addresses defined for the SCAN.

A client connection request is received by a SCAN listener that creates the connection to the least-loaded database instance.

Client connection requests are automatically failed over to another SCAN listener if the chosen SCAN listener is not available.

In a RAC One Node database, there is no LMD0 process if only one instance is running.

Global Enqueues and Instance Locks replace mutexes completely in RAC database instances.

In a RAC database, there is no LMD0 process if only one instance is running.

Global Enqueues and Instance Locks replace latches completely in RAC database instances.

Global Enqueues may have owners and waiters in the same instance.

Global Enqueues may have converters and waiters in the same instance.

The ORACLE_HOME environment variable must be set to the Grid Infrastructure home directory in the installation owner’s environment.

The upgrade must be done in-place.

The upgrade must be done out of place.

Upgrade validation may be done using the Oracle Universal Installer which in turn invokes the built-in cluster verification utility.

The cluster verification utility cluvfy.sh can verify that the cluster is ready for an upgrade.

The ORACLE_SID environment variable must be set to the SID of the ASM instance in the installation owner’s environment.

The cluster verification utility cluvfy.sh can generate fixup scripts to run on all nodes of the cluster.

Single Client Access Name (SCAN) virtual IP addresses (VIPs)

Grid Naming Service (GNS) VIPs

ASM Listener VIPs

High Available IP (HAIP) addresses uses for the cluster interconnect

Intelligent Platform Management Interface (IPMI) IP addresses

They exist both in ASM and RDBMS instances, and display the same output.

Their names can be seen in dict when connected to an ASM instance.

Their names can be seen in vfixed_table when connected to an instance of any type that is started.

They exist in both in ASM and RDBSM instances, but they can display different outputs depending on the instance type.

gvasm_attribute can be used to display the ASM_POWER_LIMIT attribute of all ASM instances in the cluster.

It is automatically created when a service is created using SRVCTL ADD SERVICE.

It contains a list of server pools on which the instances hosting the service can run.

It contains a node list and instance-to-node mapping information for the service.

It specifies the instance to which the service should fail over, if the preferred instance shuts down or fails.

It is automatically created when a service is created using DBMS_SERVICE.CREATE_SERVICE.

a Grid Management Repository database

a network interface for ASM and private interconnect traffic

a network interface for private interconnect only

a network interface for the public network

a Grid Management Cluster Health Management (CHM) application server

contention on index leaf blocks

sequence definitions

the size of the online redo log buffers

contention for online redo log files

contention for archived redo log files

the load on the Cluster Interconnect

acfssettag is a command provided by a platform-independent API to tag files.

acfssettag is a command provided by a platform-dependent API to tag files.

ACFS tagging is used to mark a subset of files in an ACFS file system for replication.

acfsutil encr on can be used to specify the tag names of the files to be encrypted.

acfsutil tag set can be used to tag files.

It applies a patch to the Grid Infrastructure only on the first cluster node.

It applies a patch to the Grid Infrastructure on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs, with the same release as the Grid Infrastructure, only on the first cluster node.

It applies a patch to all database ORACLE_HOMEs, with the same release as the Grid Infrastructure, on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs of any version on the first cluster node.

It applies a patch to all database ORACLE_HOMEs of any version on all cluster nodes.

It applies a patch to one ORACLE_HOME only on the first cluster node.

It applies a patch to all database ORACLE_HOMEs with the same release only on the first cluster node.

It applies a patch to one database ORACLE_HOME on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs with the same release on all cluster nodes.

It applies a patch to all database ORACLE_HOMEs with the same release on the first cluster node.

It fails because an ASM instance is not configured to run on HOST02.

It succeeds and starts an ASM instance on HOST02 and shuts down the ASM instance on HOST03.

It succeeds and 12c database instances connected to the ASM instance on HOST03 can be reconnected to the ASM instance on HOST02.

It fails because the ASM instance has not been shut down first on HOST03.

It succeeds and starts an ASM instance on HOST02 but the ASM instance on HOST03 is not shut down until all connected clients disconnected.

It succeeds and 12c database instances connected to the ASM instance on HOST03 can be reconnected to the ASM instance on HOST01.

1, 3, 2, 5 and 8

3, 2, 5 and 8

1, 2, 3, 5 and 8

3, 2, 6 and 8

3, 2, 5, 2 and 8

A thread of redo must be created before starting a fourth instance if a thread is not already available.

A thread of redo must contain at least two log groups before it can be enabled.

A redo log group added using ALTER DATABASE ADD LOGFILE without the INSTANCE clause is added to each instance.

All the instances must have the same number of redo log groups and each group must have the same number of redo log members.

A thread of redo is automatically dropped when an instance is removed from a RAC database by using SRVCTL.

The service must be manually restarted with SRVCTL every time the instance hosting the service fails.

Clusterware will monitor the service while it is active.

The service must be manually restarted with SRVCTL after restarting the Clusterware stack on the node hosting the service.

When manually started, the service will always start on one or more available instances rather than on their preferred instances.

The service must be manually started with SRVCTL after a planned restart of the instance hosting the service.

Run ocrconfig –repair on another node in the cluster to repair the ocr.loc file on host01

Stop the clusterware stack on host01 only.

Stop the clusterware stack on all cluster nodes.

Run ocrconfig –repair on host01.

Stop the clusterware stack on host01 and on the node used to issue the ocrconfig –repair command.

A policy-managed resource can be started manually using crsctl.

A policy-managed resource can be started manually using srvctl.

Resource dependencies are automatically set when using a policy-managed resource.

An administrator-managed resource can be started manually using crsctl.

An administrator-managed resource can be started manually using srvctl.

The action script is automatically set when using a policy-managed resource.