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 has deployed a multi-tier application across several Compute Engine virtual machines (VMs) in a single Virtual Private Cloud (VPC) network. You need to configure a firewall rule to allow inbound HTTPS traffic on TCP port 443 from the public internet exclusively to instances acting as web frontends. Database instances and internal worker VMs must not be accessible over this port from the internet.
You want to configure this security boundary using Google Cloud's recommended traffic management mechanism.
What should you do?
This configuration creates a broad, low-priority ingress firewall rule that applies to every virtual machine in the VPC network.
65535 is the lowest possible custom priority in Google Cloud firewall rules (reserved for default implied rules). If other custom deny rules exist with higher priority, this rule could be overridden unexpectedly, but more importantly, it does not provide granular filtering between VM tiers.1000 evaluates before 5000). Priority 65535 cannot override custom rules.You needed a global catch-all baseline rule that applied uniformly to every single virtual machine inside the entire VPC network regardless of their function or tier.
Identity and Access Management (IAM) roles manage administrative authorization (control plane access) for users, groups, and service accounts. The Compute Network Admin (roles/compute.networkAdmin) role grants permissions to create, modify, and delete networking resources such as VPC networks, subnets, and firewall rules.
roles/compute.networkAdmin to the frontend VM service account violates the principle of least privilege by allowing workloads on those VMs to reconfigure the organization's entire network topology.You needed to grant an automated deployment tool or network engineer administrative permission to create and manage VPC firewall rules in the project.
Network tags are user-defined metadata strings assigned to Compute Engine virtual machine instances. In Google Cloud VPC firewall configurations, target tags allow administrators to apply specific ingress or egress firewall rules only to the instances that carry those matching tags, rather than applying the rule to all instances across the entire VPC network.
web-frontend to frontend VM instances and specifying that tag in the target tags field of the firewall rule, Google Cloud ensures that only those tagged VMs evaluate and enforce the rule.0.0.0.0/0 with protocol/port tcp:443 permits incoming encrypted web traffic from any client on the public internet.
Using network tags to specify targets is Google Cloud's foundational method for defining security boundaries among VM instances within the same subnet or VPC. It satisfies all functional and security requirements cleanly while adhering to standard GCP network management practices.
Egress firewall rules regulate outbound network traffic originating from Compute Engine VM instances to external or internal destinations. They do not manage or filter incoming traffic originating from the internet.
65535) that permits all outbound traffic from all instances unless explicitly overridden.INGRESS to evaluate incoming packets from clients.The requirement were to restrict or permit database and worker VMs from initiating outbound connections to external third-party HTTPS APIs over port 443.
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