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 in Google Cloud. The backend application virtual machines (VMs) reside in a private subnet and do not have external IP addresses to comply with company security policies.
The backend VMs have the following requirements:
Which networking solution should you implement to meet these requirements?
Assigning ephemeral external IP addresses directly attaches publicly routable IPv4 addresses to the network interfaces of the backend virtual machines. A public Cloud DNS zone publishes DNS records that are publicly queryable by any system connected to the global internet.
The application tier were a public-facing web server requiring direct inbound HTTP/HTTPS traffic from public internet clients rather than an isolated private backend tier.
Cloud NAT (Network Address Translation) is a fully managed, software-defined Google Cloud service that enables compute resources without external IP addresses to access the public internet for outbound traffic without allowing inbound connections.
Cloud DNS is a high-performance, resilient Domain Name System service running on Google's global infrastructure that provides both public and private managed DNS zones for internal and external name resolution.
This approach combines Google-native managed services to fulfill outbound connectivity and hybrid/internal naming requirements without provisioning dedicated proxy compute infrastructure or compromising network isolation.
VPC Network Peering connects two Virtual Private Cloud networks to exchange traffic using internal IP addresses. In a hybrid architecture, custom route advertisements can backhaul cloud internet traffic across Cloud VPN or Cloud Interconnect to an on-premises internet gateway.
Corporate security policies strictly mandated that all outbound internet traffic from cloud resources must be inspected and routed through an on-premises centralized firewall appliance before reaching the internet.
This configuration sets up a self-managed Compute Engine instance running network address translation software (such as iptables or a squid proxy) with IP forwarding enabled, acting as a manual gateway for all outbound traffic from private VMs.
The workload required deep packet inspection or custom protocol filtering proxy capabilities that are not supported by standard Layer 4 NAT services.
Change the inputs and watch how the outcome changes.

Change the networking approach and workload tier to see how outbound traffic, inbound traffic, and DNS behave.
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