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 runs backend application workloads on Google Compute Engine virtual machine (VM) instances inside a custom VPC subnet. To maintain a strong security posture, none of the VM instances have external IPv4 addresses assigned to their network interfaces.
The applications on these VMs require access to the public internet to download critical operating system patches and repository updates. However, security policy strictly prohibits systems on the public internet from initiating inbound connections to these instances.
Which Google Cloud networking solution should you implement to meet these requirements?
Private Google Access allows Compute Engine instances that lack external IP addresses to reach the public IP addresses of Google APIs and services (such as Cloud Storage, BigQuery, and Artifact Registry) through internal routing.
The private VM instances only needed to interact with Google services—such as downloading container images from Artifact Registry or reading objects from Cloud Storage buckets—without needing to contact external third-party internet endpoints.
Cloud NAT (Network Address Translation) is a fully managed, distributed, software-defined Google Cloud networking service that enables resources without external IP addresses to access the public internet or external networks.
Cloud NAT is purpose-built to deliver scalable, secure, outbound-only internet connectivity for private Compute Engine instances without compromising security by exposing them to inbound internet traffic.

Assigning an ephemeral external IPv4 address directly attaches a public IP address from Google's pool to each VM instance's network interface, allowing direct two-way routing to and from the public internet.
The VM instances were internet-facing hosts, such as public bastion hosts or standalone web servers, that genuinely required dedicated external IP addresses to accept direct incoming connections.
An external Application Load Balancer is a reverse proxy system that distributes incoming client traffic from the public internet across a backend pool of instances or endpoints.
The primary goal was to securely expose a web application hosted on private VM instances to public internet users with global load balancing, SSL termination, and DDoS protection.
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