Avoid adding indexes for the infrequently accessed columns is correct.

Adding indexes to columns that are seldom referenced usually costs more than it helps because each index increases storage and slows down inserts updates and deletes due to extra maintenance. For a large archive table the overall query performance is best improved by indexing columns that are actually used by queries and by relying on fewer well chosen indexes rather than creating many indexes that are rarely used.

Create nonclustered indexes on every seldom used column is wrong because creating an index for every seldom used column creates heavy maintenance overhead and extra storage use and it will slow write operations without delivering meaningful read performance gains for most queries.

Create filtered indexes that target specific subsets of rows for the infrequently used columns is not the best answer for this scenario because filtered indexes can be useful for targeted query patterns but they still add maintenance and are only beneficial when a clear and frequent filter pattern exists. Creating many filtered indexes across many seldom used columns can still produce excessive overhead and complexity.

Create a clustered index on each of the rarely used columns is incorrect because a table can have only one clustered index and clustered keys should be chosen for uniqueness and frequent access patterns. It is not possible to create multiple clustered indexes and it would be inappropriate to cluster on many rarely used columns.

Full AWS Practitioner Certification Question