Examkin

Question

Difficulty: HardPlanning Google Kubernetes Engine (GKE) Cluster Architectures

An online gaming company is planning a Google Kubernetes Engine (GKE) cluster architecture to host two distinct workloads:

1. A stateless, fault-tolerant match history analytics engine that processes asynchronous batch jobs with high sensitivity to compute costs.
2. A specialized security monitoring agent deployed as a DaemonSet that requires low-level custom Linux kernel sysctl parameter modifications on host nodes.

The cloud team wants to minimize cluster management overhead as much as possible while satisfying all technical requirements. Which TWO architectural decisions should the team implement? (Select 2 choices.)

  1. Deploy a GKE Standard cluster to accommodate the host node operating system kernel modification requirements.Answer
  2. Create a dedicated GKE Standard node pool utilizing Spot VMs for the stateless match history analytics workload.Answer
  3. C
    Deploy the entire workload suite on a GKE Autopilot cluster to eliminate node management overhead.
  4. D
    Provision Spot VMs for the primary node pool hosting the security monitoring DaemonSet to reduce base cluster costs.
  5. E
    Provision a GKE Autopilot cluster configured with custom node pool images to enable specialized Linux kernel parameters.

Answer

The team should deploy a GKE Standard cluster to allow host kernel sysctl tuning and configure a GKE Standard node pool using Spot VMs for the stateless batch analytics workload.
Choosing a GKE Standard cluster fulfills the requirement for custom sysctl kernel parameter tuning on host nodes, as GKE Autopilot restricts host-level OS changes. Additionally, creating a GKE Standard node pool with Spot VMs delivers maximum cost efficiency for the stateless, fault-tolerant match history analytics batch jobs.

Step-by-Step Solution

1
Evaluate the operational boundary between GKE Autopilot and GKE Standard.
GKE Autopilot locks down the underlying node operating system to guarantee managed security, preventing custom sysctl Linux kernel modifications. GKE Standard is mandatory when node-level kernel tuning is required.
Choosing Autopilot would violate the technical prerequisite of custom sysctl configuration.
2
Evaluate compute types for the stateless batch analytics engine.
The analytics engine is stateless, fault-tolerant, and cost-sensitive. Provisioning a dedicated node pool with Spot VMs significantly reduces compute expenses while allowing batch jobs to resume upon preemption.
Spot VMs are optimized for fault-tolerant workloads needing steep cost optimization.
3
Evaluate compute types for core infrastructure and security agents.
Critical system agents requiring reliable node coverage should run on standard compute instances rather than Spot VMs to prevent widespread daemon downtime during node reclamations.
Spot VMs are volatile and unsuitable for baseline security monitoring daemons.

Key Concept

GKE Cluster Mode Selection (Autopilot vs. Standard) and Spot VM Suitability
Rate this question

Topics

Planning Google Kubernetes Engine (GKE) Cluster Architectures

More questions from this topic