A customer has these requirements for their potential Data Guard implementation: 1. Zero data loss must still be guaranteed through the loss of any one configuration component. 2. The primary database must be protected against a regional disaster. 3. Performance overheads on the primary should be minimized as much as possible given these requirements. 4. Downtime on the primary database for any reason must be kept to a minimum. Components referred to in the broker commands are: 

Which Data Guard broker commands are needed to implement these requirements? 

Answer options:

A. EDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: physt1, FASTSYNC); EDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 SYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt2 SYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
B. EDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 ASYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt FASTSYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXPROTECTION
C. EDIT DATABASE prima SET PROPERY REDOROUTES= (LOCAL: fs1 SYNC); EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES= (prima: physt ASYNC); EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;
D. EDIT DATABASE prima SET PROPERY REDOROUTES=’ (LOCAL: physt1, FASTSYNC)’; EDIT DATABASE prima SET PROPERY REDOROUTES=’ (LOCAL: fs1, FASTSYNC)’; EDIT FAR_SYNC fs1 SET PROPERTY REDORUOTES=’ (prima: physt2 ASYNC)’;

A

The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC or SYNC NOAFFIRM. Note: Fast Sync is a new Data Guard capability available with Oracle Database 12c. Fast Sync enables use of the destination parameter NOAFFIRM which specifies that the standby acknowledge receipt of redo without waiting for the write to the standby redo log file to complete. Fast Sync can improve application response time in a SYNC configuration by removing remote I/O from the total round trip time. Active Data Guard Far Sync Architecture 

Incorrect Answers: B: There is no keyword FASTSYNC. To configure fast sync you use SYNC NOAFFIRM. C: The route between fs1 and physical standbase in the remote region, like physt, should be SYNC, not ASYNC. D: The route between fs1 and physical standbase in the remote region, like physt2, should be SYNC, not ASYNC. References: http://www.oracle.com/technetwork/database/availability/farsync-2267608.pdf