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 migrating a suite of core business workloads from an on-premises data center to Google Cloud. Currently, the operations team provisions Google Cloud projects, Virtual Private Cloud (VPC) networks, and Compute Engine virtual machines using manual console operations and ad-hoc shell scripts. This approach has led to severe configuration drift across staging and production environments, untracked changes, and high operational risk during rollbacks.
As the Cloud Architect, you must advise the development and operations teams on establishing a standardized, automated deployment strategy to manage these migrated environments consistently throughout their lifecycle.
What should you recommend?
Configuration management (CM) tools such as Ansible, Puppet, Chef, and SaltStack are primarily designed to automate software installation, patch management, and OS-level configuration on existing virtual machines or bare-metal instances.
While CM tools can configure operating systems and run command modules, they are not optimized for cloud-level infrastructure orchestration, such as provisioning Google Cloud projects, VPC networks, and Cloud Load Balancing. CM tools generally lack robust native state tracking and state reconciliation engines needed to detect cloud resource drift or perform fine-grained dependency resolution across complex cloud platform architectures.
The primary goal were to configure operating system software packages, maintain application runtime files, or enforce internal system compliance across existing Compute Engine instances after they have already been provisioned.
In modern cloud architectures, teams typically combine tools: Terraform or Deployment Manager provisions the underlying cloud infrastructure (VMs, networks, IAM), while Ansible or Puppet configures the operating systems inside those VMs if immutable OS images are not used.
Imperative scripting involves authoring sequential shell scripts using command-line interfaces such as the Google Cloud CLI (gcloud) or direct REST API calls. These scripts explicitly specify each action step-by-step to create and configure resources.
Imperative scripts execute commands sequentially without tracking the lifecycle or desired end-state of resources. If a script fails midway, resources are left in an incomplete, indeterminate state. Furthermore, imperative scripts do not provide automated drift detection; running the script again often results in errors due to existing resources rather than idempotently converging to the desired configuration.
You needed to execute quick, one-off proof-of-concept tasks or run simple maintenance utilities in a sandboxed experimental environment.
Declarative IaC is explicitly favored over imperative CLI scripting for enterprise migrations because declarative engines evaluate dependency graphs and automatically calculate the necessary CRUD (create, read, update, delete) operations.
Infrastructure as Code (IaC) is the practice of defining, provisioning, and managing cloud infrastructure using human-readable, declarative configuration files rather than manual processes or imperative scripts. Tools such as Terraform and Google Cloud Deployment Manager allow teams to specify the desired end-state of cloud resources, leaving the underlying engine to determine the necessary API calls to create, modify, or destroy resources to match that state.
terraform plan) before applying changes, allowing teams to review intended modifications prior to execution.Adopting declarative IaC paired with version control and CI/CD represents the industry standard for cloud lifecycle management. It directly addresses environment drift, human error, and rollback challenges, establishing an automated, scalable, and audit-compliant deployment model.
This approach relies on human operators clicking through the Google Cloud console to create projects, VPCs, and VMs, while using VM Manager (a suite of tools within Compute Engine) to manage operating system patch compliance and OS configuration policies.
Manual provisioning via the web console fails to satisfy the requirements for consistency, repeatability, and auditability. It introduces human error, cannot be integrated into automated CI/CD pipelines, and leaves no version-controlled code history. Furthermore, VM Manager operates exclusively at the guest OS level of Compute Engine instances and cannot manage cloud-level resources like VPC subnets, firewall rules, Cloud Routers, or project creation.
The organization had already provisioned infrastructure via code and solely needed an automated mechanism to manage operating system updates, package installations, and OS patches on Compute Engine instances.
Best practices for enterprise cloud deployments dictate that all foundational cloud architecture should be codified via declarative IaC tools, avoiding manual console modifications for production environments.
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