Examkin

Question

Difficulty: HardDesigning Infrastructure for Technical Requirements and High Availability

An enterprise telemetry ingestion system deployed on Google Cloud processes real-time vehicle fleet data. The solution requires hosting simple stateless HTTP ingestion microservices with minimal operational overhead, establishing a resilient hybrid connection to an on-premises data center with a sustained bandwidth requirement of 12 Gbps, and maintaining high availability without triggering cascading load balancer failures when backend databases experience transient latency spikes.

Which TWO architectural choices should you include in the design to satisfy these technical requirements? (Select TWO.)

  1. Deploy the stateless HTTP ingestion microservices on Cloud Run and configure the load balancer health checks to target a dedicated shallow endpoint that returns HTTP 200 without executing downstream database queries.Answer
  2. Provision Dedicated Interconnect with redundant VLAN attachments across separate metro locations to handle the sustained 12 Gbps hybrid network connectivity.Answer
  3. C
    Deploy a multi-zone GKE cluster with custom ingress controllers and autoscaling node pools to host the stateless HTTP ingestion microservices.
  4. D
    Establish multiple HA VPN tunnels with Cloud Router BGP to aggregate bandwidth for the sustained 12 Gbps hybrid data connection.
  5. E
    Configure the load balancer health checks to execute a lightweight database ping query on every probe to verify full end-to-end application stack health.

Answer

The correct solution involves deploying the stateless microservices on Cloud Run with shallow health checks, and provisioning Dedicated Interconnect across redundant metro locations for the sustained 12 Gbps traffic flow.
Cloud Run is the optimal compute platform for stateless microservices because it eliminates server management overhead while scaling automatically. Pairing Cloud Run (or load balancers) with shallow health check endpoints ensures instances are not marked unhealthy when underlying databases experience temporary latency spikes. For hybrid connectivity, Dedicated Interconnect is required to reliably transport sustained bandwidth exceeding 10 Gbps across redundant metro locations.

Step-by-Step Solution

1
Select compute architecture for stateless HTTP microservices
Cloud Run provides serverless autoscaling with zero node management overhead for stateless web endpoints.
GKE adds unnecessary management complexity and fixed baseline compute costs for simple stateless HTTP services.
2
Determine high-throughput hybrid connectivity mechanism
Dedicated Interconnect supplies 10 Gbps or 100 Gbps physical circuits capable of cleanly supporting a sustained 12 Gbps payload across dual metro locations.
HA VPN is capped at 3 Gbps per tunnel, making it inefficient and prone to throttling for sustained 12 Gbps traffic demands.
3
Design resilient load balancer health checking strategy
Configure a shallow health check endpoint (such as HTTP /healthz returning 200 OK) that evaluates local web server health only.
Probing deep database dependencies in health checks causes backend instances to be declared unhealthy during transient database slowness, triggering cascading failures.

Key Concept

High-availability cloud architecture design balancing minimal operational overhead, scalable hybrid bandwidth, and resilient health check isolation.
Rate this question

Topics

Designing Infrastructure for Technical Requirements and High Availability