1z0-078 Oracle Database 19c: RAC, ASM, and Grid Infrastructure Administration Questions and Answers

All server pools in a cluster are controlled by the policy set, when user-defined policy management is used.

Clusterware administrators cannot directly modify the policy set when Quality of Service (QoS) Management is used.

A server pool can have different attributes defined for different policies in the policy set, when user-defined policy management is used.

A server pool can have the same attributes defined for different policies in the policy set, when user-defined policy management is used.

Servers in a server pool outside the control of the policy set are never affected by policy changes, when user-defined policy management is used.

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.

Any database instance with the COMPATIBLE parameter set to 12.2 or later can access it.

It can contain ASM Dynamic Volume Manager (ADVM) volumes.

Each disk in each of the three fail groups is a mirror of the corresponding disk of the other two failure groups.

The ASM compatible attributes can be changed to 12. l for this disk group.

Files created in this disk group always have two copies for each allocation unit: one primary and one secondary.

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 disconnect.

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

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

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

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

The Grid Infrastructure Management Repository is only required when using ASM.

Specifying the use of Grid Naming Service is optional.

Normal Redundancy ASM Disk Groups used for Clusterware files will contain three voting files regardless of the number of

The Clusterware binaries may be installed without installing ASM binaries.

High Redundancy ASM Disk Groups used for Clusterware files will contain two OCRs.

The Oracle Clusterware stack is stopped on all nodes.

The Oracle Clusterware stack is prevented from being automatically started on host01.

The Oracle Clusterware stack is prevented from being automatically started on all nodes.

The Oracle Clusterware stack is stopped on all nodes except host01.

The Oracle Clusterware stack is started on all nodes except host01.

The Oracle Clusterware stack is started on all nodes.

They can be applied in-place.

When performing rolling patches, the vips for the node being patched are relocated to another node.

Some Grid Infrastructure patchsets may not be intalled in a rolling fashion.

When performing rolling patches,crsctl query crs softwareversionalways displays the earliest version of the software running anywhere in the cluster.

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

AR can fail over to any one of the available CD31 instances.

AR runs as a singleton service in the server pool prod pool and the AR service is available in each of the CDBl instances.

AR can fail over to any other available CDBl instance in prod pool.

AR is available only on the CDBl instance onhost01.

AR is available on any one available CDBl instance in prod pool at any one time.

crsctl stop cluster

crsctl config crs

crsctl disable crs

crsctl stop crs

Database instances perform read I/O using an ASM instance as an I/O Server.

Database instances can write metadata to ASM diskgroups.

Database instances perform read I/O directly to ASM Disks.

ASM instances can write metadata to ASM diskgroups.

If a database instance writes to an ASM-based datafile whose redundancy attribute is set to mirror, then the ASM instance writes the mirror copy

The service must be manually started withSRVCTLafter a planned restart of the instance hosting the service.

The service must be manually restarted withSRVCTLevery time the instance hosting the service fails.

The service must be manually restarted withSRVCTLafter restarting the Clusterware stack on the node hosting the service.

Clusterware will monitor the service while it is active.

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

Services support the balancing of client connections across RAC database instances.

In server-side load balancing, node listener redirects the client to another node listener for connection to an instance.

Load balancing can be done by the client or the listener, but not both, for any one connection request.

Client-side connect-time load balancing can balance connection requests across SCAN listeners.

Load balancing can be done by the client, the listener, or both, for any one connection request.

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.

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

Their names can be seen inv$fixed_tablewhen connected to an instance of any type that is started.

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

gv$asm_attribute can be used to display the ASM_POWER_LIMIT attribute of all ASM instances in the cluster.

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

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.

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

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

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 redo log group added using alter database add logfile without the instance clause is added to each instance.

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

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.

Oracle RAC Resource Management only allows assignment of the SGA during instance startup.

Oracle RAC Resource Management requires the same SGA value for all the instances of a RAC database which is configured during database startup only.

Oracle RAC Resource Runtime Management allows for automatic and runtime adjustment of the SGA.

Oracle RAC Resource Management only allows assignment of the SGA during database startup.

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.