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.
You have deployed a multi-tier containerized application to a Google Kubernetes Engine (GKE) cluster. The architecture includes a frontend web server and a backend REST API service.
You need to expose the backend REST API service so that it can be accessed by the frontend pods within the cluster. The backend service must remain completely isolated and inaccessible from outside the GKE cluster.
Which Kubernetes Service type should you use?
The NodePort Service type exposes an application by opening a static port (typically in the range 30000–32767) on the external and internal IP addresses of every worker node in the GKE cluster.
You needed to allow external legacy systems or on-premises networks to communicate directly with cluster workloads using the nodes' IP addresses and designated high-range ports without creating a cloud load balancer.
The ExternalName Service type maps a Kubernetes Service name to an external DNS name (CNAME record) located outside the cluster, rather than routing traffic to pod selectors within the cluster.
db.external-provider.com) when queried by internal DNS.kube-proxy forwarding rules.The frontend pods needed to connect to an external third-party managed database running outside Google Cloud using a consistent internal service alias.
The LoadBalancer Service type automatically provisions a cloud provider load balancer (such as an external Google Cloud Network Load Balancer or Application Load Balancer) to route external internet traffic to your pods.
type: LoadBalancer Service in GKE provisions a public external IP address, making the backend REST API publicly reachable over the internet.The requirement was to expose the frontend web application directly to external users on the internet so they could access the application through a dedicated public IP address.
ClusterIP is the default Kubernetes Service type that provides an internal, cluster-scoped virtual IP address. It routes internal traffic among pods inside a Google Kubernetes Engine (GKE) cluster without exposing the service outside the cluster network boundaries.
backend-service.default.svc.cluster.local) or directly via the stable ClusterIP.spec.type is explicitly specified in a Service manifest, Kubernetes defaults to ClusterIP.kube-proxy rules on nodes without provisioning external cloud load balancers.Using ClusterIP perfectly matches the principle of least privilege and strict network segmentation for internal microservices. It delivers stable internal service discovery without incurring additional cloud costs or creating unintended security exposure.
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