Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is planning to migrate a three-tier web application from an on-premises data center to Google Cloud. Based on workload assessments, the architecture team has chosen a mixed migration approach:
You need to establish a testing and validation protocol to verify the application's functional integrity, scalability, and performance before executing the final production cutover.
Which validation strategy should you implement?
This option suggests completing the production cutover before executing performance and scaling validation, relying on Google Cloud Observability to monitor live telemetry (latency, traffic, errors, and saturation) and dynamically adjusting resource allocations in response to active production problems.
The workloads were already cut over and stabilized, and the objective was to enter the ongoing post-migration optimization phase using continuous monitoring and rightsizing recommendations.
This option focuses on supply chain security controls (such as container image vulnerability scanning in Artifact Registry and policy enforcement via Binary Authorization) combined with isolated, read-only database query verification during off-peak windows.
The primary requirement was strictly focused on implementing container supply chain security policies and non-intrusive database read verification prior to entering the formal workload testing phase.
This approach relies primarily on unit testing with mocked dependencies for the refactored services, combined with synthetic browser user interface (UI) tests against Cloud Run frontends, followed by a direct big-bang migration cutover without end-to-end performance benchmarking or dry runs.
The goal was strictly to conduct fast local software development checks for newly written frontend code without needing to validate end-to-end infrastructure performance, multi-tier data integration, or operational cutover timelines.
A structured validation and testing protocol is an essential phase in cloud migration that systematically assesses migrated workloads across multiple tiers and strategies. It ensures that workloads rehosted to Compute Engine, replatformed to Cloud SQL, and refactored onto Cloud Run satisfy functional specifications, performance Service Level Objectives (SLOs), and operational readiness criteria prior to cutting over production traffic.
Combining baseline benchmarking, end-to-end functional testing, staged load testing, and migration dry runs directly addresses the challenges associated with combining rehosting, replatforming, and refactoring strategies. It ensures that every tier is rigorously verified for stability and performance.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated