Migrate on-premises workloads: Flask web app, backend API, and a scheduled long-running ETL/reporting job. Minimize operational cost and follow Google-recommended serverless approaches. What should you do?

The correct option leverages Google's serverless offerings to minimize operational cost. App Engine is ideal for web applications, providing a fully managed platform. Cloud Run is excellent for stateless backend APIs, offering autoscaling and pay-per-use billing. For the scheduled long-running job, Cloud Tasks can reliably trigger a Cloud Run service, allowing the job to run in a serverless container without managing virtual machines. The first incorrect option uses Compute Engine for the background job, which is not serverless and incurs higher operational overhead due to VM management. The third and fourth options incorrectly suggest running a web application from a Cloud Storage bucket. While Cloud Storage can host static websites, a Flask web app is dynamic and requires a server-side environment like App Engine or Cloud Run.