What are two choices that a customer must make that impact diskgroup creation?

What are two choices that a customer must make that impact diskgroup creation?

A.
What is the level of redundancy required?

B.
What OS will be run?

C.
Where will disk backups be written?

D.
How many databases will run on the cluster?

Explanation:
B: There are a number of ASM disk group attributes that you can set when creating
your disk groups, but the followingare the most important:
* (B) compatible.rdms: Set this to the software version of your RDBMS home.
* au_size: Set this to 4 MB.
* compatible.asm: Set this to the software version of your Grid Infrastructure home.
* cell.smart_scan_capable: Set this to TRUE. If this attribute is set to FALSE, Smart Scan will be
disabled to segments that reside in the disk group.
* disk_repair_time: Leave this defaulted to 3.6 hours unless you’re performing maintenance
on a call and know that your outage window will be greater than 3.6 hours.
A:
Once you identify candidate grid disks, use the CREATE DISKGROUP command to create your
ASM disk groups.
Here are some of the more important considerations to think about when creating ASM disk
groups on Exadata:
* (A) When capacity planning, take your redundancy specification into consideration. Normal
redundancy will have the effect of reducing your usable storage to half the raw capacity, and
high redundancy will shrink it to a third of your raw disk capacity.
* Simplicity is best on Exadata. Using wild-carded CREATE DISKGROUP syntax not only offers
the most terse command syntax, but also ensures your ASM disk groups are spread evenly across
your Exadata Storage Server disks.
* Take the time to plan grid disk prefix names and overall grid disk configuration in the context
of your desired ASM disk group design.
* Make sure to set the appropriate compatible.asm and compatible.rdbms attributes when
creating ASM disk groups.

* Whenever possible, use a 4 MB extent size when creating disk groups on ASM storage.