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 designing a scalable, highly available compute infrastructure on Google Cloud for a stateless web service. The deployment must satisfy the following architectural requirements:
Which strategy should the architect implement to automate and standardize this resource configuration?
This approach uses an external event-driven compute layer (Cloud Run functions) triggered by audit logs or Pub/Sub events to connect to newly created instances over SSH and execute configuration steps.
The scenario involved orchestrating complex, long-running external workflows spanning third-party clouds or on-premises management tools that lack native Google Cloud guest agent integration.
An instance template is an immutable Google Cloud resource used to define VM instance properties such as machine type, boot disk image, labels, network interfaces, service accounts, and metadata. A regional Managed Instance Group (MIG) uses this instance template to deploy, autoscale, and manage identical compute instances across multiple availability zones in a single region.
startup-script (or startup-script-url) metadata key instructs the Compute Engine guest agent to execute initialization tasks, install required dependencies, and launch runtime services upon boot.http://metadata.google.internal/computeMetadata/v1/).Using instance templates paired with regional MIGs is the foundational Google Cloud best practice for deploying stateless, autoscaling compute workloads, providing seamless lifecycle automation and configuration consistency.
Standalone VM deployments involve launching distinct virtual machine instances without grouping them into a managed controller. SSH key metadata is exclusively used by the guest OS to authorize and provision administrative user access via public-key authentication.
The workload consisted of a one-off, stateful development machine where user access control via SSH keys was the only operational concern.
An unmanaged instance group is a collection of individual, heterogeneous VM instances that do not share a common instance template and cannot be managed as a single coordinated pool. OS Config patch management is designed to automate operating system patch evaluation and updates.
The scenario required grouping pre-existing, non-identical legacy servers that must be connected to a load balancer without automated scaling or centralized lifecycle management.
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