You are configuring a CI pipeline. The build step for your CI pipeline integration testing requires access to APIs inside your private VPC network. Your security team requires that you do not expose…

Question

Options

• AUse Cloud Build private pools to connect to the private VPC.
• BUse Spinnaker for Google Cloud to connect to the private VPC.
• CUse Cloud Build as a pipeline runner. Configure Internal HTTP(S) Load Balancing for API access.
• DUse Cloud Build as a pipeline runner. Configure External HTTP(S) Load Balancing with a Google

• A
  71% (22)
• B
  16% (5)
• C
  10% (3)
• D
  3% (1)

Explanation

Cloud Build private pools are a managed feature that allows Cloud Build workers to be provisioned inside (or peered with) your private VPC network. This gives build steps direct, private network access to internal APIs without routing traffic through the public internet, satisfying the security requirement. The solution requires no additional infrastructure management beyond pool configuration. Option B (Spinnaker) is a continuous delivery tool, not a VPC networking solution. Options C and D both involve HTTP(S) Load Balancers - internal load balancing still requires network peering configuration, and external load balancing exposes traffic publicly, which violates the security requirement.

No community discussion yet for this question.