Which three tasks can be automatically performed by the Automatic Data Optimization feature of Information lifecycle Management (ILM)?

Question

Options

• ATracking the most recent read time for a table segment in a user tablespace
• BTracking the most recent write time for a table segment in a user tablespace
• CTracking insert time by row for table rows
• DTracking the most recent write time for a table block
• ETracking the most recent read time for a table segment in the SYSTEM tablespace
• FTracking the most recent write time for a table segment in the SYSAUX tablespace Correct

• A
  93% (27)
• D
  3% (1)
• E
  3% (1)

Explanation

Oracle's Automatic Data Optimization (ADO) automatically tracks segment-level read/write times in user tablespaces (A, B) and row-level insert times (C) - these three are the core tracking capabilities ADO uses to evaluate data "heat" and apply ILM policies like compression or tiering.

Why the distractors are wrong:

• D is wrong because ADO tracks at the segment level, not the block level - block-level granularity is too fine and not how ADO policies are evaluated.
• E is wrong because the SYSTEM tablespace is excluded from ADO tracking; ILM applies to user data, not system-managed segments.
• F is wrong for the same reason - SYSAUX is also a system tablespace and is excluded from ADO heat tracking.

Memory tip: Think "User Segment, User Row" - ADO only tracks activity on user tablespace segments (read + write) and individual rows (insert time). Anything at the block level or in system tablespaces (SYSTEM/SYSAUX) is out of scope for ADO.

No community discussion yet for this question.