A retailer needs nightly predictions for 40 million rows and can tolerate results arriving hours later. The team wants the cheapest and simplest approach rather than a low-latency API. Which serving pattern is the best fit?
Answer & explanation
Correct answer: A
WHY A: Batch inference is the standard choice for large offline scoring workloads where latency is not critical and throughput matters most. WHY NOT B: Real-time serving adds unnecessary online API overhead. WHY NOT C: Streaming is aimed at continuously arriving data, not a simple nightly bulk run. WHY NOT D: Manual notebook execution is not the right production deployment pattern. WHY NOT E: Canary deployment is about rollout strategy, not bulk table scoring.