What are three characteristics of the Data Guard Broker? (Choose three.)
A.
It runs as a process called DMON
B.
It can be controlled through the Data Guard Manager GUI and command-line interface
C.
It is started by setting the DRS_START parameter to TRUE in your initialization file
D.
It uses a configuration file stored on the primary database server and, optionally, on one of your standby database servers
Explanation:
A – TRUE. The Data Guard monitor process (DMON) is an Oracle background process that runs for every database instance that is managed by the broker. When you start the Data Guard broker, a DMON process is created.B – TRUE. You can perform all management operations locally or remotely through the broker’s easy-to-use interfaces: the Data Guard management pages in Oracle Enterprise Manager, which is the broker’s graphical user interface (GUI), and the Data Guard command-line interface called DGMGRL.
Obs.: The right parameter should be DG_BROKER_START. The DRS_START initialization parameter has been deprecated in favor of the new parameter
DG_BROKER_START, since 9iR2 (Metalink Note: 208768.1)C – TRUE. The DG_BROKER_START initialization parameter must be set to TRUE for each database to start the DMON processes. By default, the DG_BROKER_START initialization parameter is set to FALSE. However, you can set the value in the following ways:
* If you are using Oracle Enterprise Manager, it automatically sets the DG_BROKER_START initialization parameter to TRUE for new standby databases that it creates.
* If you are using DGMGRL, you must explicitly set the DG_BROKER_START initialization parameter to TRUE; otherwise, the DMON process will not start. You can set the DG_BROKER_START initialization parameter with the following SQLstatement:
SQL> ALTER SYSTEM SET DG_BROKER_START=TRUE;D – FALSE. The DG_BROKER_START initialization parameter must be set to TRUE for each database
REF: Oracle(r) Data Guard Broker, 1-10, 1-2 and 3-6