Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization uses a Shared VPC in net-host-proj with two attached service projects: app-service-proj for Compute Engine application VMs and db-service-proj for a new Cloud SQL for PostgreSQL instance. You have already enabled the required APIs and granted roles/compute.networkAdmin in db-service-proj, and you must meet these requirements:
Which additional configuration steps should you take to complete this architecture?
db-service-proj with PSA enabled, peer it to the Shared VPC in net-host-proj, deploy the Cloud SQL instance in db-service-proj without a public IP, and start the Cloud SQL Auth Proxy on the VMs in app-service-proj with the --private-ip flag.VPC Network Peering connects two VPC networks internally over Google's Software-Defined Network (SDN) so that subnets and internal IP addresses in directly peered networks can communicate without public IP addresses. Each VPC network maintains its own distributed firewall rules and routing tables.
net-host-proj to a separate VPC in db-service-proj does not propagate routes to the Cloud SQL VPC.app-service-proj (using the Shared VPC) will have no network route to reach the Cloud SQL instance's private IP address in db-service-proj's standalone VPC, causing Cloud SQL Auth Proxy connections to fail.db-service-proj bypasses the primary benefit of a Shared VPC, which already provides a unified network across service projects.The Cloud SQL instance were placed in an isolated VPC due to legacy constraints and you additionally deployed a supported multi-VPC bridging mechanism (such as a SOCKS5 intermediate proxy or Cloud Router custom route advertisements over VPN/Interconnect) rather than relying on transitive peering.
A common misconception is that peering two customer VPCs creates a transitive mesh to Google-managed service networks. Using the Shared VPC directly for Cloud SQL PSA avoids creating a second hop altogether.
app-service-proj that targets the PSA peering connection in db-service-proj, assign a static internal IP to the endpoint, and start the Cloud SQL Auth Proxy on the VMs in app-service-proj using the --psc flag.Private Service Connect (PSC) is an alternative private connectivity model where Cloud SQL exposes a service attachment rather than using VPC Network Peering. Consumer VPC networks access the instance via an internal forwarding rule known as a PSC endpoint, and the Cloud SQL Auth Proxy uses the --psc flag to resolve and connect to PSC-enabled instances.
--psc flag is strictly for instances configured with Private Service Connect enabled. When connecting over Private Services Access, the Cloud SQL Auth Proxy requires the --private-ip flag instead./24 PSA IP range allocations and VPC Network Peering, whereas PSA relies on peering and allocated CIDR blocks.PENDING state.roles/compute.networkAdmin) on the Shared VPC network.The Cloud SQL instance were provisioned with Private Service Connect enabled instead of PSA, the endpoint in the Shared VPC targeted the instance's service attachment with Cloud DNS records configured, and app-service-proj were added to the instance's allowed PSC projects.
Although Private Service Connect is recommended for multi-VPC or cross-organization topologies, PSA and PSC are distinct networking mechanisms with different prerequisites and Cloud SQL Auth Proxy flags (--private-ip versus --psc).
net-host-proj to establish PSA on the Shared VPC, add the app-service-proj RFC 1918 subnet range to Cloud SQL Authorized Networks, and configure the VMs in app-service-proj to connect directly to the instance's private IP without the Cloud SQL Auth Proxy.Authorized Networks is an IP allowlisting control on Cloud SQL instances used primarily to permit connections to a public IP address or from non-RFC 1918 private IP ranges. Direct private IP connections allow clients within the same VPC to open standard database TCP sessions (such as port 5432 for PostgreSQL) directly to the instance's internal IP.
10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) are already automatically authorized over PSA, making an Authorized Networks entry redundant for standard internal subnets. Furthermore, enabling PSA in net-host-proj also requires the Compute Engine API and roles/compute.networkAdmin in the host project.The security policy did not require IAM authentication or rotating SSL/TLS certificates via the Cloud SQL Auth Proxy, and the clients were connecting directly from a non-RFC 1918 IP range over PSA.
While Private Services Access provides underlying virtual network encryption in transit within Google Cloud, the Cloud SQL Auth Proxy adds application-layer IAM authorization and automated rotating TLS certificates required by strict zero-trust security standards.
roles/compute.networkAdmin in net-host-proj to allocate a private IP range and create the PSA peering on the Shared VPC, deploy the Cloud SQL instance on that Shared VPC without a public IP, and start the Cloud SQL Auth Proxy on the VMs in app-service-proj with the --private-ip flag.Private Services Access (PSA) establishes a private VPC Network Peering connection between a customer VPC network and the Google-managed service producer VPC where Cloud SQL instances reside. When using a Shared VPC, network resources and peering connections are centrally managed in the host project (net-host-proj) and shared across attached service projects (app-service-proj and db-service-proj). Pairing this topology with the Cloud SQL Auth Proxy layers identity-aware access and automated transport encryption over the private network path.
servicenetworking.googleapis.com and compute.googleapis.com and granting roles/compute.networkAdmin in net-host-proj allows administrators to allocate a dedicated IP block (minimum /24, recommended /16) and establish the PSA peering connection on the Shared VPC, preventing SERVICE_NETWORKING_NOT_ENABLED or permission errors.--private-ip flag on the VMs in app-service-proj authenticates connections using IAM credentials and secures traffic end-to-end with rotating SSL/TLS certificates.net-host-proj while application and database teams operate independently in separate service projects.app-service-proj VMs and the Cloud SQL instance attach to the same Shared VPC, no intermediate proxy or transit routing is needed.Configuring PSA directly on the Shared VPC in net-host-proj satisfies the host-project prerequisites required by Google Cloud while placing both the application VMs and the Cloud SQL PSA peering in a single shared network. Unlike direct private IP connections without a proxy or workaround peering topologies, combining Shared VPC PSA with the Cloud SQL Auth Proxy (--private-ip) delivers full IAM authentication, automated encryption, and strict network isolation.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated