Topic: 1z0-066 topic 1 question 49

Examine the Fast-start configuration:
DGMGRL> show fast_start failover;

Fast-Start Failover: ENABLED -

Threshold : 30 seconds -

Target: sheep -

Observer : 017.example.com -
Lag Limit: 30 seconds (not in use)

Shutdown Primary: TRUE -

Auto-reinstate: TRUE -
Observer Reconnect: (none)

Observer Override: FALSE -
Configurable Failover Conditions
Health Conditions:

Corrupted Controlfile   YES -

Corrupted Dictionary   YES -

Inaccessible Logfile NO -

Stuck Archiver  YES -

Datafile Offline  YES -
Oracle Error Conditions:
(none)
Which three are true?

A.
The observer will initiate a failover when the primary database is unable to produce local archived redo log files.
B.
An automatic failover will be initiated even if the target standby database lags behind the primary.
C.
The observer is running.
D.
A failover may occur if the observer has lost connectivity to the primary database, even if the Fast-Start Failover target standby database has a good connection to the primary database.
E.
The configuration operates in Maximum Availability mode.
F.
The configuration operates in Maximum Performance mode.

Re: 1z0-066 topic 1 question 49

Lag Limit is ignored in Maximum Availability (Not in use message)

Re: 1z0-066 topic 1 question 49

Conditions for FSFO Failover
By default, the observer will initiate failover to the target standby if and only if ALL of the following are true:

observer is running
observer and the standby both lose contact with the primary
Note: if the observer loses contact with the primary, but the standby does not, the observer can determine that the primary is still up via the standby.
observer is still in contact with the standby
durability constraints are met
failover threshold timeout has elapsed

https://www.oracle.com/technical-resources/articles/smiley-fsfo.html

Answer: ACE

Re: 1z0-066 topic 1 question 49

Answer: A, C and E