1Z0-066 試験問題を無料オンラインアクセス

Examine the Data Guard configuration:
DGMGRL> show configuration verbose;
Configuration - Animals
Protection Mode: MaxPerformance
Databases:
cats - Primary database
dogs - (*) Physical standby database
sheep - Physical standby database
(*) Fast-Start Failover target
Properties:
FastStartFailoverThreshold = '30'
OperationTimeout = '30'
TraceLevel = 'USER'
FastStartFailoverLagLimit = '30'
CommunicationTimeout= '180'
ObserverReconnect= '10'
FastStartFailoverAutoReinstate= 'FALSE'
FastStartFailoverPmyShutdown= 'TRUE'
BystandersFollowRoleChange= 'none'
ObserverOverride = 'FALSE'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: dogs
Observer: ol5.example.com
Lag Limit: 30 seconds
Shutdown Primary:TRUE
Auto-reinstate: FALSE
Observer Reconnect: 10 seconds
Observer Override: TRUE
Configuration Status:
SUCCESS
Which two are true? (Choose two.)

• A.The observer will detect if the primary database is unable to accept new connections.
• B.The former primary database will not be reinstated automatically after a failover.
• C.The observer must run on host ol5.example.com and is currently not running.
• D.The observer will reinstate Sheep automatically after a failover, if required.
• E.The observer will mark another standby database as the failover target if the original failover target becomes unavailable.

Which two are prerequisites for configuring flashback database for Oracle 12c databases, in a Data Guard environment? (Choose two.)

• A.A flash recovery area must be configured.
• B.The database must be in ARCHIVELOG mode.
• C.The database must be in MOUNT state.
• D.The Data Guard Broker must be used.
• E.A far sync instance must be configured to flash back a standby when the primary has been flashed back.

Which three are true concerning restoring of RMAN backups to primary and physical standby databases in a Data Guard environment? (Choose three.)

• A.Backups of control files taken on the primary database may not be restored and used on a physical standby database.
• B.Backups of SPFILEs taken on a physical standby database may not be restored on the primary database.
• C.Backups of data files taken on the primary database may be restored on a physical standby database.
• D.Backups of data files taken on a physical standby database may be restored on a primary database.
• E.Backups of control files taken on a physical standby database may be restored on the primary database.
• F.Backups of SPFILEs taken on the primary database may not be restored and used on a physical standby database.

You must propose an Oracle Data Guard configuration for a database supporting a DSS workload that meets these permanent requirements:
1. The performance impact on the primary database should be kept to a minimum.
2. Creating and maintaining materialized views should not impact the performance of the primary database.
Additionally, there are these requirements, only the one of which is ever done at any one time:
3. It should be possible to apply designated patches with a minimum amount of downtime.
4. Upgrading to a new database release should be performed with the least possible amount of downtime.
5. New application software releases should be tested against an exact up-to-date replica of the production database.
You propose a configuration operating in Maximum Performance mode with a primary database and one logical standby database.
Which requirements do you meet?

• A.2, 3, and 5
• B.2 and 5
• C.1, 2, and 4
• D.1 and 5
• E.1, 2, 3, 4, and 5
• F.1, 2, and 3

Your expertise is requested for these customer requirements:
1. The Data Guard environment must be in maximum protection mode.
2. Reports must be offloaded to a physical standby database.
3. There must be no lag between the primary and standby databases that affect the reports produced.
4. The primary database must be resilient in case of a single network failure.
Which solution is correct for these requirements?

• A.two standby databases, at least one of them a physical standby with Real-Time Query enabled and the STANDBY_MAX_DELAY parameter set to zero, receiving redo from the primary with asynchronous transport
• B.one physical standby database with Real-Time Query enabled, receiving redo from two Far Sync instances that are connected the primary
• C.two physical standby databases with Real-Time Query enabled, receiving redo from the primary with the LOG_ARCHIVE_DEST_n attributes SYNC NOAFFIRM to minimize the performance impact on the primary
• D.one physical standby database with Real-Time Query enabled and the
  STANDBY_MAX_DATA_DELAY parameter set to zero, receiving redo from the primary with synchronous transport
• E.two standby databases, at least one of them a physical standby with Real-Time Query enabled and the STANDBY_MAX_DATA_DELAY parameter set to zero, receiving redo from the primary with synchronous transport