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 is deploying a Cloud SQL for PostgreSQL instance to store regulated financial data. The database design must comply with the following organizational security standards:
Which combination of security controls should you implement?
This solution combines three foundational Google Cloud governance controls—Identity and Access Management (IAM) job-function roles without long-lived keys, Customer-Managed Encryption Keys (CMEK) via Cloud Key Management Service (Cloud KMS), and VPC Service Controls—to build a defense-in-depth posture for managed databases like Cloud SQL.
roles/cloudsql.viewer or roles/cloudsql.client) restrict principals to only the permissions required for their duties, adhering to the principle of least privilege. Enforcing the organization policy constraint constraints/iam.disableServiceAccountKeyCreation eliminates downloadable JSON key files, requiring workloads to authenticate using short-lived tokens or attached service accounts.Unlike network-only controls or default encryption, this integrated design addresses identity, cryptography, and API perimeter security simultaneously without adding operational friction to managed Cloud SQL maintenance.
This option implements CMEK via Cloud KMS for encryption control, grants the basic (legacy) Editor role (roles/editor) to database operators, and uses Cloud SQL Authorized Networks to filter incoming connections.
Editor role grants thousands of read and write permissions across almost all Google Cloud services in the project—far beyond database administration. Security standards explicitly discourage legacy roles (Owner, Editor, Viewer) in favor of predefined job-function roles or tightly scoped custom roles.Only CMEK key management were required in a non-production sandbox environment where basic roles and public IP allowlisting were acceptable.
A frequent pitfall is treating Authorized Networks as an enterprise perimeter control. True exfiltration protection across Google Cloud services requires VPC Service Controls, combined with private IP connectivity and scoped IAM job-function roles.
This configuration enforces least-privilege IAM access without persistent service account keys, uses Google Cloud's default encryption at rest, and blocks outbound virtual machine traffic inside the Virtual Private Cloud (VPC) using a deny-all egress firewall rule.
The organization only needed standard encryption at rest without customer-managed key revocation and only needed to block Compute Engine VM internet egress rather than prevent Google Cloud API exfiltration.
A common misconception is that strict VPC firewall rules protect managed services from data exfiltration. Because managed database exports interact with Google Cloud APIs directly, VPC Service Controls is needed to close that API exfiltration path.
This approach relies on downloaded service account key files (even if rotated), attempts to use Customer-Supplied Encryption Keys (CSEK) for storage encryption, and enables Private Google Access so instances without external IP addresses can reach Google APIs.
restricted.googleapis.com and a VPC Service Controls perimeter to prevent exfiltration.You were securing self-managed databases on Compute Engine VMs where CSEK is supported, and organizational policy allowed rotated service account keys without requiring VPC Service Controls.
Students often confuse CMEK and CSEK. Managed databases such as Cloud SQL and AlloyDB integrate with Cloud KMS for CMEK, whereas CSEK is limited to infrastructure-level resources like Compute Engine disks.
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