1z0-078 Questions and Answers

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.

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.

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

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.

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

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.

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.

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.

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.

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.

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.

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

Transparent Application Failover (TAF) using Fast Application Notification (FAN)

Transparent Application Failover (TAF)

Fast Connection Failover (FCF)

Fast Connection Failover (FCF) with Transparent Application Failover (TAF)

A copy of an encrypted file is not encrypted unless it is created in an encrypted directory.

An ACFS snapshot can be ACFS encrypted.

acfsutil encr off can be run by an encryption manager who may not have system administrator privileges.

acfsucil encr on can be used to specify the encryption key length for a directory or file.

acfsutil encr inic is used to establish role separation between encryption managers and encryption auditors.

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.

It can analyze performance over any given time period.

It can diagnose skew in response time.

It can analyze performance using data captured on all instances.

It can only analyze performance on the instance running the ADDM job.

It can diagnose latency problems in the Cluster Interconnect.

It runs automatically in Instance ADDM mode after each AWR snapshot is created.

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.

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.