1z0-066 Practice Exam Questions with Answers Oracle Database 12c: Data Guard Administrator Certification

FLASHBACK is automatically enabled when transitioning to the logical standby database.

The Managed Recovery Process (MRPO) continues applying redo up to the SCN immediately preceding the redo corresponding to the LogMiner dictionary build.

Supplemental logging will be enabled on the logical standby database when the physical database is transitioned to the logical standby database.

SQL apply is automatically started when transitioning to the logical standby database.

It will automatically start redo apply.

whether the database at the destination is reached by using a far sync instance

whether the database at the destination is a primary or a standby

whether online redo logs are to be archived at a specific destination

whether standby redo logs are to be archived at a specific destination

whether the database at the source is a primary or a standby

In a broker configuration, the primary database name must match the DB_UNIQUE_NAME value in the database initialization parameter file.

A primary database profile may be added to the configuration prior to creating the primary database.

A standby database profile may be added to the configuration prior to creating that standby database.

A newly created broker configuration requires at least one standby database profile to be specified at the time the configuration is created.

A newly created broker configuration is in the disabled state.

Create a database service on the standby databases; automate the start of the service after a role change, and modify the connection description on the clients to use that service.

Configure a PRIMARY role service on the Primary and Standby and modify the Client connect descriptor to include both Primary and the Standby.

Set the DB_NAME parameter identically on all databases; modify the connection descriptor on the clients to use DB_NAME to connect to the primary database instance.

Set the LOCAL_LISTENER parameter for all the database instances, to register services with the default listener on the primary database host.

It succeeds only if SQL apply is stopped before deleting the SQL Apply filter.

It succeeds but the SQL Apply filters are not deleted.

It deletes both the SQL Apply filters.

It returns an error because the syntax to delete a SQL Apply filter must specify the same object names as specified when the filter was added.

It succeeds only if all DML statements executed on the primary have been applied on the logical standby deleting the SQL Apply filter.

The leading group contains the original primary database.

The trailing group contains the original primary database.

The background process DMON must be enabled on all database instances that take part in the rolling release upgrade process.

At least one logical standby database must be part of the initial Data Guard configuration.

The trailing group can contain standby databases that will protect the original primary database during the rolling release upgrade process.

It backups that are offloaded to a physical standby database are taken when not connected to a recovery catalog, then they may still be used for restoration on the primary database.

The physical standby database may be used to register the database in the recovery catalog, if the primary is not registered.

The primary and physical standby databases must be registered separately in the recovery catalog, if a far sync instance is used to route redo to the physical standby database.

It is not necessary to use a recovery catalog unless a far sync instance is used to route redo to the physical standby database.

Primary and physical standby database may use different virtual recovery catalogs in the same physical recovery catalog.

The target database should be in NOMOUNT state and DGMGRL should be connected to any database that is a member of the configuration.

The target database should be MOUNTED and DGMGRL should be connected to any database that is a member of the configuration.

The target database should be MOUNTED and DGMGRL should be connected to the primary database.

The target database should be MOUNTED and DGMGRL should be connected to the target database.

The target database should be in NOMOUNT state and DGMGRL should be connected to the primary database.

DGMGRL> convert database cats to physical standby;

DGMGRL> convert database sheep to physical standby;

DGMGRL> convert database sheep to physical standby;DGMGRL> convert database cats to physical standby;

DGMGRL>edit configuration set protection mode as maxperformance;DGMGRL> convert database sheep to physical standby;

None, because you can directly failover to a Snapshot Standby Database.

If the former primary database became a logical standby database it will be in mount state.

The new primary database will be open read-write.

The former primary database will always be open.

If the former primary database became a logical standby database it will be open read-write.

If the former primary database became a physical standby database it will always be open read-only.

If the former primary database became a physical standby database it will be in the same state as the former physical standby database.

A recovery catalog is required when RMAN is used to take backups from a logical standby database in a Data Guard configuration if you plan to recover the primary using those backups.

Backups of archived redo logs taken on a physical standby are interchangeable with a primary.

A recovery catalog is required when RMAN is used to take backups from a physical standby database if you plan to recover the primary using those backups.

Backups of control files taken on a physical standby are not interchangeable with a primary.

Backups of data files taken on a physical standby are interchangeable with a primary.