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

ASM Cluster File System (ACFS) can be deployed on any nodes.

A database instance on a node can be a client of an ASM instance running on any node.

A database instance on a node cannot be a client of an ASM instance running on other nodes.

A database instance on a node can only be a client of an ASM instance running on the same node.

A database instance on a node uses an ASM instance as an I/O server when requesting I/O to diskgroups.

An ASM instance and database instances can coexist on the same node.

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;

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.

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.

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

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.

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.

High availability for the CRM service

Load balancing of connection requests across all six database instances

High availability for the ERP service

Load balancing of client connection requests for CRM across four Single Client Access Name (SCAN) listeners

Load balancing of connection requests for ERP across all database instances running on servers in the prod pool

Load balancing of client connection requests for ERP across three Single Client Access Name (SCAN) listeners

Load balancing of connection requests for CRM across all database instances running on servers in the prod pool

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.

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 ADVM volume is individually named and can contain only one file system.

ADVM extends ASM by providing a device driver interface to storage backed by an ASM disk group.

File systems contained in ADVM volumes may only contain database files.

Only one ADVM volume can be created in an ASM disk group.

To create an ADVM volume, disk group attributes COMPATIBLE.ASM and COMPATIBLE.ADVM must be minimally set to 12.1.<.span>.

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.

An application VIP is created on the default network by the appvipcfg utility.

Application VIPs do not fail over to surviving cluster nodes when the node hosting the VIP fails.

If an application sends messages to be displayed and sets the display variable, then an application VIP is required.

An application VIP can be created with the crsccl utility.

An application VIP is created on the interconnect network by the crsccl utility.

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 OCRCHECK utility can check the OLR in an online fashion with the clusterware running on all nodes.

The OCRCONFIG utilty can be used to repair a corrupt OCR file in an online fashion with the clusterware running on all nodes.

The CLUVFY utility can check the integrity of the OCR but not the OLR.

The OCRDUMP utility can dump specific keys from the OLR in an online fashion with the clusterware running on all nodes.

The OCRDUMP utility can dump specific keys from the OCR in an online fashion with the clusterware running on all nodes.

The clusterware log files are stored inside the Grid Infrastructure Management Repository database used by the cluster health monitor

The diagcolleccion.pl script must be run from the Grid home directory as the arid infrastructure owner.

There is one ologgerd service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

The oclumon utility may be used to get and set parameters for the cluster health monitor (CHM) repository.

There is one osysmond service for the cluster health monitor (CHM) on each cluster node regardless of cluster size.

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.

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.