Examkin

Question

Difficulty: MediumPlanning Google Kubernetes Engine (GKE) Cluster Architectures

A global logistics provider is designing a Google Kubernetes Engine (GKE) cluster strategy for two distinct workloads: a critical stateless routing microservice that requires automated infrastructure provisioning without administrative node management, and a non-critical, fault-tolerant batch analytics processing job designed to minimize compute costs. Which TWO architectural decisions should the engineering team implement to satisfy these requirements?

  1. Deploy the stateless routing microservice in a GKE Autopilot cluster to eliminate node management and infrastructure maintenance overhead.Answer
  2. Provision a GKE Standard node pool utilizing Spot VMs to run the fault-tolerant batch analytics workload at a significantly discounted compute rate.Answer
  3. C
    Deploy the real-time routing microservice on a Spot VM node pool to lower infrastructure cost for critical API traffic.
  4. D
    Provision a GKE Standard cluster with manually configured node pools for the routing microservices to minimize operational management overhead.
  5. E
    Select GKE Autopilot for workloads that require custom host OS kernel sysctl parameters for specialized network optimization.

Answer

The correct decisions are to deploy the stateless routing microservice in a GKE Autopilot cluster and to provision a GKE Standard node pool utilizing Spot VMs for the batch analytics workload.
Deploying the stateless routing microservice on GKE Autopilot eliminates the need to manage, patch, or scale underlying node infrastructure. Utilizing Spot VMs in a GKE Standard node pool for fault-tolerant batch workloads dramatically reduces compute expenses while accounting for potential instance interruptions.

Step-by-Step Solution

1
Analyze the operational requirements for the critical routing microservice.
Identified that zero node management overhead and automated cluster operations are required for stateless workloads.
GKE Autopilot handles node lifecycle, security patching, and autoscaling automatically, satisfying zero node management overhead.
2
Analyze the compute and availability requirements for the batch analytics processing job.
Identified that the job is non-critical, fault-tolerant, and targeted at minimizing compute expenses.
Spot VMs offer steep discounts (up to 60-91%) compared to standard compute instances, making them optimal for interruptible batch workloads.
3
Evaluate the architectural constraints of GKE Autopilot vs. Standard and Spot VM suitability.
Confirmed that Autopilot eliminates node overhead for stateless apps and Spot node pools in GKE Standard accommodate fault-tolerant batch processing.
Critical workloads should not run on Spot VMs due to preemption risk, and Autopilot cannot be used if host OS sysctl kernel adjustments are mandatory.

Key Concept

GKE Autopilot vs Standard Operational Boundaries & Spot VM Workload Suitability
Rate this question

Topics

Planning Google Kubernetes Engine (GKE) Cluster Architectures

More questions from this topic