A customer asks for your recommendation regarding this requirement:
1. We plan to have a Data Guard Configuration with one primary database and one physical standby database.
2. We want zero data loss in case of a disaster involving the loss of one component.
3. We want to do Real Application Testing occasionally on the Standby Database.
Which solution, if any, satisfies these requirements?

• A. A snapshot standby database with real time query that can be converted regularly into a physical standby database open read write, to do real application testing
• B. A far sync instance plus a snapshot standby database and real time apply that can be converted regularly into logical standby database to do real application testing
• C. A physical standby database with synchronous redo transport that can be converted regularly into a snapshot standby to do real application testing
• D. These requirements cannot be met.

A Data Guard environment has this configuration and these attributes:
The primary database prima is in the local region.
A physical standby database physt1 is in the local region.
A physical standby database physt2 is in a remote region.
The primary ships redo to physt1.
physt1 ships redo to physt2.
physt1 and physt2 have Real-Time Query enabled.
A sequence has been created with this SQL statement in the primary database:
CREATE SEQUENCE a NOCACHE SESSION;
Which TWO statements are TRUE?

• A. The sequence is usable on physt1 and physt2.
• B. physt2 will no longer receive redo if physt1 becomes unavailable, unless LOG_ARCHIVE_DEST_n has the ALTERNATE attribute specified on physt1.
• C. The sequence is usable on physt1 but not usable on physt2.
• D. The sequence is usable on physt2 if physt1 becomes unavailable, but only if an alternate redo destination has been configured on the primary database.
• E. physt2 will no longer receive redo if physt1 becomes unavailable, unless LOG_ARCHIVE_DEST_n has the ALTERNATE attribute specified on the primary database.

The Oracle database 19c Observer is currently running on host1 and you wish to have it running on host2.
Examine this list of possible steps:
1) Stop the observer on host1
2) Disable Fast-Start Failover
3) Update the broker configuration with the new observer hostname
4) Enable Fast-Start Failover
5) Start the Observer on host2
Which contains the minimum required steps to move the observer to host2?

• A. Execute tasks 1 and 5
• B. Execute only task 5
• C. Execute tasks 1, 3, and 5
• D. Execute tasks 1, 2, 3, 4, and 5

Examine this list of possible steps:
1. Raise the compatibility level on both databases.
2. Restart SQL Apply on the upgraded logical standby database.
3. Start SQL Apply on the old primary database.
4. Perform a Switchover to the logical standby database.
5. Upgrade the logical standby database.
6. Upgrade the old primary database.
Which is the minimum number of steps in the correct order, to perform a rolling release upgrade of a data guard environment using an existing logical standby database and to enable the new functionality?

• A. 1,5,2,4,6,3
• B. 4,6,5,2,3,1
• C. 5,2,4,6,3,1
• D. 5,2,4,1
• E. 5,2,4,3,6,1

Your Data Guard environment has a remote physical standby database with real-time query enabled, which is used for reporting, and a logical standby database used for DSS reporting.
Switchovers or failovers are possible due to testing or in case of a disaster.
Clients use local TNSNAMES.ORA files to define connection strings to the database instances.
Which three will prevent clients from connecting to the wrong database instances?

• A. The LOCAL_LISTENER parameter on the primary database instance must always be set.
• B. A service name is registered with the local listener of each database instance.
• C. Client TNS entries for the databases use the correct service names for the intended service.
• D. The client applications must use the correct TNS entries when requesting connections to the database instances.
• E. The standby database services must be defined statically with the Listeners running on the standby database hosts.
• F. Oracle Net connectivity to the primary database instance must be established on all the standby database instances.
• G. The DB_NAME and DB_UNIQUE_NAME parameters must be set to the same value for all the databases in the Data Guard environment.