Hard1 markMultiple Choice
Subtask 1.4: Migration PlanMigrationCompute EngineCase Study

GCP PCA · Question 01 · Migration Plan

CASE STUDY: TechStream Gaming
Overview: Gaming company, 500 employees, $100M revenue. 200 on-prem servers (US/EU), MySQL 5TB. 2M peak users. $150K/mo cost.
Business Req: Reduce cost 40%, 5x growth, 3 new regions, daily deployments.
Execs: CEO wants scale; CFO caps budget at $100K/mo; CTO needs 99.95% uptime, notes team has limited cloud skills.
Tech Req: <100ms global latency, real-time analytics, 5x seasonal spikes, EU data residency, DDoS protection.
Constraints: 12-month migration, max 4-hour downtime.

QUESTION:
Which migration strategy should you recommend for the legacy gaming application to meet the 12-month timeline and team skill constraints?

Answer options:

A.

Refactor the application into microservices and deploy to Google Kubernetes Engine (GKE).

B.

Rehost the application to Compute Engine using Migrate for Compute Engine.

C.

Replatform the application to Cloud Run to minimize operational overhead.

D.

Replace the application with a managed gaming backend service.

How to approach this question

Analyze the constraints: 12 months and limited cloud skills. Choose the strategy with the lowest barrier to entry.

Full Answer

B.Rehost the application to Compute Engine using Migrate for Compute Engine.✓ Correct
A 'Rehost' (Lift and Shift) strategy is the most appropriate when facing tight timelines and limited cloud-native skills. Once in the cloud, the team can gradually modernize (Replatform/Refactor) as they upskill.

Common mistakes

Choosing Refactor (A) because it's the 'best' cloud-native approach, ignoring the business constraints of time and skills.

Practice the full GCP Professional Cloud Architect Practice Exam 5

50 questions · hints · full answers · grading

More questions from this exam