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 organization operates multiple Google Kubernetes Engine (GKE) clusters distributed across three distinct environments: Development, Staging, and Production.
The cloud architecture team needs to automate their cluster lifecycle and upgrade strategy to minimize downtime and prevent flawed updates from impacting critical production workloads. The requirements are:
Which strategy should you implement?
HAProxy in a managed instance group combined with a floating IP is an infrastructure routing and load balancing pattern frequently used in database high-availability topologies (such as AlloyDB Omni with Patroni) to direct client traffic transparently to an active primary node.
This pattern would be appropriate if you were designing a self-managed database infrastructure (such as AlloyDB Omni containers) requiring high-availability failover and client connection pooling between primary and standby database instances.
Looker Continuous Integration (CI) is a business intelligence development feature that automates SQL validation, content testing, and LookML code checks whenever developers submit pull requests to a LookML remote Git repository.
This approach would be correct if the objective was to automate quality assurance and linting for business intelligence models and data exploration queries during a Git pull request workflow.
Fleet-based rollout sequencing in Google Kubernetes Engine (GKE) is a native multi-cluster management feature that links clusters into a defined rollout pipeline. By grouping clusters into fleets representing distinct deployment stages (such as Testing, Staging, and Production), administrators can orchestrate sequential version qualification and cluster updates across environments.
--default-upgrade-soaking parameter defines an observation window between when an upstream fleet finishes upgrading and when downstream upgrades can commence, allowing potential regressions to surface in lower environments first.gcloud container fleet clusterupgrade commands or Terraform.Fleet-based rollout sequencing provides a declarative, Google-managed control plane for multi-cluster progressive delivery. It eliminates manual upgrade approvals, reduces configuration drift, and ensures high availability across mission-critical production environments.
Team scopes are fleet subdivisions designed to allocate cluster resources and namespaces to individual organizational teams within a single fleet. Configuring them without upstream dependencies means upgrades occur independently or simultaneously across scopes.
This structure would be suitable if the goal was simply to grant different developer teams scoped administrative control over namespaces within an existing fleet without managing progressive multi-cluster rollout sequences.
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