C or D? The question says "minimizing changes to data schema and application code" and I’m wondering if they allow for some rewrites or strict minimal change. If extensive rewrites are allowed, then Bigtable might work, otherwise AlloyDB fits better.
Just to clarify, is minimizing operational overhead more important than preserving the current directory structure? If keeping the structure unchanged is a hard requirement, that could change which option makes sense.
C/D? I get why people are picking D since it matches the current structure, but GCP URL maps don't support wildcards in the middle, so you can't use /*/video. On the other hand, C uses regex which isn't supported either. So neither seems quite right without changing the directories. Maybe A is technically best, but still not 100% sure since the question talks about minimizing operational overhead. Am I missing something small in how path rules work?
Yeah, D and E work for Dedicated Interconnect. Google sends the LOA-CFA both to the NOC email (D) you list during setup, and also directly to the provider (E). Downloading from console is only for Partner Interconnect, not Dedicated. Pretty sure that's how it's been on my last project, but open to corrections if something's changed.
Seen this setup before, you'd use D. Multi-exit Discriminator (MED) helps your on-prem router know which Cloud Router should be primary for inbound BGP traffic. It's not about Local Preference since that's more for outbound path selection. Pretty sure it's D, but if someone disagrees let me know.
Actually, Multi-exit Discriminator (D) is the standard way to influence inbound traffic from the on-prem router to GCP. MED lets you signal your preferred path when there are multiple entry points, so setting a lower MED on the active router makes it primary. I think that's what Google Cloud expects here. Open for debate if someone disagrees.
It's actually D in this scenario because MED tells your on-prem router which Cloud Router path to prefer for inbound routes. If you set a lower MED on the active Cloud Router, that one gets picked for incoming traffic. Local Preference (C) would influence outbound from your own side, not which Google peer is active. I think that's how most exam guides explain it, but if anyone's got a real-world case where C worked, let me know!
A isn’t it, D is more likely. Remember seeing a similar scenario in practice tests, where the Via header caused the web server to skip compression. But just to confirm, does the question specify if all load-balanced web servers are running identical configs? That could switch things between D and C.
-zone-file-format when importing a BIND zone file, nothing in the question says to replace NS records or wipe out anything first. Only extra flags if the scenario calls for them. Someone shout if I'm missing a detail here.Why not B? Shared VPC can’t go across organizations, right?
A and C make sense here. VPC peering (A) works even if the VPCs are in different orgs and have no CIDR overlap. Cloud VPN (C) is also valid for secure cross-org communication. Shared VPC can't span organizations, so that's out. Let me know if I'm missing something!