1Z0-485 · Question #21
Which is a best practice for High Availability (HA) in an Exadata environment?
The correct answer is C. Oracle Exadata Storage Server Software HARD checks operate transparently after enabling. Exadata storage cells include Oracle Hardware Assisted Resilient Data (HARD) to provide a unique level of validation for Oracle block data structures such as data block address, checksum. and magic numbers prior to allowing a write to physical disks. HARD validation with…
Question
Which is a best practice for High Availability (HA) in an Exadata environment?
Options
- AChecksums performed on the Exadata Storage Server ensure logical consistency of block
- BWhen a standby database is in place, DB_BLOCK_CHECKING is not required and thus not
- COracle Exadata Storage Server Software HARD checks operate transparently after enabling
- DDue to the different architecture that Exadata has with storage servers, compared to regular
- EStretched RAC is the best alternative for Exadata that combines both HA and DR into one.
How the community answered
(36 responses)- A17% (6)
- B3% (1)
- C72% (26)
- D8% (3)
Explanation
Exadata storage cells include Oracle Hardware Assisted Resilient Data (HARD) to provide a unique level of validation for Oracle block data structures such as data block address, checksum. and magic numbers prior to allowing a write to physical disks. HARD validation with Exadata is automatic (setting DB_BLOCK_CHECKSUM is required to enable checksum validation). The HARD checks transparently handle all cases including Oracle ASM disk rebalance operations and disk failures. Not A: The checksum is used to validate that a block is not physically corrupt, detecting corruptions caused by underlying disks, storage systems, or I/O systems. Checksums do not ensure logical consistency of the block contents. Not B: MAA recommends that you set DB_BLOCK_CHECKING=MEDIUM or FULL on the physical standby as a minimum practice to prevent the standby from various logical block Not D: The recommendation is: On the primary database: DB_LOST_WRITE_PROTECT=TYPICAL (default TYPICAL on Exadata) On the Data Guard Physical Standby Database: DB_LOST_WRITE_PROTECT=TYPICAL Not E: Protection from a broad range of, but not all While not a full disaster recovery (DR) solution, an Extended Distance Oracle RAC or Oracle RAC One Node deployment will provide protection from a broad range of disasters. For a full DR protection Oracle recommends deploying an Oracle RAC together with a local and a remote Oracle Data Guard setup as described in the Maximum Availability Architecture (MAA).
Topics
Community Discussion
No community discussion yet for this question.