What services should Helicopter Racing League use for global live streaming?

Use Media CDN (or Cloud CDN with a Global External Load Balancer) for broadcast delivery, with Cloud Storage as the origin for recorded content and Live Stream API for ingest. Transcoding happens before delivery with Transcoder API.

How does Helicopter Racing League handle large, unpredictable audience spikes?

Design for elasticity: Cloud CDN caches at edge locations close to viewers, Pub/Sub buffers race telemetry for ingest bursts, and managed services (GKE or managed instance groups) autoscale behind a global load balancer. Serving cached content from the edge removes nearly all origin load during spikes.

Where should race telemetry be stored for analytics?

Race telemetry flows through Pub/Sub into BigQuery. BigQuery's streaming inserts handle real-time dashboards during the race, and its storage handles historic race analysis without separate warehouse infrastructure.

Why not run Helicopter Racing League on-premises video servers?

On-premises servers cannot absorb race-day audience spikes. A global CDN combined with autoscaling backends means the infrastructure grows and shrinks with the audience, which is impossible with fixed on-premises capacity.

Is the Helicopter Racing League case study still on the GCP PCA exam?

Yes. Helicopter Racing League is one of the official case studies in the current Professional Cloud Architect exam guide, alongside EHR Healthcare, Mountkirk Games, TerramEarth, Cymbal Retail, Altostrat Media, and KnightMotives Automotive.

Case Study Deep Dive

Helicopter Racing League Case Study: Global Live Streaming at Scale

September 18, 2026 9 min read By GCP Expert Team

Where EHR Healthcare tests migration discipline and Mountkirk tests managed-services thinking, Helicopter Racing League (HRL) tests one specific skill: designing for global, spiky, live media distribution. If the exam question mentions "live streaming," "transient audience," or "broadcast," you're in HRL territory.

The Mission: Broadcast Racing to a Global Audience

Helicopter Racing League runs a worldwide racing series. Each race is broadcast live in ultra-low latency with 4K video, telemetry overlays, and real-time leaderboards. The audience is global and wildly unpredictable: a championship race in one region can pull tens of millions of concurrent viewers, while the following week's regional heat draws a fraction of that. Their existing hosting can't absorb those spikes.

Exam takeaway: The word "transient" in the case study is a hint. HRL's workload is bursty, so the correct answers almost always favor managed, autoscaling, edge-delivered services over fixed-capacity infrastructure.

The Architecture Examiners Expect

1. Content Delivery: Media CDN + Cloud CDN

For live and recorded race video, Google's Media CDN (or Cloud CDN with a Global External Load Balancer for recorded clips) is the correct delivery layer. It caches video segments at edge locations near viewers, which solves two problems at once: low latency for the audience, and near-zero origin load during the spikes that break on-premises systems. Recorded races also use the Transcoder API to produce multiple bitrate renditions for adaptive bitrate streaming.

2. Race Telemetry: Pub/Sub → BigQuery

Helicopter telemetry (position, altitude, speed, battery, engine data) streams from aircraft sensors in real time. The expected pattern is Pub/Sub for ingestion buffering, then BigQuery streaming inserts so commentators and fan dashboards see race standings live. Historic telemetry stays in BigQuery for season-long comparative analytics - no separate data warehouse needed (see our TerramEarth deep dive for the closely related connected-vehicle variant of this pattern).

3. Compute: Managed, Autoscaling, Regional

Where HRL needs custom logic (leaderboards, race analytics APIs, viewer interactivity), managed compute wins on the exam: GKE with regional clusters behind a Global External Load Balancer, or Cloud Run for stateless APIs. Under no circumstances does a fixed on-premises or single-region VM fleet satisfy the "transient audience" requirement.

Frequently Asked Questions (FAQ)

How does HRL keep video quality consistent worldwide?

Adaptive bitrate streaming solves this: the Transcoder API produces multiple renditions of each stream, and Media CDN serves the best quality each viewer's connection can sustain at that moment.

What protects the broadcast from DDoS during a championship race?

Cloud Armor policies attached to the global load balancer filter volumetric attacks before they reach origin infrastructure - essential when millions of concurrent viewers and attackers can share the same event window.

Should race analytics run real-time or batch?

Both. Live dashboards during the race use BigQuery streaming inserts; post-race strategic analysis runs as scheduled batch queries over the same tables. The architecture doesn't change - only the query pattern does.

Why is this case study such good exam prep?

Because it isolates ONE decision most candidates get wrong: capacity planning. Fixed capacity always fails for "transient audience" scenarios. If the answer involves buying permanent infrastructure, it's wrong for HRL.

Summary Checklist

If you see Helicopter Racing League, look for these keywords in the correct answer:

Media CDN / Cloud CDN for global delivery at the edge
Autoscaling (never fixed capacity for a transient audience)
Pub/Sub buffering for telemetry bursts
BigQuery for race analytics
Global External Load Balancer routing to the nearest healthy region

Practice the HRL scenario

Our mock exams include Helicopter Racing League scenarios alongside all six other official PCA case studies - free, timed, and scored.

Take a Free Mock Exam