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.
A healthcare analytics company is deploying an application on Google Cloud that uses Cloud SQL for PostgreSQL in a Shared VPC service project and exports reports to Cloud Storage. An external ETL service on another cloud provider must also read from the database.
Your design must meet these security requirements:
Which security architecture should you implement?
This option combines Cloud SQL IAM database authentication and Workload Identity Federation with Cloud KMS CMEK and TLS, while using the Compute Engine default service account and placing only the Shared VPC service project inside a VPC Service Controls perimeter in dry-run mode.
roles/editor) across the project unless restricted by the constraints/iam.automaticIamGrantsForDefaultServiceAccounts organization policy.You were only in an initial testing and traffic-auditing phase using dry-run mode prior to enforcement, had replaced the default service account with dedicated least-privilege accounts, and included the Shared VPC host project in the perimeter.
This configuration relies on a rotated service account JSON key for external authentication, IAM custom roles paired with VPC egress firewall rules to restrict network traffic, and Google-managed default encryption with TLS.
The external ETL platform did not support OIDC or SAML federation (making a service account key unavoidable), compliance policies accepted Google-managed encryption keys, and there were no requirements to prevent authorized identities from copying data to external projects.
This approach configures Cloud SQL IAM database authentication with service account impersonation internally, uses a downloaded service account key externally, places only Cloud Storage inside a VPC Service Controls perimeter (leaving the Cloud SQL API unrestricted), and pairs Google-managed encryption with Access Transparency.
The organization only needed audit visibility into cloud provider administrative actions rather than customer-controlled encryption keys, and the external workload could not integrate with Workload Identity Federation.
Combining Cloud SQL IAM database authentication, Workload Identity Federation, VPC Service Controls, and Customer-Managed Encryption Keys (CMEK) provides defense-in-depth across identity, network perimeter, and data encryption layers for cloud database workloads.
constraints/iam.disableServiceAccountKeyCreation).Unlike approaches that rely solely on IAM, firewall rules, or Google-managed keys, this architecture secures every stage of the data lifecycle—from workload authentication and private Shared VPC transport to API-level exfiltration prevention and customer-controlled encryption.
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