Which two Exadata security features would you configure to control which databases can access which griddisks, when multiple databases share space on your storage servers in an unpartitioned storage…

Question

Options

• AExadata storage realms using ASM-scoped security mode
• BFile permissions on the griddisks in each database server
• CUsing EXADCLI instead of CELLCLI to create the griddisks
• DFile permissions on the griddisks in each storage server
• EExadata storage realms using database-scoped security mode

• A
  74% (20)
• B
  7% (2)
• C
  4% (1)
• D
  15% (4)

Explanation

Exadata Storage Realms are the purpose-built mechanism for isolating griddisk access between databases sharing an unpartitioned storage grid. ASM-scoped security (A) enforces access at the ASM diskgroup level - only ASM instances holding the correct realm credentials can mount the associated griddisks - while database-scoped security (E) adds a finer-grained layer, tying access control directly to individual database instances rather than just their ASM. Together, these two modes of Storage Realms give you layered, Exadata-native access boundaries without physically partitioning the storage.

Why the distractors fail:

• B - Griddisks live on storage servers (cells), not database servers, so file permissions there are irrelevant to griddisk access control.
• C - EXADCLI is not a real Exadata tool; CELLCLI is used to administer cells, but the tool used to create griddisks has no bearing on which databases can access them.
• D - Griddisks do reside on storage servers, but OS-level file permissions are not how Exadata enforces database isolation; that's exactly what Storage Realms replace.

Memory tip: Think "REALM = Real Logical Access Management." When storage is unpartitioned (shared), you need a logical boundary - Realms - applied at two scopes: the ASM level and the database level.

No community discussion yet for this question.