1Z0-078 — frequently asked questions

In RAC, OPatch is cluster-aware and defaults to All-Node patching when no rolling or minimize-downtime option is provided.

No; it patches only the Oracle Home from which the command is run, not every home of the same release.

They protect memory structures accessed only by processes inside a single instance, so they never serialize access across the instances of a multi-instance database.

The Global Cache Service (GCS) coordinates database block buffers through cache fusion, while the Global Enqueue Service (GES) manages enqueues across all instances.

Because CDB1 has six instances, but prod_pool has cardinality 3, so only three instances are in the pool; a singleton service is restricted to its server pool.

Singleton means AR runs on exactly one instance in prod_pool at a time and can fail over to another instance within that same pool.

No, OCRCHECK only checks the integrity of the OCR, not the OLR.

Yes, CLUVFY can check the integrity of both OCR and OLR using commands like 'cluvfy comp ocr -n all'.

While acfsutil encr init initializes the encryption wallet, it does not directly establish role separation assignments. Role separation is configured via separate user assignments after initialization.

Yes, ACFS snapshots inherit the encryption settings of the parent directory, ensuring data remains protected at rest in the snapshot.

Staging is part of the patching workflow, but the question targets OPatch's documented environment prerequisite: setting PATH to $ORACLE_HOME/OPatch before invoking the utility.

No. Oracle requires updating PATH only on the node where you will run OPatch; other nodes' environments are irrelevant unless you execute OPatch there.

Ologgerd does not run on every node. It aggregates logs from all nodes onto one or a few nodes to reduce overhead and network traffic.

By default, CHM data is stored in flat files under $GRID_HOME/log/<hostname>/chm, not inside the MGMTDB database as in previous versions.

VIPs are relocated to prevent client connection drops. If the VIP remained on the patched node, clients connecting via that VIP would lose connectivity while the node's stack was down.

No. Some patches, especially those affecting the cluster file system or requiring kernel updates, may necessitate a complete cluster outage. However, the question focuses on the mechanics of rolling patches where possible.

No, only managed server pools are controlled. Unmanaged pools like 'Generic' are excluded from policy set governance.

Yes, administrators can still modify the policy set. QoS Management provides performance-based recommendations but does not lock the configuration.

No. In GI 19c, the system handles encryption and certificates automatically. Administrators do not need to create or manage an Oracle Wallet for the cluster interconnect.

Yes. Secure Cluster Communication uses Transport Layer Security (TLS) to ensure privacy and data integrity between cluster nodes automatically.

It is not registered automatically; you must use srvctl to add or enable it in the OCR.

No, the default service lacks the configuration needed for Clusterware to automate the opening process.

CTSSD decides its mode by checking whether the NTP daemon is active, not whether configured time servers respond, so unreachable servers leave CTSSD in observer mode.

No. CTSSD starts automatically at clusterware startup and selects observer mode when NTP is active; you must deactivate NTP on all nodes for active mode.

It enters a 'drain' state to allow connected database instances to gracefully reconnect to the new ASM instance on HOST02 without dropping connections.

They reconnect to HOST02, as it is the new node hosting the active ASM instance that provides the storage services.

srvctl is the primary tool for managing both server pools and user-defined policies. You use 'srvctl modify policy' to activate or deactivate a specific policy.

No. By design, user-defined policies are initially inactive. They must be explicitly activated by an administrator to begin enforcing resource constraints.

Option A implies all requests for a partitioned table go to one instance. Affinity actually maps specific partitions or subsets to different instances based on load and data location, not just a single static target for the whole table.

XA affinity directs all branches of a distributed transaction to a single RAC instance. This prevents cross-instance locking and minimizes global cache block pings during the transaction processing.

In Oracle 19c, DBCA has been enhanced to handle template creation and RAC conversion autonomously, making the separate use of rconfig unnecessary for this specific workflow.

Yes, when you use DBCA to create a RAC database from a template, it configures all necessary cluster resources and can start the instances as part of the deployment process.

The source PDB must be open to provide the data files for cloning. Closing it would make the data inaccessible for the create process.

No, restricted mode is not required. The key requirement is READ ONLY mode if the CDB is not in ARCHIVELOG mode to ensure consistency.

Yes, ACFS snapshots can be created from both read-only and read/write file systems. The key requirement is the ADVM compatibility level.

Redundancy determines data protection levels, not feature availability. Snapshots work across all redundancy types as long as version compatibility is met.

Because upgrades are out-of-place; the installer uses its own path resolution. Setting ORACLE_HOME to the old home can cause conflicts or incorrect file selection.

Yes, cluvfy.sh can generate fixup scripts that you can execute to resolve configuration issues detected during the verification phase.

The term 'quorum failgroup' is specific to Flex ASM and certain redundancy configurations. Standard voting disk groups do not universally require this specific terminology or configuration during basic installation.

Yes, an ASM instance can start even if no disk groups are specified or available during installation. It will remain operational until a disk group is created and mounted.

Setting COMPATIBLE.RDBMS to 12.1 prevents Oracle 11g databases from mounting the diskgroup. Since the scenario requires supporting 11g RAC, this attribute must remain at 11.2.

Not strictly for the feature itself, but COMPATIBLE.ADVM must be 12.1. In Option D, ASM is raised to 12.1 likely for best practice or specific GI interactions, but the critical factor is ADVM >= 12.1 and RDBMS <= 11.2.

No, it primarily depends on the availability of the preferred instance. Performance metrics are handled by Load Balancing Goals.

The trigger is the preferred instance becoming available again after a failure or downtime event.

Oracle documents that specifying TRANSACTIONAL on an ASM instance performs an IMMEDIATE shutdown, so the same description fits both labels — which is why the question has two valid lists.

NORMAL waits for connected sessions to disconnect before shutting down, so while a database instance is still attached as an ASM client the command errors out and no dismount occurs.

SYSREPL is not part of Oracle's privilege set. ACFS replication is administered with acfsutil repl by root, grid or an ASM administrator, not through a replication-specific role.

No. Standby redo logs are database Data Guard objects; ACFS replication transfers file system change data directly to the standby ACFS file system without database redo streams.

Fix-up scripts are generated when the installer detects missing OS prerequisites, and on UNIX/Linux they must be run as root to apply the fixes.

Under standard Oracle licensing, yes—RAC is an Enterprise Edition option. Some engineered systems may allow SE2 with RAC, but 1Z0-078 expects Enterprise Edition.

No, changes to ASM_DISKSTRING do not require a restart of ASM instances; they are dynamic.

It controls the degree of parallelism for rebalance operations, not the number of client instances.

Enqueue resources require frequent access to library cache-like structures, which are optimized in the shared pool. The large pool is reserved for large contiguous allocations like backup buffers.

Yes, multiple shadow resources can exist to provide redundancy and allow other instances to quickly access lock information without contacting the master instance immediately.

PDBs can be relocated using srvctl, and the -eval flag allows checking impact on instances and services.

No, the specific documentation lists Local resources, Administrator-defined resources, and PDBs as the evaluable entities.

Oracle ACFS restrictions prevent storing Oracle Clusterware, ASM, and ADVM components in its file systems to ensure stability and proper management.

Yes, in a RAC environment, database instances can act as clients to ASM instances running on any node in the cluster via the interconnect.