1z0-078 Sample Questions Answers

When a policy is activated, resources can be automatically stopped to comply with the policy definition.

An administrator-defined policy may be activated using the srvctl utility.

When a policy is first created, it is initially inactive.

When a policy is first created, it is initially active.

When a policy is activated, resources cannot be automatically started to comply with the policy definition.

When a policy is activated, nodes may be reassigned to server pools based on the policy definition.

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.

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.

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.

They listen only for database instances on the same node.

They listen on behalf of any ASM instance and all database instances on the same node.

They listen only for the ASM instance on the same node.

There can be only one node listener per node.

They run from the Grid Infrastructure home by default.

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.

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.

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.

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.

crsctl stop cluster

crsctl config crs

crsctl disable crs

crsctl stop crs

It is uniformly available on all instances for administrator-managed databases.

It cannot be used to automate the opening of the PDB by the Clusterware.

It is automatically registered in the OCR.

It is created and started on only one instance when using policy-managed database configuration.

It is not automatically registered in the OCR.

Each hub node must be connected to storage shared across all hub nodes.

Each leaf node must be connected to storage shared across all cluster nodes.

Each leaf node must be connected to storage shared across all leaf nodes.

Leaf nodes require direct access to the voting disks.

Hub nodes require direct access to the OCR file.

Hub nodes require direct access to the voting disks.

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.

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)

Oracle RAC Resource Management only allows assignment of the SGA during instance startup.

Oracle RAC Resource Management requires the same SGA value for all the instances of a RAC database which is configured during database startup only.

Oracle RAC Resource Runtime Management allows for automatic and runtime adjustment of the SGA.

Oracle RAC Resource Management only allows assignment of the SGA during database startup.

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.

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.

an application VIP

A Server Pool

a resource dependency definition

an application resource

a script agent

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.

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