A DevOps engineering team is designing a continuous delivery architecture using Google Cloud Build, Google Cloud Deploy, and Google Kubernetes Engine (GKE). The application requires distinct manifest configurations across development, staging, and production environments using Kustomize. The pipeline must satisfy the following technical requirements: Developers must be able to use the same skaffold.yaml configuration file for both local development and remote CI/CD execution. The automated build step in Cloud Build must build container images, push them to Artifact Registry, and capture all immutable image digests. Google Cloud Deploy must automatically hydrate and substitute container image placeholders with exact SHA256 digests across the corresponding target profiles during release creation. Which configuration and workflow strategy should the team implement?

Configure `skaffold.yaml` with artifact definitions and environment-specific `profiles` referencing Kustomize paths. In Cloud Build, run `skaffold build` with `--file-output=artifacts.json --push=true --default-repo=[REPO]`, and pass `--build-artifacts=artifacts.json` to `gcloud deploy releases create`.: ### What the Solution Is This solution orchestrates a seamless continuous delivery workflow by coupling **Skaffold** artifact management and environment profiles directly with **Google Cloud Deploy** release management. Skaffold serves as the declarative configuration layer that bridges local developer workflows and automated cloud delivery pipelines. ### How It Meets the Requirements - **Unified Local and Remote Configuration**: Using a single `skaffold.yaml` containing root artifact configurations and target-specific `profiles` allows developers to test locally with `skaffold dev` or `skaffold run` while Cloud Deploy invokes the defined profiles during pipeline progression. - **Immutable Digest Capture**: Running `skaffold build` with the `--file-output=artifacts.json` flag produces a structured metadata file capturing the exact image repository tags and immutable `sha256` digests published to Artifact Registry. - **Deterministic Manifest Rendering**: Passing `--build-artifacts=artifacts.json` into `gcloud deploy releases create` enables Cloud Deploy (via internal Cloud Build execution) to run `skaffold render` and swap placeholder image references across all target profiles deterministically. ### Key Advantages - **Decoupled Architecture**: Separates image build automation from delivery pipeline definition while preserving end-to-end traceability. - **Immutable Deployments**: Guarantees that the exact container binary built in CI is promoted without tag drift across targets. - **Native Profile Integration**: Maps delivery pipeline target profiles directly to Kustomize directory overlays. - **Automated Manifest Hydration**: Eliminates manual manifest manipulation scripts such as `sed` or `kustomize edit` in CI jobs. ### Why This Is Optimal This architecture represents the native Google Cloud best practice for continuous delivery. It allows Cloud Deploy to manage release progression and target rendering through standard Skaffold CLI contracts without requiring custom synchronization scripts or fragile intermediate storage steps.

Skaffold Cloud Deploy Kustomize Orchestration | Professional Cloud DevOps Engineer

Skaffold Cloud Deploy Kustomize Orchestration

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.

A DevOps engineering team is designing a continuous delivery architecture using Google Cloud Build, Google Cloud Deploy, and Google Kubernetes Engine (GKE). The application requires distinct manifest configurations across development, staging, and production environments using Kustomize.

The pipeline must satisfy the following technical requirements:

Developers must be able to use the same skaffold.yaml configuration file for both local development and remote CI/CD execution.
The automated build step in Cloud Build must build container images, push them to Artifact Registry, and capture all immutable image digests.
Google Cloud Deploy must automatically hydrate and substitute container image placeholders with exact SHA256 digests across the corresponding target profiles during release creation.

Which configuration and workflow strategy should the team implement?

Configure skaffold.yaml with deploy.kustomize and set the build execution to googleCloudBuild. In Cloud Build, run skaffold apply --offline=true and upload the resulting manifests to a Cloud Storage bucket linked to Cloud Deploy.

Configure dynamic Skaffold modules for each environment referencing Helm charts with deploy.helm. In Cloud Build, execute skaffold render --output=rendered.yaml and pass --manifests=rendered.yaml to gcloud deploy releases create.

Configure skaffold.yaml with artifact definitions and environment-specific profiles referencing Kustomize paths. In Cloud Build, run skaffold build with --file-output=artifacts.json --push=true --default-repo=[REPO], and pass --build-artifacts=artifacts.json to gcloud deploy releases create.

Configure skaffold.yaml with lifecycle hooks under each profile to invoke kustomize edit set image. In Cloud Build, execute standard docker build commands and specify individual image URIs using the --images flag during gcloud deploy releases create.

Professional Cloud DevOps Engineer

Skaffold Cloud Deploy Kustomize Orchestration

Related questions