Free Oracle 1z0-076 Practice Exam with Questions & Answers | Set: 3

The command will execute successfully only if the DG_BROKER_START initialization parameter is set to TRUE for the PROD database instance.

The PRODSBY1 standby database is automatically added to the configuration if DG_BROKER_START is TRUE for PRODSBYl.

The PRODSBYI standby database is automatically added to the configuration if Oracle Net connectivity to the PRODSBYl database instance is defined on the primary host.

The command will execute successfully only if Oracle Net connectivity to the PROD database instance is defined on the primary host.

The Data Guard Broker configuration files is automatically created in the destinations specified by the DG_BROKER_CONFIG_FILEn initialization parameters on the primary database.

The command will execute successfully only if Oracle Net connectivity to the PROD and PRODSBYl database instances are defined on the primary host.

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.

A failover may occur if the observer has lost connectivity to the primary database, even if the Fast-Start Failover target standby database has a good connection to the primary database

If South_Sales develops a problem and cannot be the target of a failover, the broker automatically changes the fast-start failover target to one of the other candidate targets.

The observer will initiate a failover when the primary database is unable to produce local archived redo log files.

You must disable fast-start failover first to change the fast-start failover target to East sales.

The observer is running.

The compatible parameter on a standby database that is applying redo, must be equal to or greater than the compatible parameter on the primary that is shipping redo to that standby.

Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a logical standby database.

Modifications to the data dictionary on the primary database caused by the upgrade, are applied on a physical standby database.

During the upgrade of a logical standby database, standby redo log files must reside on O/S file systems.

User equivalence must be established for the owner of the Oracle software on the affected hosts prior to the upgrade.

Force Logging Mode is not required for a primary database but is recommended.

The Primary Database can operate in noarchivelog mode.

A Logical Standby Database can be in MOUNT state while applying changes.

Databases in a Data Guard Configuration need not operate in Flashback Logging mode.

A primary database may ship redo directly to more than nine standby databases.

When a flashback database operation is performed on a primary database, a physical standby database is also flashed back automatically.

You can use it when real-time apply is enabled in case the phylt may not be used to flash back a primary database after a failover to a logical standby.

It may be used to flash back a physical standby that receives redo from a far sync instance.

You can use it when real-time apply is enabled in case the physical standby suffers from logical corruption.

It may not be used to flash back a primary database after a failover to a physical standby.

When a flashback database operation is performed on a primary database, a logical standby database is also flashed back automatically.

A physical standby database with synchronous redo transport and Real-Time Query enabled.

A physical standby database with asynchronous redo transport and Real-Time Query enabled.

A logical standby database with synchronous redo transport and redo apply on.

A logical standby database with synchronous redo transport and SQL apply on.

A logical standby database with asynchronous redo transport and SQL apply on.

Performing transportable tablespaces

Adding or dropping a redo file group

Adding a data file or creating a tablespace

Creating a PDB from the existing PDB within the same CDB

Renaming a data file in the primary database

It provides a disaster-recovery solution with switchover and failover options that can recover any data updated on the primary database.

It can be used for reporting workloads requiring additional indexes or materialized views or both.

It can be used for testing patchsets without affecting the primary database.

It can be used for database rolling release upgrades.

It can be used to replicate a single pluggable database (PDB) in a multitenant container database.

It can be used as an updatable database for Real Application Testing and then converted back to a standby database without affecting the updates.

Ensure that supplemental logging is enabled on the primary database.

Ensure that no ROWID data types are contained in the primary database.

Ensure that no BFILE LOB data types are contained in the primary database.

Do not perform any nologging operations on the primary.

Ensure that flashback is enabled on the primary database.