A tax assessor imagery farm must project when the records lake will need a second namespace or scale-out node. Which planning activity is required?

A tax assessor imagery farm must project when the records lake will need a second namespace or scale-out node—capacity and scalability forecasting that triggers expansion before saturation. Imagery growth is rarely flat; forecasting filesystem/namespace limits and usable capacity lets the city add scale-out resources while jobs still succeed. Proactive scale-out is the Domain 2.3 scalability planning activity the stem requires.

Throughput performance tuning that optimizes ingest speed for existing imagery pipelines fails by concept: it speeds current pipelines but does not forecast namespace saturation or trigger a scale-out node before the lake fills. Data lifecycle planning that migrates aging imagery to lower-cost archival storage tiers fails observational planning—moving old imagery to archives reduces cost but does not project when the primary lake needs a second namespace or scale-out node. Disaster recovery planning that replicates lake datasets to a secondary protection facility fails system balance; replication protects data but does not forecast inode/namespace limits or add scale-out capacity to the primary imagery lake.

Exam caveat: Forecasting includes capacity bytes and platform limits (namespaces, file counts, performance headroom). The exact trigger threshold is operational; the exam cares that scale-out is planned before hard failure.

Operational check: trend imagery ingest and namespace utilization; set order triggers with vendor lead time before hard full; validate that adding a namespace/node restores headroom without emergency tax-season downtime.