Which three statements are true about ASM performance and scalability?

Question

Options

• ADisks in a diskgroup may be of varying speed and capacity without affecting performance.
• BDisks in a diskgroup should match in speed and capacity for best performance.
• CA database seldom needs more than two diskgroups: one for data and the other for a fast
• DA database needs a separate diskgroup for each major tablespace, redo logs, and fast recovery
• EMultiple databases that use the same diskgroup make the best use of space.
• FMultiple databases that use a separate diskgroup for each database make the best use of space.

• A
  14% (8)
• B
  79% (46)
• D
  2% (1)
• F
  5% (3)

Explanation

Performance, Scalability, and Manageability Considerations for Disk Groups Create separate disk groups for database files and fast recovery area. Disks in a disk group should have the same size and performance characteristics. - Allows the disk group to deliver consistent performance - Allows ASM to use disk space most effectively - Allows operations with different storage requirements to be matched with different disk groups effectively Using separate disk groups for each database as opposed to having multiple databases in a disk group has various benefits and drawbacks. Housing multiple databases in a single disk group affords the most efficient use of space. However, any faults or maintenance that affects the disk group may affect many databases. Separate disk groups provide greater isolation from the effects of a fault or maintenance operation. However, to achieve this may consume more disk space and may require more disk group maintenance to balance disk resources. Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 8 - 37

No community discussion yet for this question.