Examine the Data Guard configuration: DGMGRL> show configuration; Configuration - Animals Protection Mode: MaxAvailability Databases: dogs - Primary…

A failover operation can only target a physical or logical standby database. A snapshot standby database is open in read-write mode and is not actively applying redo, making it ineligible to become a primary database directly. Therefore, before initiating a failover to the 'sheep' database, it must first be converted from a snapshot standby back into a physical standby. This action reverts the database to a mounted state and begins the process of applying all the redo that was archived while it was a snapshot standby.

B: The goal is to failover to 'sheep', so converting 'cats' is an irrelevant action for this specific task. C: Changing the protection mode is not a prerequisite for converting the standby or for the failover itself. The broker manages protection levels during role transitions. D: This is incorrect as the target for failover is 'sheep', not 'cats'. E: This is incorrect. A direct failover to a snapshot standby is not supported; it must be converted to a physical or logical standby first.

1. Oracle Database 19c, Data Guard Broker, Chapter 5, "Performing a Failover". The prerequisites for failover state that the target must be a physical or logical standby.

2. Oracle Database 19c, Data Guard Broker, Chapter 4, "CONVERT DATABASE". The documentation describes the command used to change a database's role, including from snapshot standby to physical standby.