Answer: Use Cloud Composer in a Shared VPC configuration. Place the Cloud Composer resources in the service project.

## Explanation **Correct Answer: D** **Why Option D is correct:** - Cloud Composer is Google's managed workflow orchestration service based on Apache Airflow - When using Shared VPC, Cloud Composer environments must be placed in the **service project**, not the host project - The host project contains the network resources (VPC, subnets), while service projects attach to the host project to use these shared network resources - This configuration allows Cloud Composer to leverage the Shared VPC networking while maintaining proper project separation **Why other options are incorrect:** - **Option A & B**: Dataflow is for data processing pipelines, not workflow orchestration/scheduling. Cloud Run triggers or shell scripts don't provide the comprehensive workflow management that Cloud Composer offers - **Option C**: Placing Cloud Composer resources in the host project violates Shared VPC best practices - Cloud Composer should be in the service project **Key Points:** - Shared VPC architecture requires clear separation between host project (network resources) and service projects (workloads) - Cloud Composer is the appropriate managed service for workflow pipeline scheduling using open-source tools - GKE integration is supported through Cloud Composer's managed Airflow environment Reference: https://cloud.google.com/composer/docs/how-to/managing/configuring-shared-vpc

Author: LeetQuiz .