Examkin

Soru

Zorluk: OrtaDeploying and Managing Google Kubernetes Engine (GKE) Clusters and Workloads

An infrastructure team is preparing to deploy a specialized network monitoring workload to Google Kubernetes Engine (GKE). The workload container requires running in privileged mode (`securityContext.privileged: true`) and modifying node-level kernel `sysctl` settings. Which GKE cluster operational mode should the team select to accommodate this requirement?

  1. Deploy a GKE Standard cluster and configure a node pool that permits privileged containers.Cevap
  2. B
    Deploy a GKE Autopilot cluster, because Autopilot automatically grants host kernel capabilities to pods requesting privileged status.
  3. C
    Deploy a GKE Autopilot cluster utilizing Spot node pools to bypass security baseline constraints for batch workloads.
  4. D
    Deploy a GKE Standard cluster and execute kubectl apply directly without initializing cluster credentials via gcloud container clusters get-credentials.

Cevap

Deploy a GKE Standard cluster and configure a node pool that permits privileged containers.
GKE Standard allows cluster administrators full control over node management, custom node pools, and container security contexts, enabling workloads to run with privileged capabilities and modify kernel parameters.

Adım Adım Çözüm

1
Analyze workload security requirements
Identified that the workload requires elevated capabilities, specifically privileged mode (`securityContext.privileged: true`) and host kernel modification.
Understanding workload requirements determines which GKE operational model is compatible.
2
Compare GKE Autopilot and GKE Standard operational boundaries
GKE Autopilot enforces locked-down node configurations and strict security policies, blocking privileged containers. GKE Standard provides full node management control.
Autopilot manages node infrastructure fully and restricts administrative node-level access, whereas Standard allows node OS customization.
3
Select the appropriate cluster operational model
Choose GKE Standard to support host-level kernel modifications and privileged containers.
GKE Standard is required whenever workloads need administrative host capabilities or non-standard node kernel parameters.

Anahtar Kavram

GKE Autopilot vs Standard Operational Boundaries
Bu soruyu puanla

Konular

Deploying and Managing Google Kubernetes Engine (GKE) Clusters and Workloads