UUS Practice Tests⌕ Search
IT Certifications · 1Z0-076

Oracle Database 19c: Data Guard Administration Exam Practice Test

Oracle Database 19c Data Guard administration centers on maintaining a standby database that can support availability and recovery goals. The practice material addresses redo transport and application, archive destination monitoring, standby roles and open states, and configuration choices for physical and logical standbys. These concepts help administrators assess whether a standby is receiving and applying changes as expected.

Exam overview

Exam providerOracle
Exam code1Z0-076
CategoryIT Certifications

About the Oracle Database 19c: Data Guard Administration Exam

Data Guard administration requires distinguishing redo that has arrived at a standby from redo that has been applied, then investigating gaps or delays before they affect recovery readiness. Administrators inspect database and archive-destination status, interpret errors, and understand how transport settings such as REOPEN influence retries. Physical standby configuration includes matching datafile and log file names when primary and standby paths differ, while FAL_SERVER relates to fetching missing archived redo. Standby redo logs support redo reception, and archive log deletion policies must account for standby needs so required logs are not removed prematurely. Role and open-mode checks help confirm whether a database is primary or a physical standby and how it is operating. Practice scenarios can build skill in connecting these settings and status indicators to operational decisions.

Sample Practice Questions

Review a selection from this exam's published US Practice Tests practice bank.

Question 1

Which view is commonly queried on a database to inspect the status and error information for configured archive destinations?

  1. AV$ARCHIVE_DEST_STATUS
  2. BDBA_USERS
  3. CV$SESSION_WAIT
  4. DDBA_TABLESPACES
Show answerCorrect answer: A

V$ARCHIVE_DEST_STATUS reports runtime status information for archive destinations, including destination state and relevant error details.

Question 2

What is the purpose of the DB_FILE_NAME_CONVERT parameter in a physical standby setup when primary and standby datafile paths differ?

  1. AIt maps primary datafile names to corresponding standby file names during file creation or recovery operations.
  2. BIt translates database usernames between sites.
  3. CIt changes archived redo sequence numbers.
  4. DIt maps listener service names to IP addresses.
Show answerCorrect answer: A

DB_FILE_NAME_CONVERT provides filename mapping patterns for datafiles between primary and standby locations when their paths differ. Other file-management approaches may be appropriate depending on the configuration.

Question 3

What is the primary purpose of the LOG_FILE_NAME_CONVERT initialization parameter in a physical standby configuration?

  1. ATo map primary online redo log filenames to corresponding standby filenames
  2. BTo set the maximum size of archived redo logs
  3. CTo translate service names used for redo transport
  4. DTo choose the location of the standby control file
Show answerCorrect answer: A

LOG_FILE_NAME_CONVERT provides filename pattern mappings for online redo log files between primary and standby. It does not configure archive-log sizing, network naming, or control-file location.

Question 4

Which statement about a logical standby database is correct?

  1. AIt applies changes by executing SQL reconstructed from redo, allowing it to remain open for read-write activity subject to restrictions.
  2. BIt applies redo only by restoring primary datafile copies after every log switch.
  3. CIt cannot be opened while SQL Apply is running.
  4. DIt requires every primary table to have a matching bitmap index.
Show answerCorrect answer: A

A logical standby uses SQL Apply to transform redo into SQL changes and apply them to its own database objects. It can support read-write activity for eligible objects, but SQL Apply and object support have restrictions.

Question 5

What is the purpose of the FAL_SERVER initialization parameter on a physical standby?

  1. AIt identifies a server from which the standby can request missing archived redo logs.
  2. BIt selects the standby database's default temporary tablespace.
  3. CIt sets the maximum number of redo apply workers.
  4. DIt defines the destination for RMAN backup pieces.
Show answerCorrect answer: A

FAL_SERVER provides the Oracle Net service name of a FAL server that can supply archived redo logs requested by a standby when a gap is detected.

Question 6

Why should archive log deletion policies be coordinated with Data Guard requirements?

  1. ATo avoid deleting redo needed by a standby or required for recovery before it is safe to remove
  2. BTo make the standby use a different database character set
  3. CTo force every standby to become a snapshot standby after each log switch
  4. DTo ensure that the listener automatically registers all archive destinations
Show answerCorrect answer: A

A deletion policy can preserve archived redo until relevant standby or recovery requirements are met. Removing logs too early can make gap resolution or recovery more difficult or impossible without another source of the missing redo.

Question 7

A Data Guard administrator needs to determine whether a standby is in the PRIMARY or PHYSICAL STANDBY role and whether it is open. Which view provides this information?

  1. AV$DATABASE
  2. BV$ARCHIVE_DEST
  3. CV$LOG_HISTORY
  4. DV$SESSION
Show answerCorrect answer: A

V$DATABASE includes database role and open-mode information, including DATABASE_ROLE and OPEN_MODE. The other views focus on destinations, log history, or sessions.

How to use this practice test

The free practice bank contains 50 questions; each session presents up to 20 questions selected at random. Use a session to test your understanding of redo transport, standby configuration, and status interpretation, then review the results to identify concepts that need further attention.

Preparation tips

  • Compare received and applied redo progress when diagnosing a standby that appears behind, and identify what each status indicates before choosing a response.
  • Practice interpreting archive destination status and error information, including how the REOPEN attribute affects retry behavior.
  • Work through physical standby path-mapping examples using DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT; distinguish datafile paths from log file paths.
  • Trace how FAL_SERVER, standby redo logs, and archive log deletion policies affect redo continuity and standby recoverability.
  • Use role and open-state information to distinguish a primary database from a physical standby, and relate that status to its current operational role.
Official sourceOfficial exam page ↗