1Z0-076: Oracle Database 19c: Data Guard AdministrationDemo

By Oracle · Browse Mode
About the Exam

Oracle lists this exam as covering Oracle Data Guard concepts, configuration, management, optimization, and monitoring, with emphasis on data protection, high availability, and disaster recovery. It is aimed at experienced database administrators; Oracle says ideal candidates typically have 4 to 5 years of database administration experience and 2 to 3 years of Data Guard experience. Passing the exam is one requirement for the Oracle Certified Professional, Oracle Database 19c: Data Guard Administrator certification.

Exam Topics

  • Oracle Data Guard Overview20%
  • Creating a Physical Standby Database16%
  • Managing the Redo Transport Services12%
  • Managing Log Apply Services12%
  • Configuring and Managing Oracle Data Guard Broker14%
  • Performing Role Transitions14%
  • Monitoring a Data Guard Configuration12%

How to Use This Practice Exam

  1. Browse — Read each question, select your answer, and reveal the explanation.
  2. Exam Mode — Simulate real exam conditions with a timed session and score report.
  3. Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Get PDF
Learn More

Last updated December 3, 2025 at 2:54 PM

Topic filter
Retired questions
Question sort

QuestionQ1

Performing Role Transitions

Examine the following command, which is run on a physical standby database to convert it to a logical standby database:

SQL> ALTER DATABASE RECOVER TO LOGICAL STANDBY prodlgsby;

Which two statements are true about executing this command?

Choose two
  • A The Managed Recovery Process (MRP0) continues applying redo data to the physical standby database until it is ready for conversion to a logical standby database.
  • B SQL apply is automatically started when transitioning to the logical standby database.
  • C Supplemental logging will be enabled on the logical standby database when the physical standby database is transitioned to the logical standby database.
  • D The DBID of the database is changed.
  • E FLASHBACK is automatically enabled when transitioning the logical standby database.
  • F It will automatically start redo apply.
Explanation

ALTER DATABASE RECOVER TO LOGICAL STANDBY continues applying redo on the physical standby until the required LogMiner dictionary is located, which is performed by managed recovery. Without the KEEP IDENTITY clause, the conversion also changes the database DBID. SQL Apply is started separately after conversion; supplemental logging and Flashback are not automatically enabled by this statement.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Configuring and Managing Oracle Data Guard Broker

Which three conditions are required before using Data Guard Broker?

Choose three
  • A A statically defined listener end-point must be registered with the local listener on the servers hosting the standby database instances.
  • B Network connectivity to the primary database instance must be defined on the servers hosting the standby database instances.
  • C The primary and standby databases must run the same version of the Oracle Database server.
  • D The broker configuration files for a RAC database must reside in shared storage accessible by all the RAC database instances.
  • E If any database in the configuration in a RAC database, then the broker configuration files must reside in shared storage accessible by all database instances for all databases in the broker configuration.
  • F DG_BROKER_START must be set to TRUE for a database instance before adding the database to the broker configuration.
Explanation

Data Guard Broker requires the primary and standby databases to run the same Oracle Database version. DG_BROKER_START must be set to TRUE before a database participates in the broker configuration. For an Oracle RAC database, the DG_BROKER_CONFIG_FILEn parameters must reference the same shared broker configuration files for every instance of that RAC database; this requirement does not apply to non-RAC databases elsewhere in the configuration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Monitoring a Data Guard Configuration

Which TWO statements are correct about block media recovery in a Data Guard environment?

Choose two
  • A DB_LOST_WRITE_PROTECT must be set to TYPICAL to enable Automatic Block Media Recovery.
  • B A corrupt block on the primary database can be recovered automatically, using blocks from a physical standby database that has Real-Time Query enabled.
  • C When using RMAN, the RECOVER CORRUPTION LIST command can use blocks from block change tracking files..
  • D DB_LOST_WRITE_PROTECT must be set to FULL to enable Automatic Block Media Recovery.
  • E When using RMAN, the RECOVER CORRUPTION LIST command can use blocks from block change tracking files.
Explanation

Automatic Block Media Recovery in a Data Guard configuration lets the primary database automatically retrieve an uncorrupted copy of a data block from a physical standby database that is open in real-time query (Active Data Guard) mode, transparently repairing the corruption without manual RMAN intervention. Enabling this automatic repair additionally depends on setting the DB_LOST_WRITE_PROTECT initialization parameter to TYPICAL on both the primary and standby databases, which activates the redo-based block validation needed to detect and safely correct corrupt or lost-write blocks; FULL is not the documented setting required to enable this feature.

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

Oracle Data Guard Overview

You need to propose an Oracle Data Giard configuration for a database that supports an OLTP workload and meets these permanent requirements:

  1. Data loss is not allowed.
  2. Read-only applications must not connect to the primary database instance.

Additionally, the following requirements exist, with only one ever performed at a time:

  1. It must be possible to apply and test designated patches with minimal downtime.
  2. An upgrade to a new database release must be performed with the least possible downtime.
  3. New application software releases must be tested against an exact, up-to-date replica of the production database.

You propose a primary database with one physical database configured in Maximum Protection mode.

Which requirements are met?

  • A 1 and 2
  • B 1, 2, 3, 4, and 5
  • C only requirement 5
  • D only requirement 1
  • E 2, 3, 4, and 5
  • F 1, 2, and 4
Explanation

Maximum Protection guarantees no data loss when the primary fails, and a physical standby can be opened for read-only access to offload queries from the primary. With only that single physical standby, the configuration cannot preserve Maximum Protection while using the standby as a snapshot or transient logical standby for general patch testing, rolling release upgrades, or writable application-release testing. A snapshot standby also cannot be the only standby in a Maximum Protection configuration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Oracle Data Guard Overview

Which three statements are accurate about snapshot standby databases?

Choose three
  • A A logical standby database can be converted into a snapshot standby database.
  • B Tables can be dropped.
  • C The FAILOVER TO command results in a transition of a snapshot standby database to the primary role.
  • D The SWITCHOVER TO command allows a switchover operation to a snapshot standby database.
  • E Tablespaces can be created.
  • F Tablespaces can be dropped.
Explanation

A snapshot standby database is opened read-write and is fully updatable, permitting operations such as dropping tables and creating tablespaces. It can be the target of a manual FAILOVER TO operation; the broker converts it to a physical standby, applies accumulated redo, and transitions it to the primary role. A switchover to a snapshot standby is not allowed, and a dropped tablespace’s data file cannot be restored by Flashback Database.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!
Know a question that should be here? Contribute to this exam
Back home