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 preparing to deploy a Google Kubernetes Engine (GKE) cluster to host internal backend microservices. The security team requires the following:
Which GKE cluster configuration should you implement to meet these requirements?
A standard GKE cluster provisions worker nodes with public (external) IP addresses by default. Applying custom VPC firewall rules at the subnet level filters traffic heading to Compute Engine instances based on specified IP protocols and ports.
The requirement allowed nodes to have public IP addresses but required blocking specific application port traffic entering existing public nodes without changing the cluster deployment model.
A private GKE cluster is a cluster configuration where worker nodes are assigned only internal RFC 1918 IP addresses, ensuring that nodes are isolated from direct inbound communication over the public internet. When combined with Master Authorized Networks, access to the cluster's Kubernetes API control plane is strictly limited to an approved list of specified CIDR IP blocks.
This approach directly leverages native Google Kubernetes Engine security controls designed precisely for isolated workload compute environments with restricted management access, requiring no third-party firewalls or complex custom proxy routing.
Private Google Access allows VM instances without external IP addresses to access Google APIs and services (such as Cloud Storage or BigQuery). Cloud NAT provides managed Network Address Translation for outbound-only internet connectivity.
kubectl commands.The primary goal was enabling worker nodes without external IP addresses to download container images or access external third-party APIs via outbound connections.
A private cluster with private endpoint only completely disables the control plane's public endpoint, allowing control plane access solely from within the VPC network or connected on-premises networks. Placing a Cloud Load Balancer in front of internal infrastructure typically exposes HTTP(S) applications using custom SSL termination policies.
kubectl operations.The organization had a strict policy banning all public control plane endpoints entirely and required all administrative access to transit through an internal private corporate interconnect with dedicated enterprise reverse proxies.
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