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.
Your organization wants to enforce centralized traffic filtering rules across virtual machine (VM) instances located in multiple projects. The security team requires an access control method where VM administrators cannot independently modify or bypass their instances' security classifications, overcoming the governance limitations of legacy network tags.
Which mechanism should the organization implement in Cloud NGFW policies to achieve this?
Custom static routes define the network paths that packets must follow to reach destination IP ranges from within a Virtual Private Cloud (VPC) network, specifying next hops such as VPN tunnels, instances, or default internet gateways.
The scenario required redirecting outbound network traffic destined for on-premises subnets through a specific Cloud VPN gateway or virtual appliance.
Resource Manager labels are lightweight key-value pairs used primarily for resource categorization, inventory querying, and billing allocation across Google Cloud resources.
The organization wanted to track billing and categorize infrastructure spending by department or environment name.
Legacy network tags are simple, plain-text string attributes added directly to the metadata of individual Compute Engine VM instances to apply VPC firewall rules or custom static routes.
roles/compute.instanceAdmin or compute edit access) can add, modify, or delete network tags on their VMs.The organization were using legacy VPC firewall rules in a single project without requiring centralized administrative separation between VM operators and security teams.
Secure tags (officially managed as Resource Manager tags) are strongly typed key-value pairs defined at the organization or folder level in Google Cloud. They are attached to resources, such as Compute Engine virtual machine (VM) instances, through formal tag bindings and managed via dedicated Identity and Access Management (IAM) roles.
compute.instances.create or compute.instances.setTags) can attach or remove, secure tags require distinct IAM permissions (roles/resourcemanager.tagUser and roles/resourcemanager.tagAdmin). VM administrators cannot alter tags unless explicitly granted permission on the tag values.
Using secure tags solves the fundamental security challenge of legacy network tags by ensuring that security classifications are strictly governed by central IAM policies. This ensures VM owners cannot unilaterally alter their firewall postures or bypass perimeter controls.
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