An enterprise architectural team is designing a modernized data ingestion pipeline on Google Cloud. The system includes two separate workloads with distinct runtime requirements:
1. Event Ingestion Webhook: A lightweight HTTP service that receives intermittent data payloads, experiences rapid traffic spikes, requires scale-to-zero capacity during idle periods, and must minimize operational management overhead.
2. Custom Analytics Engine: A long-running backend data processing application that requires specific Linux kernel parameters (`sysctl` network tuning) and direct hardware device driver access.
Which TWO platform architectural decisions should you recommend to meet these requirements efficiently?
- Deploy the Event Ingestion Webhook on Cloud Run to leverage fully managed serverless container execution with automatic scaling to zero.Cevap
- Deploy the Custom Analytics Engine on Google Kubernetes Engine (GKE) with custom node pools configured for kernel tuning and specialized node setup.Cevap
- CDeploy the Event Ingestion Webhook on a multi-zone GKE cluster using Standard node pools to ensure baseline compute capacity is available for webhooks.
- DDeploy the Custom Analytics Engine on Cloud Run container instances with maximum CPU allocations.
- EDeploy both workloads together on App Engine Standard environment to minimize overall service deployment configuration.
Cevap
Deploying the Event Ingestion Webhook on Cloud Run and deploying the Custom Analytics Engine on Google Kubernetes Engine (GKE) with custom node configurations represent the optimal architectural design.
Cloud Run is optimized for stateless HTTP containers requiring automatic scaling to zero with zero infrastructure management. Google Kubernetes Engine (GKE) provides full node-level access and daemonset capabilities to apply custom sysctl kernel parameters and OS drivers for specialized batch processing.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Compute Platforms Based on Workload Characteristics and OS Level Access
Tahmini Süre:2m 0s