Exam Professional Data Engineer topic 1 question 198 discussion

D. Use Cloud Composer in a Shared VPC configuration. Place the Cloud Composer resources in the service project. Shared VPC requires that you designate a host project to which networks and subnetworks belong and a service project, which is attached to the host project. When Cloud Composer participates in a Shared VPC, the Cloud Composer environment is in the service project. Reference: https://cloud.google.com/composer/docs/how-to/managing/configuring-shared-vpc

Using the host project to deploy services is a bad practice and should only be used if the service doesn't support shared VPC. It may be easier networking wise, but that's why it's the wrong answer. Cloud Composer supports Shaved VPC, so it should go in it's own project.

Place in host project for network connectivity

The recommended approach is to place Cloud Composer resources in the host project of the Shared VPC. This centralizes network management, simplifies connectivity, and enhances security by adhering to the principle of least privilege.

Placing Cloud Composer resources in the service project can lead to more complex network configurations and management overhead compared to placing them in the host project, which is designed to manage Shared VPC resources.

Please correct if I am wrong.. I think it is Option C coz I feel Option D is incorrect because placing the Cloud Composer resources in the service project would not allow you to access resources in the host project.

✅ Use Cloud Composer in a Shared VPC configuration. Place the Cloud Composer resources in the service project. - Cloud Composer is a managed Apache Airflow service. It is an open-source tool that programmatically author, schedule, and monitor pipelines, which fits your needs perfectly. - In a Shared VPC configuration, Cloud Composer resources should be placed in the service project. This provides network isolation while still allowing the Cloud Composer environment to communicate with resources in the host project. - With Shared VPC, the host project's network (including its subnets and secondary IP ranges) is shared by other service projects, which promotes network peering, and it's compliant with the networking considerations of GKE.

D is the answer. https://cloud.google.com/composer/docs/how-to/managing/configuring-shared-vpc Shared VPC enables organizations to establish budgeting and access control boundaries at the project level while allowing for secure and efficient communication using private IPs across those boundaries. In the Shared VPC configuration, Cloud Composer can invoke services hosted in other Google Cloud projects in the same organization without exposing services to the public internet.

D Shared VPC requires that you designate a host project to which networks and subnetworks belong and a service project, which is attached to the host project. https://cloud.google.com/composer/docs/how-to/managing/configuring-shared-vpc#:~:text=This%20page%20describes,the%20service%20project.

D according to documentation Shared VPC requires that you designate a host project to which networks and subnetworks belong and a service project, which is attached to the host project. When Cloud Composer participates in a Shared VPC, the Cloud Composer environment is in the service project. https://cloud.google.com/composer/docs/how-to/managing/configuring-shared-vpc#set_up_shared_vpc_and_attach_the_service_project