A healthcare organization is architecting a high-throughput genomic processing platform on Google Cloud. The core containerized pipeline executes compute-intensive analysis jobs that run continuously for up to 4 hours per execution. The pipeline depends on specialized third-party Linux kernel modules that must be loaded directly into the host operating system kernel, and it requires raw block access to high-performance local NVMe SSDs formatted with custom filesystem mount parameters. The organization wants to minimize operational overhead while fully satisfying all technical requirements. Which compute platform should the Cloud Architect select for this workload?
- ACloud Run jobs configured with custom memory limits and an extended 4-hour execution timeout
- BGoogle Kubernetes Engine (GKE) Autopilot mode deploying Pods with privileged security contexts
- Compute Engine Managed Instance Groups (MIGs) using a custom VM OS image pre-configured with the required kernel modules and local NVMe SSD scriptsCevap
- DApp Engine Flexible Environment with custom Dockerfiles configured to load the required kernel drivers upon container initialization
Cevap
Compute Engine Managed Instance Groups (MIGs) using a custom VM OS image pre-configured with the required kernel modules and local NVMe SSD scripts.
Compute Engine provides full Infrastructure-as-a-Service (IaaS) control over virtual machines. When a workload demands specific Linux kernel modules loaded at the host layer and custom local NVMe SSD storage initialization, custom Compute Engine OS images built into Managed Instance Groups provide the required control alongside operational automation.
Adım Adım Çözüm
Anahtar Kavram
Compute Platform Selection Constraints and Host OS Customization