You are the network administrator responsible for hybrid connectivity at your organization. Your developer team wants to use Cloud SQL in the us-west1 region in your Shared VPC. You configured a…

Question

Options

• AModify the VPC Network Peering connection used for Cloud SQL, and enable the import and
• BChange the VPC routing mode to global.
• CCreate an additional Cloud Router in us-west2.
• DChange the VPC routing mode to global.

• A
  77% (30)
• B
  8% (3)
• C
  3% (1)
• D
  13% (5)

Explanation

When you configure Private Services Access (PSA) for Cloud SQL, Google creates a VPC Network Peering connection between your Shared VPC and Google's service producer network. By default, VPC peering does not export or import custom routes, so the IP range reserved for Cloud SQL (in the peered service producer network) is not advertised to your Cloud Router, and therefore not propagated to your on-premises network via the Dedicated Interconnect. The fix is to enable 'Export custom routes' and 'Import custom routes' on the PSA peering connection, which allows the Cloud Router to learn the Cloud SQL IP routes and advertise them to on-premises. Options B and D both suggest changing VPC routing mode to global, which is redundant (and identical choices - likely a typo in the question). Option C (additional Cloud Router in us-west2) is irrelevant since the Cloud SQL instance is in us-west1.

No community discussion yet for this question.