Which two statements are true about the initial storage configuration after the standard (non- virtualized) deployment of a new Exadata Database Machine with High Capacity storage servers?

Question

Options

• AThe sparse_<DBM_NAME> diskgroup is created automatically.
• BThere is free space available on the hard disks inside the database servers for possible extension
• CThe DATA_<DBM_Name> and RECO_<DBM_NAME> ASM diskgroups are built on with DATA on
• DThere is free space available on flashdisks inside the Exadata storage servers for possible use for
• EThere is free space available on flashdisks inside the Exadata storage servers to configure

• A
  7% (2)
• B
  10% (3)
• C
  3% (1)
• D
  80% (24)

Explanation

On Exadata High Capacity (HC) storage servers, the initial standard deployment allocates HDD capacity fully to the DATA and RECO ASM diskgroups, but does not fully commit all flash disk capacity - leaving free flash space available both for potential use (D) and for future configuration such as adding a flash-based diskgroup or expanding the Smart Flash Cache (E).

Why the distractors are wrong:

• A is wrong because sparse_<DBM_NAME> diskgroups belong to virtualized Exadata deployments (used for sparse clones); they are not auto-created in a standard non-virtualized setup.
• B is wrong because free storage space for extension resides on the storage servers, not on the hard disks inside the database/compute servers - compute nodes hold only OS/local data.
• C is wrong because on HC servers, DATA and RECO diskgroups are built on HDDs, not flash - all HDD capacity is consumed at deployment, leaving no free hard disk space for extension.

Memory tip: Think of HC Exadata as "HDDs are full on day one, flash has room to grow." The HDD space is completely carved into DATA + RECO, while flash has leftover capacity you can tap later - that leftover flash headroom is the key concept behind both D and E.

No community discussion yet for this question.