Exam Professional Cloud Database Engineer topic 1 question 38 discussion

A. B is wrong since Serverless VPC Access is for connecting to your VPC network from serverless environments (Cloud Run, App Engine, Cloud Functions). C is wrong as this concerns private consumption of services across VPC networks that belong to different groups, teams, projects, or organizations. D is wrong because it concerns application networking for services. Nothing in its documentation mentions BMS. That leaves A. I would prefer to have seen something about VPC network peering, but the clincher is firewall rules which you would use to limit IP traffic sources to the backend Oracle DBs residing in their own Google managed VPC on BMS.

The answer is for sure A read the following; https://medium.com/google-cloud/shared-vpc-in-google-cloud-64527e0a409e#:~:text=Unlike%20VPC%20peering%2C%20Shared%20VPC%20connects%20projects%20within%20the%20same%20organization.&text=There%20are%20a%20lot%20of,between%20VPCs%20in%20different%20projects.

A is the correct answer

B is not applicable here. C is also not the case - don't confuse it with Private Google Access https://cloud.google.com/bare-metal/docs/bms-security#enforce-a-secure-perimeter-with-private-google-access We don't have a Service Mesh here, so D is also not an option. I go for A - https://cloud.google.com/bare-metal/docs/bms-security#:~:text=As%20shown%20in%20Figure%206%2C%20use%20a%20shared%20VPC%20architecture%20to%20allow%20resources%20from%20different%20projects%20to%20access%20the%20Bare%20Metal%20Solution%20servers

When you use Shared VPC, you designate a project as a host project and attach one or more other service projects to it.