1z0-076 Exam Dumps - Oracle Certification Questions and Answers

A corrupt block on the primary database can be automatically recovered, using a block from a standby database with Real-Time Query enabled.

A corrupt block on the primary database is automatically recovered, using a block from a flashback log from a standby database with Real-Time Query enabled.

A corrupt block on a standby database with Real-Time Query enabled, is automatically recovered, using flashback logs from the standby database.

A corrupt block on a standby database with Real-Time Query enabled, can be automatically recovered, using a block from the primary database.

A corrupt block on the primary database is automatically recovered, using a block from a flashback log from the primary database.

Receives redo synchronously from the primary database

Can be created using the RMAN DUPLICATE command

Includes a standby control file, password file, data files, standby redo logs, and archive logs

Can only be created using a series of SQL commands

Applies redo received

The databases should be at least mounted before block comparison.

Logical standby databases can be the target database for the dbms_dbcomp.dbcomp procedure.

It requires that the DB_LOST_WKITE_protect initialization parameter be enabled.

You can monitor the progress of an ongoing block comparison operation by querying VS SES SION_LONGOPS.

It can be used to detect lost writes and inconsistencies between the primary database and the cascaded standbys.

A resize command to reduce the size of an empty datafile in the snapshot standby database, which was created in the primary database, will succeed.

A resize command to reduce the size of an empty datafile in the snapshot standby database, which was created in the snapshot standby database, will succeed.

A resize command to extend the size of a datafile in the snapshot standby database, which was created in the snapshot standby database, will succeed.

A resize command to reduce the size of an empty datafile in the snapshot standby database, which was created in the physical standby database, will succeed.

A resize command to extend the size of a datafile in the snapshot standby database, which was created in the primary database, will succeed.

Create role based services with the si vet] utility when using clusterware for Oracle RAC databases or Oracle Restart for single instance Oracle databases.

Establish Oracle Net connectivity to the primary database instance from all the standby database instances.

Create a static service for each of the databases, register it with the local listener of each database instance, and add connection descriptors on clients to connect to those services.

Create database services on each of the standby databases, start the services, and add connection descriptors on the clients to connect to those services.

Create database services for each database and use event triggers to make sure that services are activated only when the database is in the correct role.

The fastStartFailoverTarget property is not set on Dogs.

The LogxptModr property is set to async on Sheep while Sheep is the target standby database.

The LogXptMode property is set to FASTSYNC on Cats while Sheep is the target standby database.

The LogXptMode property is set to async on Dogs.

The LogXptMode property is set to fastsync on Dogs.

A multi-tenant standby database can have fewer pluggable databases than the primary container database.

Different pluggable databases within a logical standby database may have different guard statuses.

The Data Guard broker automatically opens all pluggable databases of a primary database after a role change operation.

The Data Guard broker automatically always opens the pluggable databases of a standby database after a role change operation.

The CDBDBA privilege must be used instead of the SYSDBA privilege for connections as SYS to the root container of a multi-tenant standby database.

The primary and standby databases must run the same version of the Oracle Database server.

Network connectivity to the primary database instance must be defined on the servers hosting the standby database instances.

DG_BROKEB_START must be set to TRUE for a database instance before adding the database to the broker configuration.

If any database in the configuration is a RAC database, then the broker configuration files must reside in shared storage accessible by all database instances for all databases in the broker configuration.

The broker configuration files for a RAC database must reside in shared storage accessible by all the RAC database instances.

A statically defined listener end-point must be registered with the local listener on the servers hosting the standby database instances.

To enable Real-Time Query on a physical standby database, a TNS entry enabling connectivity to the standby database instance must be defined on the primary database host.

To start SQL Apply on a logical standby database, a TNS entry enabling connectivity to the primary database instance must be defined on the logical standby database host.

A TNS entry enabling connectivity to the primary database instance must be defined on each of the standby database hosts.

A TNS entry or entries enabling connectivity to standby database instance(s) must be defined on the primary database host.

The LOCAL_LISTENER initialization parameter must be set to the listener used to register the primary database instance.

a primary database with one logical standby database

a primary database with two logical standby databases

a primary database with one physical standby database

a primary database with two physical standby databases

A primary database with one logical and one physical standby database