I'd say D makes sense here. If you assign an external IP to the Cloud Run service, it should be able to connect out to external resources like an on-prem database, assuming firewall rules allow it. I remember seeing a similar setup in a practice set, so I think D works, but open to other ideas if I'm missing a detail.
Q: 1
A microservice running on Cloud Run needs to connect to an external on-premises
database via a Dedicated Interconnect connection. What is the required networking
configuration for the Cloud Run service?
Options
Discussion
D, not C
C. encountered exactly similar question in my exam and this is the setup needed for Cloud Run to reach on-prem over Interconnect.
Maybe D, but only if the on-prem DB had a public IP instead of being accessed over Interconnect using private IPs. Otherwise C feels right for this scenario.
D. saw a similar question pop up in some practice sets.
Option C is the right pick, not D. Assigning an external IP (option D) seems tempting but doesn't enable private connectivity to on-prem via Interconnect-that's what Serverless VPC Access does. I see folks mix that up a lot in practice.
Probably C since Serverless VPC Access is needed for Cloud Run to hit internal IPs over Interconnect. Assigning an external IP (D) doesn't help with on-prem private resources, that's a common trap here. I think this lines up with how Google expects you to connect hybrid workloads, but happy for any corrections.
C/D? D is tempting but only works for public IPs, not private over Interconnect. C is correct in this context.
Nah, D seems like a trap since assigning an external IP won't help Cloud Run reach on-prem private IPs over Interconnect. C is what you need for private connectivity. Anyone disagree?
C vs D? Not totally confident, but pretty sure C is right since Serverless VPC Access is usually needed for private connections back to on-prem. D doesn't really let Cloud Run reach internal IPs over Interconnect, if I'm remembering this right.
Be respectful. No spam.
Question 1 of 35