Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise is deploying a mission-critical workload on a VPC-native Google Kubernetes Engine (GKE) cluster that must interact with a Cloud SQL for PostgreSQL instance configured exclusively with private IP. The organization's security policy mandates the following:
Which configuration should the security engineer implement to meet these requirements?
This approach relies on creating an RSA private key file for a Google Service Account, storing it inside a Kubernetes Secret, and mounting it via the --credentials-file argument into a standalone proxy pod while using the v1 proxy flag --enable_iam_login.
--enable_iam_login flag is part of Cloud SQL Auth Proxy v1, which is deprecated; modern deployments require v2 (cloud-sql-proxy) with the --auto-iam-authn parameter.The cluster were hosted on an external on-premises environment without access to Google Cloud Workload Identity federation, and public IP egress was explicitly allowed.
The Cloud SQL Auth Proxy is a companion connector that provides secure access to Cloud SQL instances by establishing an encrypted TLS/SSL tunnel and authenticating through the Cloud SQL Admin API. When combined with GKE Workload Identity and IAM database authentication, applications running on Google Kubernetes Engine authenticate seamlessly without managing static database user passwords or long-lived private key files.
--private-ip flag forces network traffic to route through internal RFC 1918 addresses via Private Service Access or Private Service Connect. Outgoing connections from the proxy to the database on port 3307 are automatically wrapped in 256-bit TLS/SSL with ephemeral certificates refreshed every hour.--auto-iam-authn flag instructs the proxy to supply IAM credentials directly during the database handshake, eliminating static database passwords entirely.roles/cloudsql.client permits connection authorization via the Cloud SQL Admin API, while roles/cloudsql.instanceUser grants permission to log in using IAM database authentication.127.0.0.1 (localhost), ensuring unencrypted local traffic never leaves the pod boundary.This approach adheres strictly to Google Cloud security best practices by eliminating credential persistence, enforcing internal encrypted routing, and automating identity federation across GKE and Cloud SQL.
This option bypasses the Cloud SQL Auth Proxy entirely, configuring application containers to initiate raw TCP connections to port 5432 on the database private IP while authenticating using static database credentials retrieved from Cloud Secret Manager and manually installed SSL/TLS certificates.
The application architecture prevented running sidecar containers or connectors and required standard direct TCP sockets with customer-managed server/client SSL certificates.
This configuration establishes a centralized Cloud SQL Auth Proxy service accessible cluster-wide by binding the proxy to 0.0.0.0, assigning administrative IAM roles to the underlying Compute Engine default service account, and authenticating database transactions using static database user passwords.
0.0.0.0 over a shared ClusterIP service allows any container within the GKE cluster to send unencrypted SQL queries to the proxy service endpoint.roles/cloudsql.admin gives broad control over instance configurations, backups, and deletions rather than strictly scoping connection rights (roles/cloudsql.client and roles/cloudsql.instanceUser).0.0.0.0 proxy socket.The goal was to provide legacy, non-sensitive shared database access across heterogeneous microservices where individual pod identities could not be established.
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