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 ControlfileYES - Corrupted DictionaryYES - Inaccessible Logfile NO - Stuck ArchiverYES - Datafile OfflineYES - Oracle Error Conditions: (none) Which three are true? 

Answer options:

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.

ACE

A: Stuck Archiver: YES - Archiver is unable to archive a redo log because the device is full or unavailable. C: Observer : 017.example.com - E: The FastStartFailoverLagLimit configuration property is only used by the broker when enabling fast-start failover for configurations operating in maximum performance mode. References: docs.oracle.com/cd/E11882_01/server.112/e40771/sofo.htm