Free Oracle 1z0-078 Practice Exam with Questions & Answers

An administrator-managed resource can be started manually using srvct1.

A policy-managed resource can be started manually using crsct1.

An administrator-managed resource can be started manually using crsct1.

The action script is automatically set when using a policy-managed resource.

A policy-managed resource can be started manually using srvct1.

Resource dependencies are automatically set when using a policy-managed resource.

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.

The maximum value of ASM_POWER_LIMIT is 1024.

The default value of INSTANCE_TYPE is ASM.

A change to ASM_DISKSTRING requires a restart of all ASM instances for the change to take effect.

The ASM_DISKGOUPS parameter is optional.

ASM_POWER_LIMIT controls the number of RDBMS instances that can access a disk group while it is being rebalanced.

You can dynamically assign a newly created undo tablespace to an instance.

In a policy-managed RAC database, an undo tablespace may automatically be created if OMF is enabled for the database.

An instance that performs instance recovery can write to the undo tablespace of a failed instance.

A mixture of automatic undo management and manual undo management is supported within a RAC database.

It is necessary to assign a specific undo tablespace to a specific instance.

Oracle RAC affinity for partitioned tables routes all database requests for a partition tables to a single Oracle RAC instance leading to higher Oracle RAC performance and scalability because of improved cache locality and reduced internode synchronization and block pings of the partition tables.

Oracle RAC affinity for partitioned tables routes database requests to Oracle RAC instances in such a way that each instance always gets requests for a disjoint subset of rows in the database, this affinity leads to higher Oracle RAC performance and scalability because of improved cache locality and reduced internode synchronization and block pings.

Oracle RAC affinity for partitioned tables routes database requests to all available Oracle RAC instances evenly to create a global affinity in such a way that each instance always gets an even number of requests leading to higher Oracle RAC performance by using a higher levels of available global cache to reduce global resource contention.

To enhance the performance of distributed transactions with applications server that provides XA affinity, you can automatically spawn new dedicated database RAC instances to isolate distributed transaction.

To enhance the performance of distributed transactions with applications server that provides XA affinity, you can direct all branches of a distributed transaction to a single instance in the cluster to improve cache locality and reduce internode synchronization and block pings.

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.

Use the crsct1 set trace res "resource_name=debugging_level" command.

Use the crsct1 set log res "resource_name=debugging_level2" command.

Set the environment variable _USR_ORA_DEBUG=1 and then stop and restart the resource that requires resource debugging data to be collected.

Use the cluvfy comp command for the specific resource within a component.

Only one GRD shadow resource may exist for an Enqueue Resource.

Shadow GRD resources may exist in more than one database instance for a resource.

Clustered ASM has GRD resources distributed among all ASM instances.

All GRD Enqueue Resource master metadata is held in the large pool of the same database instance.

All GRD Enqueue Resource master metadata is held in the shared pool of the same database instance.

RAC databases have GRD cache resources distributed among all the database instances and stored in the large pool of each instance.

RAC databases have GRD cache resources distributed among all the database instances and stored in the shared pool of each instance.

crsctl stop cluster

crsctl config crs

crsctl disable crs

crsctl stop crs

Cluster resources running on the failed node must be recovered when the node is restarted.

Cluster Resources running on the failed node are relocated to one or more surviving hub nodes.

Cluster Resources running on the failed node are suspended until the node is restarted.

Sessions connected to the failed node could be relocated to one or more surviving nodes.

The node is evicted from the cluster