To persist historical query performance metrics for trend analysis is the correct option.

The query store is designed to record query execution statistics and associated plans over time so database administrators and developers can analyze trends, identify regressions, and correlate performance changes with schema or workload shifts.

By keeping historical metrics the query store helps you compare past and present behavior, detect slowdowns, and choose or force stable execution plans when needed for troubleshooting and tuning.

Cloud SQL Insights is an interactive monitoring and diagnostics tool and not the query store feature. It is focused on surfacing recent query activity and diagnostics rather than acting as a long term persisted store of historical query metrics.

To schedule and manage automated database backups is incorrect because backups are about protecting and restoring data and schema and do not provide stored query performance metrics for trend analysis.

To cache frequently executed statements for faster response is incorrect because caching and plan caching are runtime optimizations and do not constitute a historical repository of query performance data for trend analysis.

Full AWS Practitioner Certification Question