Which two are true about database roles in an Oracle Data Guard Configuration?
A.
a configuration consisting only of a primary and one or more physical standby databases can support a rolling release upgrade.
B.
A Logical Standby Database can be converted to a Snapshot Standby Database.
C.
A Logical Standby Database can cascade redo to a terminal destination
D.
A Snapshot Standby Database can be a fast-start failover target
E.
A Physical Standby Database can be converted into a Logical Standby Database.
B is incorrect, snapshot standby is only available for physical stby
C is correct: https://docs.oracle.com/cd/B19306_01/server.102/b14239/cascade_appx.htm#g639625
C, E
seems that C is wrong:
Cascading has the following restrictions:
• Only physical standby databases can cascade redo.
• Real-time cascading requires a license for the Oracle Active Data Guard option.
• Non-real-time cascading is supported on destinations 1 through 10 only. (Real-time cascading is supported on all destinations.)
https://docs.oracle.com/database/121/SBYDB/log_transport.htm#SBYDB5123
A,E
A is true in that sense that we can convert a physical standby to a logical standby.
C can be true, but the logical will send its own redo instead of the primary redo.
To reduce the load on your primary system, you can implement cascaded destinations, whereby a standby database receives its redo data from another standby database, instead of directly from the primary database. You can configure:
A physical standby database to retransmit the incoming redo data it receives from the primary database to other remote destinations in the same manner as the primary database
A logical standby database (because it is open in read/write mode) to send the redo data it generates (after filtering and applying the redo data it receives from the primary database) to its own set of standby (physical or logical) databases
AE is correct.
in short: A & C
i think A is referencing to DBMS_ROLLING (https://docs.oracle.com/database/121/SBYDB/dbms_rolling_upgrades.htm) and since the technical requirements are met, A is correct.
B is not possible – a snapshot standby is always based on a physical standby (https://docs.oracle.com/database/121/SBYDB/manage_ps.htm#SBYDB4801)
C is incorrect – only a physical standby can cascade the transport (https://docs.oracle.com/database/121/SBYDB/log_transport.htm#SBYDB5122)
D is incorrect – only physical or logical standby’s can be target of FSO (https://docs.oracle.com/database/121/DGBKR/sofo.htm#DGBKR3402)
E is correct (https://docs.oracle.com/database/121/SBYDB/create_ls.htm#SBYDB4737)
You mean A & E given C is incorrect, right?
I think the capture of the question is bad, because the B could be PHYSICAL , then you must pay attention in exam, if the b) or C) literal is physical rather than Logical, then these could be the right answer, but actually A Y E seems the correct answer.
thanks
A,E
A,E
A and E
D is correct: https://docs.oracle.com/database/121/DGBKR/sofo.htm#GUID-995CED84-BEA1-4675-9C68-B37CB996924F
it states: Fast-start failover can be enabled in maximum availability mode when the fast-start failover target is a logical or physical standby database that receives redo data from a far sync instance. This lets you take advantage of the broker’s automatic failover feature in configurations set up for zero data loss protection at any distance.
Although option A is possible, the MOST CORRECT scenario would have a logical standby