1Z0-078 Sample Questions & Answers

This allows the administrator to control exactly when the I/O-intensive rebalance operation occurs, minimizing impact on the workload by running it during off-peak hours.

Proper failure group design is crucial for ASM's striping and mirroring. Adding disks to a new failure group (or distributing them among existing ones) is necessary for ASM to maintain redundancy and balance data correctly.

The goal is a balance between speed and workload impact. POWER 1 is too slow. A very high power would impact the workload too much. A moderate power like 4 is a common choice to make good progress without causing severe performance degradation.

The Cluster Synchronization Services Daemon (CSSD) is responsible for cluster integrity and node membership, which requires access to voting disks. The log message "Waiting for voting disk access" is the key indicator. Since CSSD on node1 is online, it has successfully accessed the voting disks. The failure of CSSD on node2 to come online, combined with the log message, strongly points to a loss of connectivity from node2 to the shared storage where the voting disks reside.

This is a primary use case for Flex Clusters. Leaf Nodes can host database instances but do not require direct access to storage. They connect to ASM instances running on Hub Nodes over the ASM network. This reduces storage network traffic and is ideal for scalable, read-intensive workloads where direct, high-bandwidth storage access from every node is not critical.

The correct way to control PDB placement and workload in RAC is through services and server pools. By creating a server pool with only the desired nodes and then creating a service for the PDB that is assigned to that pool, you ensure that connections to that PDB (via the service) are routed only to the specified nodes, and the PDB will only be active on nodes within its assigned pool.

The zero-downtime patching process involves multiple phases. First, opatchauto apply -prepare-clone is used to prepare the new home. After this is done on all nodes, opatchauto apply -deploy-clone is run. This command performs the switchover by stopping the old GI stack and starting the new, patched GI stack in a rolling fashion across the cluster, ensuring the cluster remains operational throughout the process.

In RAC, a COMMIT requires that not only the local instance's redo is written to disk, but also that any corresponding current blocks in other instances' caches are flushed to disk or downgraded. The log file sync wait event in RAC includes the time spent waiting for this cross-instance coordination, which is captured by the gcs log flush sync wait event. If local redo write time is low but log file sync is high, it's very likely that this global coordination is the source of the delay.

The GIMR is a dedicated database (typically multitenant) installed with Grid Infrastructure to serve as a repository for cluster-wide management data. Its primary clients are the Cluster Health Monitor (CHM), which stores fine-grained OS and cluster performance metrics, and Oracle Database Quality of Service (QoS) Management.

The acfsutil audit enable command is used to turn on the auditing feature for a specific ACFS mount point. Once enabled, it captures file access and modification events based on the configured audit rules, storing them in a secure audit trail.

The DB_FILE_NAME_CONVERT parameter is specifically designed for this purpose. It takes a pair of strings: the pattern to find in the source datafile names and the pattern to replace it with for the target. For this scenario, you would set it to ('/u01/oradata/PROD/', '+DATA/') to instruct Oracle to convert filesystem paths to ASM paths.

The 'what-if' evaluation can predict the cascading effects of stopping a resource, showing which dependent resources would also be stopped.

This command can evaluate the impact of relocating a resource, verifying if the target location is valid and if any other resources would be affected.