Oracle 1z0-078 Oracle Database 19c: RAC, ASM, and Grid Infrastructure Administration Exam Practice Test

It fails to resize voli because it must be executed as a user belonging to the sysasm group.

It fails to resize the filesystem because it must be unmounted before resizing.

It succeeds but leaves the file system unmounted.

It resizes voli.

It resizes the filesystem mounted on /u01/app/grid/acfsmount.

Update the path environment variable on each cluster node to point to the 50RACLE HOME/OPacch directory

Stage the patch on the cluster node where the OPacch utility will be executed.

Update the path environment variable on the node where you will run the OPatch utility to point to the SORacle HOME/OPacch directory.

Stage the patch on all cluster nodes.

It can manage database services only if they are defined as UNIFORM services.

It requires Oracle Grid Infrastructure for a Cluster to be installed and Clusterware to be running.

A server pool can be managed by QoS even if it does have database instances running on any server in the pool.

Databases managed by QoS can be administrator managed or policy managed.

It supports multiple databases assigned to the same server pool.

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

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

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

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

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

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

If ASM disk groups are configured for the Clusterware files, then ASM must be used for all databases on the cluster.

The Installer permits the creation of a disk group to be used for the Recovery Area for the ASM instance.

If no ASM disk groups are specified during installation, then ASM instances are not started after the installation completes on any cluster node.

ASM disk groups used for voting files and OCR files require a quorum failqroup.

The Installer permits the creation of a disk group for use by the voting disks and OCR file.

ssh user equivalence for the Oracle software owner must be configured on all cluster nodes where the Database software will be installed.

Grid Infrastructure must be installed on all cluster nodes.

The Clusterware stack must be up on all cluster nodes.

The Clusterware stack must be up on all cluster nodes where the Database software will be installed.

SSH user equivalence for the Oracle software owner must be configured on all cluster nodes.

Grid Infrastructure must be installed on all cluster nodes where the Database software will be installed.

Dynamic Service Fallback allows a service to relocate to an available instance when the service is stopped on a preferred instance.

Dynamic Service Fallback allows a service to fall back to a preferred instance when the available instance performance falls below a specified threshold after it was failed over to an available instance.

To enable Dynamic Service Fallback, you should specify the level of performance of a preferred instance for a service to be relocated to an available instance by setting the -fallback attribute of a service to "Low, Medium, or High".

Dynamic Service Fallback allows a service to fall back to a preferred instance when it becomes available after it was failed over to an available instance.

They listen only for database instances on the same node.

They listen on behalf of any ASM instance and all database instances on the same node.

They listen only for the ASM instance on the same node.

There can be only one node listener per node.

They run from the Grid Infrastructure home by default.

2 = NORMAL, 3 = TRANSACTIONAL, 1 = ABORT

2 = NORMAL, 3 = IMMEDIATE, 1 = ABORT

3 = NORMAL, 2 = TRANSACTIONAL, 1 = ABORT

3 = NORMAL, 2 = ABORT, 1 = IMMEDIATE

3 = NORMAL, 2 = IMMEDIATE, 1 = ABORT

Data files, redo logs, and RMAN backup pieces must be stored in different ASM disk groups for optimal performance.

All ASM Disks belonging to a disk group should be of the same size for optimal performance.

Hardware-based mirroring combined with ASM mirroring guarantees optimal performance.

All ASM Disks belonging to a disk group should have the same hardware specifications and storage attributes for optimal performance.

To improve performance a database must have two disk groups; one for data and one for the fast recovery area.

Transparent Application Continuity is automatically enabled for a session when a database session reaches a safe place (such as a connection test or a known recoverable point) and the transactions are drained at the database.

Transparent Application Continuity is enabled when failover type=auto.

Recovery of the user database session is done safely and with no need for a DBA to have any knowledge of the application or make application code changes.

Recovery of the user database session is done safely by enabling auto recover within the user database session.

Transparent Application Continuity is enabled when failover type=All

Using the rconfig utility to migrate the database to shared storage and then using dbca to start one or more RAC database instances on the cluster

Using dbca to migrate the database to shared storage and then to start one or more RAC database instances on the cluster

Using the rconfig utility to create a template from the single-instance database and then using dbca to create a RAC database on the cluster using that template

Using dbca to create a template from the single-instance database and then to create a RAC database on the cluster using that template

One undo tablespace for each pdb is required.

PDBs can have local temporary

You can open one, several, or all PD3s on one, several, or all cdb instances.

It requires the cdb to use shared undo management.

One undo tablespace for each instance is required.

PDBs must use shared Temporary

The DB_CREATE_FILE_DEST parameter must be set to +DATA(newtemplate).

newtemplate must be defined for the +DATA disk group.

Existing data files in TBS1 must also use the same template.

User-defined subdirectories ORCL and USERS must already exist.

The +DATA disk group should not be part of Flex ASM.

Zero Downtime Patching requires out-of-place patching of Oracle Grid Infrastructure 19c with Oracle RAC or Oracle RAC One Node databases of 19c or later releases and only the binaries in the Oracle Grid Infrastructure user space are patched.

When using Zero Downtime Patching, the root.sh script must be executed manually with –nodriver update option.

When using Zero Downtime Patching, Oracle Grid Infrastructure OS system software, kernel modules and system commands including ACFS, AFD, OLFS, and OKA are not updated.

Zero Downtime Patching requires in-place patching of Oracle Grid Infrastructure 19c with Oracle RAC or Oracle RAC One Node databases of 19c or later releases and only the binaries in the Oracle Grid Infrastructure user space are patched.

Zero Downtime Patching can be fully automated by selecting the option to automatically run the root.sh script.

Run the crsctl unpin css - host04 command as root on host01, or on either host02 or host03.

Run the crsctl delete node -n host04 command as root on host04.

Run the crsctl delete node -n host04 command as root on host01, or on either host02 or host03.

Run the crsct1 unpin css - host04 command as root on host04.

Run the rootcrs.pl -deconfig -force command as root on host04.

Run the rootcrs.pl -deconfig -force command as root on host01, or on either host02 or host03.

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

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

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

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

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

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

If network time protocol (NTP) time servers are unreachable on any cluster node, then Oracle Cluster Time Synchronization Service (CTSSD) will start automatically in active mode when the clusterware is started.

Configure network time protocol (NTP) on all cluster nodes, and then start the Oracle Cluster Time Synchronization Service (CTSSD) in active mode on all cluster nodes.

If network time protocol (NJP) is not configured properly on all cluster nodes, then Oracle Cluster Time Synchronization Service (CTSSD) will start automatically in active mode when the clusterware is started.

Configure network time protocol (NTP) on all cluster nodes; Oracle Cluster Time Synchronization Service (CTSSD) will then start automatically in observer mode when the clusterware is started.

Deactivate network time protocol (NTP) on all cluster nodes; Oracle Cluster Time Synchronization Service (CTSSD) will then start automatically in active mode when the clusterware is started.

Database block buffers

Mutexes

Redo log buffers

Latches

Enqueues

Cursors

Use srvctl start vip to start the VIP on host01.

Use oifcfg setif to start the VIP on host01.

Use oifcfg setif to stop the VIP on host01.

Use srvctl modify nodeapps to change the VIP on host01.

Use srvctl stop vip to stop the VIP on host01.

Client-side connect time load balancing works only if it uses a tnsnames entry specifying load BALANCE=yes.

Server-side connect time load balancing is done at the time of the initial connection attempt to the database service.

Server-side load balancing connections are always distributed across instances based on the fastest response time for the service.

Client-side connect time load balancing is done at the time of the initial connection attempt to the database service.

In client-side load balancing, the SCAN listener uses the Load Balancing Advisory to direct a connection request to the least loaded instance hosting the service.

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

acfsutil audit init must be run by a system administrator.

acfsutil audit purge can be run by an audit manager.

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 10 MB.

1, 2, 3, 4, 5 and 6.

2, 3, 4 and 6.

1, 2, 3 and 4.

2, 3, 4, 5 and 6.

1, 2, 3, 4 and 6.

1, 2, 3, 4, 5, 6 and 7.