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 fleet of web servers on Compute Engine instances inside a Virtual Private Cloud (VPC) network. The web servers must accept incoming public web traffic on TCP port 80.
All existing lower-priority default rules blocking unapproved traffic must remain intact, and the new rule must apply strictly to inbound requests.
Which combination of firewall rule attributes should the administrator configure to allow this traffic?
In Google Cloud VPC networking, a VPC firewall rule with ingress direction inspects and filters incoming traffic directed toward virtual machine instances. Firewall rules are defined by specific attributes including traffic direction, action, source or destination filters, protocols, ports, and rule priority.
0.0.0.0/0): Specifies the entire IPv4 address space, allowing legitimate incoming web requests from any public client on the internet.tcp:80): Accurately restricts access exclusively to standard HTTP web traffic over the TCP transport layer, blocking unintended protocols and ports.65535), ensuring traffic is permitted while honoring normal rule evaluation ordering.
0 to 65535) ensure rules with lower numerical values take precedence over higher numerical values.This configuration directly satisfies all security and operational criteria with minimal attack surface exposure. It enforces strict protocol and port constraints on inbound connections while using a standard priority value that properly precedes Google Cloud's default catch-all rules.
This rule explicitly rejects incoming UDP packets arriving on port 80 from all IPv4 addresses at a priority of 1000.
The organization needed to actively mitigate an amplification attack over UDP on port 80 before any other rules were processed.
Standard web traffic requires the TCP three-way handshake to establish reliable connections, making TCP the essential protocol attribute for HTTP/HTTPS web endpoints.
This configuration attempts to permit Internet Control Message Protocol (ICMP) traffic using an invalid port specification and the lowest possible priority (65535).
ping). It does not transport HTTP application payload data.icmp:80 syntactically invalid.65535 is reserved for implied default rules and is overridden by any custom rule with a lower numerical priority (1–65534).ping and traceroute.0 (highest priority) to 65535 (lowest priority).The goal was to configure the lowest-priority default fallback rule to allow network diagnostics across the entire VPC.
When creating custom allow rules in Google Cloud, administrators should assign priority values between 0 and 65534 (typically 1000 by default) so that they take precedence over default system rules.
This configuration creates an egress firewall rule intended to manage outbound traffic leaving Compute Engine VM instances toward external destination IP addresses.
65535.The requirement called for restricting outbound communication from backend database servers so they could only contact external software repositories on port 80.
Confusing ingress (inbound) and egress (outbound) is a common misconception when configuring network firewalls. Ingress rules require source filters, whereas egress rules require destination filters.
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