Which two statements are true regarding Data Guard Broker?
A.
It automatically adds the primary database to an existing broker configuration when Enterprise Nlanager Cloud Control is used to create a standby
B.
It automatically starts the DMON process for the database instances that are part of a Data Guard configuration.
C.
it can be used to perform failovers and switchovers.
D.
It can be used to create and manage standby databases.
E.
It can be used to monitor redo transport and log apply services.
B is incorrect, DMON is started by the database, based on the broker_start_true parameter.
C is correct.
D is incorrect, the creation of a standby database is done by rman.
C, E?
Wim J, I think that B is correct:
https://docs.oracle.com/database/121/DGBKR/concepts.htm#DGBKR045
“When you start the Oracle Data Guard broker, a DMON process is created.”
So I think B,C are correct, and because about E, at least me, I haven’t found any documentation about it.
😉
sm, you are right, but documentation is wrong 🙂
tested in labo environment.
As soon you set dg_Broker_start = true, the dmon is started, regardless the instance is in broker configuration or not…
I really hope that the real exam questions have more detail…
Wim, you are right, in documentation “dataguard administration I” says:
“Set the DG_BROKER_START initialization parameter to TRUE. This starts the DMON
process.”
and I also tested in lab environment.
🙂
It’s CE – you are informed about redo/apply lag when inssuing show database query:
DGMGRL> show database mystdby
Database – mystdby
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds (computed 0 seconds ago)
Apply Lag: 0 seconds (computed 0 seconds ago)
Apply Rate: 2.28 MByte/s
Real Time Query: OFF
Instance(s):
dcbdbkaz
Database Status:
SUCCESS
I’m agree with… C and E are correct
Refer – https://docs.oracle.com/database/121/DGBKR/concepts.htm#DGBKR030
1.2 Benefits of Oracle Data Guard Broker
Simplified switchover and failover operations:
Built-in monitoring and alert and control mechanisms:
The broker provides built-in validation that monitors the health of all of the databases in the configuration. While connected to any database in the configuration, you can capture diagnostic information and detect obvious and subtle problems quickly with centralized monitoring, testing, and performance tools.
Both Cloud Control and DGMGRL retrieve a complete configuration view of the progress of redo transport services on the primary database and the progress of Redo Apply or SQL Apply on the standby database.
Simplified, centralized, and extended management:
You can issue commands to manage many aspects of the broker configuration. These include:
•Simplify the management of all components of the configuration, including the primary database, standbys, redo transport services, and log apply services.
•Coordinate database state transitions and update database properties dynamically, with the broker recording the changes in a broker configuration file that includes information about all the databases in the configuration. The broker propagates the changes to all databases in the configuration and their server parameter files.
•Simplify the control of the configuration protection modes (to maximize protection, to maximize availability, or to maximize performance).
•Invoke the Cloud Control verify operation to ensure that redo transport services and log apply services are configured and functioning properly
•Automatically sets up redo transport services and log apply services. Simplifies management of these services, especially in an Oracle RAC environment.
( Table 1-1 Configuration Management With and Without the Broker )
C,E seems to be true
C, E correct