In your database, the STATISTICS_LEVEL parameter is set to TYPICAL and an Automatic Workload Repository (AWR) snapshot is taken every 30 minutes. Which two statements are true about the Automatic…

ADDM measures database performance by analyzing the wait time and CPU time consumed by all non-idle user sessions, providing a comprehensive view of resource usage and bottlenecks. This approach identifies the most significant areas of database activity and their impact on performance.

ADDM typically analyzes the interval between the two most recent AWR snapshots, not necessarily always comparing the latest snapshot with a baseline snapshot unless specifically configured to do so.

ADDM is designed to run automatically after each AWR snapshot is created, leveraging the collected data to diagnose performance issues. It requires a minimum of two snapshots, representing a start and end point, to analyze a specific time interval and compare performance metrics.

ADDM requires only two AWR snapshots (a start and an end snapshot) to define an analysis period, not four.

ADDM provides recommendations for performance improvements and often suggests using other advisors, such as the SQL Tuning Advisor or Memory Advisors, for deeper analysis of specific problems.