Examkin

Soru

Zorluk: OrtaPlanning Google Kubernetes Engine (GKE) Cluster Architectures

A financial services organization is planning a Google Kubernetes Engine (GKE) cluster architecture to host two distinct workloads:

1. A high-throughput ledger ingestion service that requires custom sysctl kernel parameter tuning on the underlying node OS to optimize TCP socket buffers.
2. A stateless risk-analysis batch processing pipeline that is fault-tolerant and can handle unexpected node terminations.

The infrastructure team needs to ensure that node OS customizations are supported while minimizing compute expenses for the batch processing workload.

Which GKE cluster configuration should the team select?

  1. Deploy a GKE Standard cluster, configuring a standard node pool with custom sysctl settings for the ledger service, and a Spot VM node pool for the stateless batch processing pipeline.Cevap
  2. B
    Deploy a GKE Autopilot cluster and configure the required sysctl kernel parameters directly within the pod deployment manifest for the ledger ingestion service.
  3. C
    Deploy a GKE Standard cluster utilizing Spot VMs for both the ledger ingestion node pool and the batch processing node pool to minimize total compute costs.
  4. D
    Deploy a GKE Autopilot cluster and configure Horizontal Pod Autoscaler (HPA) to provision custom OS kernel configurations dynamically when workload traffic scales up.

Cevap

Deploy a GKE Standard cluster with a node pool configured with custom sysctl settings for the ledger service, and a Spot VM node pool for the fault-tolerant batch processing workload.
GKE Standard is required when workloads demand underlying OS kernel tuning (such as custom sysctl settings). Combining a standard node pool for the critical ledger service with a Spot VM node pool for the stateless, fault-tolerant batch workload satisfies both the OS customization requirement and the cost-optimization objective.

Adım Adım Çözüm

1
Evaluate operational mode requirements for OS customization.
GKE Autopilot locks down node configuration and does not support custom sysctl kernel parameter modifications on nodes. Therefore, a GKE Standard cluster is required.
Workloads requiring low-level Linux kernel parameter changes must run on GKE Standard node pools where node configurations can be customized.
2
Select the appropriate compute instance type for the stateless batch processing workload.
Spot VMs offer significant cost savings for stateless, fault-tolerant workloads that can tolerate preemption.
Batch processing can handle sudden termination and retries, making Spot VMs ideal for cost optimization.
3
Select the appropriate compute instance type for the ledger ingestion service.
Standard (on-demand) VM node pools ensure uninterrupted availability for latency-sensitive, critical ingestion tasks.
Critical ingestion workloads should not run on preemptible instances to avoid service disruption.

Anahtar Kavram

Selecting between GKE Standard and Autopilot based on OS kernel customization needs, alongside Spot VM integration for cost optimization.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Planning Google Kubernetes Engine (GKE) Cluster Architectures

Bu konudan daha fazla soru