1z0-076 Exam Study Guide: The Ultimate 2026 Practice Test

The command executed ( CREATE CONFIGURATION 'DGConfig' AS PRIMARY DATABASE IS 'PROD' CONNECT IDENTIFIER IS PROD; ) is used to create a Data Guard Broker configuration named 'DGConfig'. The successful execution of this command depends on several conditions:

A : The DG_BROKER_START parameter must be set to TRUE on the primary database to start the Data Guard Broker processes. Without the broker processes running, the configuration cannot be created.

D : Oracle Net connectivity to the PROD database instance must be established on the primary host. This is because the Data Guard Broker requires network accessibility to communicate with the primary database and manage the configuration.

E : When the configuration is created, the Data Guard Broker configuration files are indeed automatically created in the locations specified by the DG_BROKER_CONFIG_FILEn parameters on the primary database.

It's important to note that the command will not automatically add the PRODSBY1 standby database to the configuration (thus B and C are not correct), and there is no requirement for the standby database to have Oracle Net connectivity defined on the primary host for the execution of this command (making F incorrect as well).

The process of performing a rolling release upgrade in a Data Guard environment using a logical standby database generally involves these steps:

Raise the compatibility level on both databases (1): Ensuring both the primary and logical standby databases are operating with the same and correct compatibility level is essential before starting the upgrade process.

Upgrade the logical standby database (5): Apply the database upgrade to the logical standby first, which allows the primary database to continue serving the workload without interruption.

Restart SQL Apply on the upgraded logical standby database (2): Once the logical standby has been upgraded, SQL Apply must be restarted to apply the redo data from the primary database, which is still running the earlier version.

Perform a switchover to the logical standby database (4): After confirming that the logical standby database is successfully applying redo data, perform a switchover to make it the new primary database.

Upgrade the old primary database (6): With the new primary database now in place, upgrade the old primary database (which is now the new standby) to the new Oracle Database release.