Oracle Database 19c: Data Guard Administration Intermediate Practice Exam: Medium Difficulty 2025

Your production database is configured with a physical standby database in MAXIMUM PERFORMANCE mode. After a network outage, the primary database shows a 2-hour lag in redo transport. The DBA_DATAGUARD_STATUS view shows 'ORA-16191: Primary log shipping client not logged on standby'. What is the MOST likely cause and solution?

A database administrator needs to perform a switchover from the primary database to a physical standby database using SQL commands (not the Data Guard Broker). The standby database is synchronized and ready. What is the correct sequence of steps?

Your Data Guard environment has a primary database and two physical standby databases. You want to offload reporting queries to one standby while keeping the other for disaster recovery with minimal lag. How should you configure the environment?

During a routine check, you notice that the primary database parameter LOG_ARCHIVE_DEST_2 is configured with SYNC AFFIRM transport mode, but the Data Guard protection mode is set to MAXIMUM PERFORMANCE. What will be the actual behavior of redo transport?

After a network failure at the standby site, automatic gap resolution is not working. You query V$ARCHIVE_GAP on the standby database and identify missing archive logs 150-158. The primary database still has these archive logs on disk. What should you do to resolve the gap?

You are configuring a new Data Guard environment with one physical standby. The primary database has 4 online redo log groups with 2 members each, each log file sized at 1GB. How should you configure standby redo logs (SRLs) on the primary database for optimal performance and protection?

A failover operation was performed due to primary database failure. After repairing the old primary database, you attempt to reinstate it as a physical standby but receive 'ORA-19573: cannot obtain exclusive enqueue for datafile'. What is the most likely cause and solution?

Your environment uses MAXIMUM AVAILABILITY protection mode. During peak hours, you notice that commit performance on the primary database has degraded significantly. Investigation shows the standby database's RFS process is experiencing I/O delays writing to standby redo logs. What is the BEST approach to improve commit performance while maintaining data protection?

You need to apply a critical security patch to both primary and physical standby databases in your Data Guard configuration. The patch requires database downtime. What is the recommended approach to minimize overall downtime?

Your Data Guard Broker configuration shows 'Warning: ORA-16809: multiple warnings detected for the member' for the standby database. Upon investigation, you find that the standby has applied all available redo but shows a transport lag of 45 minutes, while the apply lag is 0 seconds. The primary database shows LOG_ARCHIVE_DEST_2 status as 'VALID'. What is the most likely explanation?