Iac Ephemeral Environment Pipeline Architecture

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

Your enterprise DevOps team needs to implement an automated ephemeral environment strategy for feature branch testing on Google Cloud. Every time a developer opens a pull request (PR), an isolated environment containing dedicated Google Kubernetes Engine (GKE) workloads and supporting Google Cloud resources (such as Cloud Storage buckets and service accounts) must be created on-demand. The solution must ensure secure state isolation, prevent resource naming collisions across concurrent PRs, execute integration test suites, and automatically tear down all provisioned resources when the PR is closed or merged.

How should you architect this pipeline to meet these requirements?

Use Cloud Composer to trigger Google Cloud Deployment Manager to provision a brand new Google Cloud Organization folder and standalone billing account per pull request.

Create a scheduled Cloud Scheduler job that runs an hourly Cloud Build pipeline executing Terraform across all active Git branches using a single shared default workspace.

Configure Cloud Build triggers listening to PR events that invoke Terraform using dynamic state prefixes in Cloud Storage for environment provisioning, and configure an automated PR closure trigger to execute a destruction pipeline.

Deploy a permanent, multi-tenant GKE cluster with manual namespace assignments and execute non-declarative shell scripts in Cloud Build to provision GCP backend resources directly via gcloud commands.

Professional Cloud DevOps Engineer

Iac Ephemeral Environment Pipeline Architecture

Related questions