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

When possible, clients with the samecolocation_tagare routed to the same instance that offers a given service.

When possible, clients with the samecolocation_tagare routed to the same available instance even if a preferred instance is available.

When possible, clients with the samecolocation_tagcould be routed across a set of preferred instances based on a specific load balancing option.

When possible, clients with the samecolocation_tagare routed to the same available instance when a preferred instance is not available.

Cluster resources

Database transactions

Local resources

Administrator-defined resources

Pluggable Databases (PDBs)

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

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

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

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.

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

The upgrade must be done out-of-place.

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

crsctl stop cluster

crsctl config crs

crsctl disable crs

crsctl stop crs

Security for the cluster interconnect is invoked automatically as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c and Database administrators or cluster administrators do not need to make any configuration changes for this feature.

Security for the cluster interconnect is invoked automatically as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c using an auto-generated encryption key that is stored locally on each node of the cluster in an Oracle Wallet and Database administrators or cluster administrators must provide a valid path for the Wallet file.

Security for the cluster interconnect is invoked by auto-generated server certificates that will be assigned to each cluster node as part of a new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c.

Database administrators or cluster administrators must provide an encryption key during new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c to secure the interconnect communication.

Database administrators or cluster administrators must provide a valid server certificate and an Oracle Wallet for each node during new Oracle Grid Infrastructure 19c deployment or an upgrade to Oracle Grid Infrastructure 19c to secure the interconnect communication.

The disk group compatibility attribute for advm must be set to 12. l or higher.

The parent snapshot must be read-only.

The underlying advm volume must be configured with high redundancy.

The parent snapshot must be read/write.

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.

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

It applies a patch to one database ORACLE home on alll cluster nodes.

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

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

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

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.

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.

an 0/S user to own the Oracle Database installation

an O/S group called dba

an O/S user to own the Grid Infrastructure installation

an O/S group to own the software inventory

A group to own Automatic Storage Management (ASM) Filter Driver-provisioned storage

an O/S user to own the Clusterware installation and a different O/S user own the Automatic Storage Management (ASM) installation

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.

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.

exec sys.dbms shared pool.keep('SEQ1','Q'>

alter sequence seal cache 10000;

alter sequence seql noorder;

alter sequence seql keep;

alter sequence seql order;

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.

The source PD3 must be closed on the CDS instance from where the command is executed.

The source PD3 must be in read only mode on all CD3 instances if the CDB is in No Archive mode.

The source pdb must use a global temporary

It can be executed only by a common user with the create pluggable database system privilege connected to the root container.

Oracle Managed Files must be enabled or PD3 file name convert must be set.

All running CDB instances must be open in restricted mode.

Different nodes in a cluster may belong to separate administrator-defined categories.

All nodes in a cluster belong to the same Oracle-supplied category.

A server may be added to only one category using the crsctl utility.

All server attributes that may be used to determine the server category are discovered automatically by Oracle Clusterware.

All server attributes used for categorization are administrator modifiable.

Server categories can only be used for nodes running an application server.

A server pool must be created with srvct1 before creating a policy-managed RAC database that uses that server pool for a service.

They can be policy managed for a multitenant database.

Policy-managed services specified for a database allow the creation of a new server pool using dbca.

They can be administrator managed for a multitenant database.

Singleton services are not permitted for multitenant databases.

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.