Scheduled batch processing is the correct option.

Scheduled batch processing fits a dataset that arrives once every 24 hours because the workload can run on a fixed schedule to ingest and transform the entire file set in one job. The approach accepts higher end to end latency and is easy to orchestrate with tools that run periodic jobs and manage compute only when needed.

Cloud Pub/Sub is incorrect because it is a messaging and event ingestion service that is designed for asynchronous or streaming data delivery rather than for processing a single daily file transfer.

Continuous stream processing is incorrect because it targets constant event streams and low latency processing of individual events, and it is not the natural fit for a once per day batch file workload.

Real time analytics is incorrect because it emphasizes immediate, low latency insights and often sub second or second scale processing, which is unnecessary for a dataset that is delivered every 24 hours.

Full AWS Practitioner Certification Question