You must configure an Oracle Data Guard environment consisting of:
1. A primary database
2. Three Physical Standby Databases
You must meet these requirements:
1. A designated physical standby database should become the primary database automatically whenever the primary database fails.
2. The chosen protection mode should provide the highest level of protection possible without violating the other requirement.
Which redo transport mode and protection mode would you configure to meet these requirements?

• A.SYNC NOAFFIRM and Maximum Protection
• B.SYNC NOAFFIRM and Maximum Availability
• C.ASYNC and Maximum Performance
• D.SYNC AFFIRM and Maximum Availability
• E.SYNC AFFIRM and Maximum Protection

Comment: *

Name: *

Email: *

Verification: *

Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration -Animals
Protection Mode: MaxAvailability
Databases:
dogs- Primary database
cats- Snapshot standby database
sheep- Snapshot standby database
Fast-Start Failover: DISABLED
Configuration Status:
ORA-01034: ORACLE not available
ORA-16625: cannot reach database "dogs"
DGM-17017: unable to determine configuration status
You wish to perform a failover to Sheep.
Which command, or sequence of commands, should you issue to the broker before executing "failover to sheep", using the broker?

• A.DGMGRL> convert database cats to physical standby;
• B.DGMGRL> convert database sheep to physical standby;
• C.DGMGRL> convert database sheep to physical standby;
  DGMGRL> convert database cats to physical standby;
• D.DGMGRL>edit configuration set protection mode as maxperformance;
  DGMGRL> convert database sheep to physical standby;
• E.None, because you can directly failover to a Snapshot Standby Database.

Comment: *

Name: *

Email: *

Verification: *

Examine the Data Guard configuration:
DGMGRL> show configuration;
Configuration Animals
Protection Mode: MaxAvailability
Databases:
dogs Primary database
cats Physical standby database
sheep Logical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
Which three will be true after a switchover to Sheep? (Choose three.)

• A.Cats will be an enabled physical standby database.
• B.Dogs will be an enabled logical standby database.
• C.Sheep will be the primary database.
• D.Dogs will be a disabled logical standby database.
• E.Cats will be a disabled physical standby database.

Comment: *

Name: *

Email: *

Verification: *

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?

• 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)'; EDIT CONFIGURATION SET PROTECTION MODE AS MAXAVAILABILITY;

Correct Answer: 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

Comment: *

Name: *

Email: *

Verification: *

Examine this list of possible steps:
1 Raise the compatibility level on both databases
2 .Restart SQL Apply on the upgraded logical standby database
3 Start SQL Apply on the old primary database.
4 . Perform a Switchover to the logical standby database
5 . Upgrade the logical standby database.
6 . Upgrade the old primary database.
Which is the minimum number of steps in the correct order, to perform a rolling release upgrade of a data guard environment using an existing logical standby database and to enable the new functionality?

• A.5,2,4,6,3,1
• B.5,2,4,1
• C.5,2.4,3,6,1
• D.1,5,2,4,6,3
• E.4,6,5,2,3,1

Comment: *

Name: *

Email: *

Verification: *