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.
An organization hosts sensitive financial data in BigQuery and Cloud SQL, which is accessed by backend applications running on Compute Engine VMs inside a Google Cloud VPC. A recent security review identified the following gaps:
roles/editor role on the project.private.googleapis.com.Which combination of controls should you implement to enforce least privilege and mitigate data exfiltration?
Chrome Enterprise Premium provides user-centric, context-aware access controls that evaluate user identity, IP address, and device attributes on API requests. Google Cloud Armor provides Layer 3 through Layer 7 DDoS mitigation and web application firewall (WAF) protection for applications exposed behind Cloud Load Balancing.
gcloud CLI sessions), whereas VPC Service Controls applies to both user identities and service accounts.The requirements were to restrict human developers' access to the Google Cloud console based on corporate device posture and to protect a public-facing web application behind an external HTTP(S) load balancer from DDoS and Layer 7 attacks.
Organizations often combine Chrome Enterprise Premium (for human user context) with VPC Service Controls (for service accounts and resource perimeters) and VPC egress firewall rules (for VM outbound traffic) to achieve comprehensive zero-trust security.
VPC Service Controls establishes a context-based security boundary around Google-managed services, while IAM governs identity-based authorization on specific resources. Legacy roles such as roles/editor grant broad read and write permissions across nearly all services in a project.
roles/editor. Inside the perimeter, a compromised application with roles/editor can modify configurations, delete data, or access resource metadata that is not fully restricted by service perimeters.private.googleapis.com inside a VPC Service Controls perimeter negates protection against insider data exfiltration, because private.googleapis.com exposes Google APIs that are not integrated with or enforced by VPC Service Controls.Owner, Editor, Viewer) violate the principle of least privilege by granting thousands of unnecessary permissions across unrelated services.private.googleapis.com allows workloads inside the VPC to reach unsupported APIs, creating an exfiltration path out of the perimeter.A workload required access to Google APIs not supported by VPC Service Controls via private.googleapis.com and did not store sensitive data; in that case, the recommended design is to isolate the unsupported workload into a separate project outside the service perimeter rather than mixing it with sensitive data.
Always pair a VPC Service Controls perimeter with least-privilege IAM roles and route Google API traffic exclusively through restricted.googleapis.com (with DNS resolving *.googleapis.com to restricted.googleapis.com) to close both identity and network exfiltration paths.
Granular IAM roles restrict which API actions a principal can perform on authorized resources, while VPC egress firewall rules control outbound IP traffic leaving Compute Engine VMs. Using private.googleapis.com enables VMs without external IP addresses to reach Google APIs over Google's internal network.
private.googleapis.com reaches shared public Google API endpoints, a malicious insider or compromised VM with credentials for an external Google Cloud project can still copy sensitive BigQuery or Cloud SQL exports to an attacker-controlled Cloud Storage bucket.private.googleapis.com provides access to almost all Google APIs and services, without enforcing organizational boundaries.The sole objective was to enforce least privilege on VMs and block outbound connections to third-party internet hosts, without needing to prevent data movement to unauthorized Google Cloud projects or block API access from external networks using stolen credentials.
For defense in depth around sensitive data stores, VPC Service Controls complements IAM and VPC firewall rules by blocking data movement across organizational perimeters and restricting API calls to authorized networks.
Securing cloud database environments against data exfiltration requires combining identity-based access control through Identity and Access Management (IAM) with context-based perimeter security through VPC Service Controls and VPC firewall rules. Rather than relying on a single control, this layered approach protects sensitive data from compromised credentials, malicious insiders, and overly broad network paths.
roles/editor role with granular predefined IAM roles (such as specific BigQuery Data Viewer or Cloud SQL Client roles) ensures the service account only holds the minimum permissions required for its workload.bq mk or gcloud storage cp) to external projects.restricted.googleapis.com) restricts traffic strictly to services supported by VPC Service Controls and prevents insiders from bypassing perimeter enforcement via private.googleapis.com.443 traffic to restricted.googleapis.com stops VMs from sending data to arbitrary external endpoints on the internet.Neither IAM nor network controls alone can stop all exfiltration vectors. Granular IAM restricts what an identity can do, while VPC Service Controls with restricted.googleapis.com and strict egress firewall rules restricts where data can travel and from which networks APIs can be reached.
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