Which three can be done using Data Guard Broker?

Oracle Data Guard Broker is a management and monitoring framework that automates and simplifies the administration of a Data Guard configuration. Its key capabilities include simplifying role transitions, such as converting a physical standby to a snapshot standby. A primary function of the Broker is to provide a centralized interface for monitoring and managing the core Data Guard services, including redo transport and log apply. Furthermore, the Broker is essential for implementing high-availability solutions like Fast-Start Failover (FSFO), which automates the failover process to a designated standby database without manual intervention.

A. The Broker manages and monitors an existing Data Guard configuration; it does not perform the initial creation of the physical standby database itself.
B. The initial configuration of standby files (control file, SPFILE, data files) is a prerequisite step performed before the database is added to a Broker configuration.
C. Defining skip rules for a logical standby database is performed using the DBMSLOGSTDBY PL/SQL package, not directly through Data Guard Broker commands.

1. Oracle® Database Data Guard Broker 19c Documentation, Chapter 4, "Managing a Broker Configuration", Section "Converting a Physical Standby to a Snapshot Standby". This section explicitly states, "You can use the DGMGRL CONVERT DATABASE command or Enterprise Manager to convert a physical standby database into a snapshot standby database." (Supports option D).

2. Oracle® Database Data Guard Broker 19c Documentation, Chapter 1, "Introduction to Oracle Data Guard Broker", Section "Oracle Data Guard Broker Benefits". This section details that the Broker simplifies "Managing and monitoring a Data Guard configuration... This includes setting database properties, monitoring the status of the configuration, and controlling the state of each database." (Supports option E).

3. Oracle® Database Data Guard Broker 19c Documentation, Chapter 6, "Enabling Fast-Start Failover". This chapter describes how to "configure the broker's fast-start failover feature so that it will be automatically initiated by the broker when the primary database becomes unavailable." (Supports option F).

4. Oracle® Database Data Guard Broker 19c Documentation, Chapter 3, "Creating a Broker Configuration". The workflow described shows that the standby database must already exist before it can be added to the Broker configuration, invalidating options A and B.

5. Oracle® Database Data Guard Concepts and Administration 19c, Chapter 4, "Managing a Logical Standby Database", Section "Specifying That SQL Apply Skip Certain DML or DDL Statements". This section details the use of the DBMSLOGSTDBY.SKIP procedure, confirming this task is outside the direct command set of the Broker. (Supports why C is incorrect).