Which two statements are true about the Automatic Database Diagnostic Monitor (ADDM)?

ADDM processes performance data gathered by AWR snapshots, needing at least a pair of snapshots (start and end) to analyze a time period, and it executes automatically after each snapshot is created.

While ADDM findings are stored in views within the AWR repository, AWR itself is the source of the performance data ADDM analyzes, not strictly the storage location for its derived results in the same conceptual way it stores raw snapshots.

A key feature of ADDM is its ability to diagnose SQL-related performance problems and recommend or even automatically initiate SQL advisors, such as the SQL Tuning Advisor, for deeper analysis.

ADDM provides comprehensive recommendations for various performance bottlenecks, including CPU, I/O, memory, and concurrency issues, not exclusively for poorly performing SQL statements.

ADDM requires a minimum of two AWR snapshots (a starting and an ending snapshot) to define the time interval over which it performs its diagnostic analysis.