Your rapidly growing ecommerce company is migrating their analytics workloads to AlloyDB for PostgreSQL. You anticipate a significant increase in reporting queries as the business scales. You need a read pool strategy to scale your analytics operations in anticipation of future growth while minimizing costs. What should you do?

A. Direct all complex, long-running analytics queries to the primary instance, and only use read pools for short, frequent reports. B. Change the instance sizes of the read nodes in the read pool. C. Begin with minimal read pools and iteratively expand or shrink them based on real-time load monitoring to optimize resource allocation. D. Assign all reporting queries to a single, large read pool to maximize the combined compute resources available for analytics.