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 are creating a new node pool in an existing Google Kubernetes Engine (GKE) cluster to host dedicated, high-priority workloads. You need to ensure that general application pods are not scheduled on these specific nodes, while allowing only dedicated pods configured with matching tolerations to run on them.
Which configuration should you apply to the node pool?
Maintenance windows and maintenance exclusions in GKE allow administrators to control the timing of automated control plane and node pool upgrades. By setting a maintenance window, you define recurring time periods during which GKE is permitted to perform automatic updates and repairs, helping prevent disruptions during peak business hours.
The requirement was to limit automated GKE node pool updates and version upgrades to specific hours during the weekend or night to minimize production disruption.
Node taints are a core Kubernetes scheduling primitive applied to nodes or entire GKE node pools to repel certain sets of pods. A taint consists of a key, value, and an effect (such as NoSchedule, PreferNoSchedule, or NoExecute). Nodes configured with a taint will reject any pod that does not possess a matching toleration in its pod specification.

workload=dedicated:NoSchedule) ensures that standard pods lacking a matching toleration cannot be scheduled on the nodes within this node pool.tolerations: [{key: "workload", operator: "Equal", value: "dedicated", effect: "NoSchedule"}]) are permitted to schedule onto these tainted nodes.gcloud container node-pools create --node-taints or via the Google Cloud console, applying uniformly across all worker nodes in the pool.Configuring node taints at the node pool level directly solves the requirement of restricting pod placement. Other features like network tags or maintenance windows govern network routing and upgrade schedules respectively, but only taints prevent the Kubernetes scheduler from placing standard pods on dedicated nodes.
Node auto-repair is a GKE management feature that continuously monitors the health of worker nodes in a node pool. If a node fails health checks consistently (for example, reporting a NotReady status for an extended period), GKE automatically initiates a drain and recreation process to restore node health.
The objective was to ensure that unhealthy or unresponsive nodes in the node pool are automatically detected and replaced without manual administrator intervention.
Compute Engine network tags are metadata strings assigned to the underlying virtual machine (VM) instances that comprise GKE nodes. They are primarily used in Virtual Private Cloud (VPC) firewall rules and route configurations to identify which VM instances a firewall rule or route should apply to.
The scenario required applying specific VPC firewall rules or routing policies to allow or deny network traffic to and from the nodes in a specific node pool.
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