1.2 Managing Infrastructure PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   A DevOps engineer wants to write a Python script that programmatically creates a Compute Engine instance in a Google Cloud project. Which Google Cloud client library should the script use?

   • Agoogle-cloud-pubsub
   • Bgoogle-cloud-storage
   • Cgoogle-cloud-resource-manager
   • Dgoogle-cloud-compute
   Reveal Solution Discussion Select an answer first
2. 2application · medium

   A startup is adopting IaC for the first time. They have a small DevOps team and want to enforce code review and version control on all infrastructure changes. They also want to minimize the number of tools to learn. Which approach aligns with Google-recommended practices?

   • AUse Cloud Shell to run Terraform commands directly and document changes in a shared wiki
   • BStore Terraform configurations in a Git repo with a pull-request-based workflow and use Cloud Build to plan and apply on merge
   • CCreate a single Terraform state file stored locally on the lead engineer's workstation
   • DUse Infrastructure Manager to deploy Terraform configs from a Cloud Storage bucket without a Git repo
   Reveal Solution Discussion Select an answer first
4. 3application · medium

   Your organization uses a multi-repo Git structure and wants to deploy infrastructure changes using a GitOps approach. They want to use a Google Cloud managed service that can sync their Git repo to their GKE cluster and also manage GCP resources outside the cluster. Which service should they use?

   • AHelm with a custom controller
   • BConfig Sync with Config Connector
   • CCloud Build with a trigger on the Git repo
   • DInfrastructure Manager with a Git repo source
   Reveal Solution Discussion Select an answer first
5. 4expert · hard

   A large enterprise is standardizing on Terraform for all GCP infrastructure. They have a central platform team that owns the 'landing zone' (networking, org policies, folders) and multiple application teams that own resources within their own projects. They want to enforce that application teams cannot modify the landing zone, but they also want to avoid duplicating common configurations. Which approach best balances governance and autonomy?

   • AUse separate Terraform state files and repositories for the platform and application teams, with the platform team's state protected by IAM, and use Cloud Foundation Toolkit modules for common patterns
   • BUse Config Connector in each application team's cluster to manage all GCP resources, including the landing zone
   • CUse a single Terraform state file and repository managed by the platform team, where application teams submit pull requests
   • DUse Infrastructure Manager to deploy all Terraform configs from a single repository, with no separation of state
   Reveal Solution Discussion Select an answer first
6. 5expert · hard

   A company is using a GitOps approach with Config Sync to manage their GKE clusters. They now want to manage their Cloud SQL instances and VPC networks using the same GitOps workflow. They have a requirement that changes to these GCP resources must be reviewed by the security team before being applied. Which approach best meets this requirement?

   • AUse Config Sync to sync all GCP resources from the same repository as the Kubernetes manifests
   • BUse Terraform with a GitLab CI/CD pipeline that requires a security approval before applying
   • CInstall Config Connector and use a separate Git repository for GCP resources, with a Cloud Build trigger that runs a security review step before syncing
   • DUse Cloud Foundation Toolkit to deploy Cloud SQL and VPC, but manage them separately from the GitOps workflow
   Reveal Solution Discussion Select an answer first