Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An organization is deploying a multi-tier application across Compute Engine virtual machines (VMs) in a Virtual Private Cloud (VPC) network. The web tier VMs scale dynamically, resulting in frequently changing internal IP addresses, and they require access to database tier VMs on TCP port 5432.
The cloud team wants to enforce strict ingress and egress traffic filtering based on workload identity rather than managing fluctuating IP address ranges.
Which configuration should the administrator implement?
Service account-based filtering in Google Cloud VPC firewall rules and Cloud Next-Generation Firewall (NGFW) policies allows network security controls to be defined using IAM service account identities attached to Compute Engine instances instead of static IP addresses or network tags.
web-tier@project.iam.gserviceaccount.com) to the web instances and a separate service account (e.g., db-tier@project.iam.gserviceaccount.com) to the database instances, traffic rules bind strictly to the assigned identity.db-tier with the source filter set to web-tier allowing only tcp:5432.iam.serviceAccountUser role, providing strict role-based access control.Using service accounts as source and target parameters is the Google Cloud standard for identity-driven microsegmentation. It ensures secure, automated, and scalable communication without operational overhead.
Static IP address filtering involves reserving fixed internal IP addresses for every VM instance and explicitly declaring those IP addresses or subnet CIDR blocks in firewall rule source and destination fields.
This approach would be appropriate if the workloads consisted of fixed, static legacy systems or external on-premises appliances with permanent, non-changing IP addresses that do not support Google Cloud IAM integration.
In-guest OS packet filtering relies on host-level firewall utilities such as iptables, nftables, or Windows Defender Firewall configured inside the operating system of each individual virtual machine.
This approach would be appropriate for defense-in-depth on standalone unmanaged bare-metal servers or non-cloud environments where centralized cloud SDN firewalls are unavailable.
Access scopes are a legacy mechanism used to define the default OAuth 2.0 permission boundaries for API calls made from a Compute Engine VM to Google Cloud service endpoints (such as Cloud Storage or BigQuery).
cloud-platform scope and managing specific permissions purely through IAM roles attached to service accounts.This approach would be relevant if applications running on the VMs needed authorization to interact directly with Google Cloud managed APIs (such as uploading objects to Cloud Storage) and required legacy scope configuration.
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