You have the following Shared VPC design. VPC Flow Logs is configured for Subnet-1 in the host VPC. You also want to monitor flow logs for Subnet-2. What should you do?
You have the following Shared VPC design. VPC Flow Logs is configured for Subnet-1 in the host VPC. You also want to monitor flow logs for Subnet-2. What should you do?
In a Shared VPC setup, each project can have its own VPC, and the VPC Flow Logs are configured individually for each VPC. Since Subnet-2 is in the service project VPC, which is separate from the host project VPC, you need to configure VPC Flow Logs for Subnet-2 in the service project VPC to monitor its flow logs. Configuring VPC Flow Logs in the host project VPC would not capture the logs for Subnet-2. Therefore, the correct answer is to configure VPC Flow Logs in the service project VPC for Subnet-2.
B is right Those are two separate VPCs
the subnets are created on the Host Project, friend.
It's not two separate VPCs... all subnets are defined in Host Projects.
A Shared VPC network is a VPC network defined in a host project and made available as a centrally shared network for eligible resources in service projects
A compute engine can't have multiple NICs in the same VPC, so in the figure the VPCs are two (even if with the same name), one in the host project and one in the service project. So the answer is B
This is the only correct answer
It's A. https://cloud.google.com/vpc/docs/flow-logs#vm-to-vm-flows-shared-vpc
"In Shared VPC networks, logs only appear in the host project, not the service projects. Make sure you look for the logs in the host project." https://cloud.google.com/vpc/docs/using-flow-logs I go with A
Option B is incorrect because logs for VPC Flow Logs do not appear in the service projects in a Shared VPC setup. Option C is unrelated to monitoring flow logs and would not achieve the desired result. Option D is also unrelated to monitoring flow logs and would not achieve the desired result.
It's B. Service project has it's own VPC where the Subnet-2 is located and it has nothing to do with Host Project and Shared VPC. If the Subnet-2 was the part of Host project Shared VPC then correct answer would be B.
I mean A.
A Shared VPC network is a VPC network defined in a host project and made available as a centrally shared network for eligible resources in service projects
A compute engine can't have multiple NICs in the same VPC