Q: 20
In your company, two departments with separate GCP projects (code-dev and data-dev) in the same
organization need to allow full cross-communication between all of their virtual machines in GCP.
Each department has one VPC in its project and wants full control over their network. Neither
department intends to recreate its existing computing resources. You want to implement a solution
that minimizes cost.
Which two steps should you take? (Choose two.)
Options
Discussion
Its C and E, since shared VPC helps centralize control and custom routes handle cross-project traffic.
B/D makes sense since VPC peering (B) lets both projects manage their own VPCs without extra cost, and D covers the firewall rules needed so the VMs can actually talk. I think that's pretty much GCP best practice here, unless I'm missing something.
BD imo, seen similar on practice sets. VPC peering (B) is the cheapest and lets both projects keep their own VPCs, and you need firewall rules (D) to actually allow the traffic. No need for VPN or shared VPC here.
Yeah, B and D fit this case. VPC peering keeps costs way down, plus both teams control their own networks. Just gotta add the right firewall rules so the traffic isn't blocked. Not 100 percent but pretty sure that's what GCP expects here.
Option B and D make sense here. VPC peering (B) is the low-cost way to connect separate projects while keeping each team's control, and then you need firewall rules (D) so traffic actually flows. Nice clear scenario, matches what I've seen in some practice sets.
Be respectful. No spam.
