nerdexam
GoogleGoogle

PROFESSIONAL-DATA-ENGINEER · Question #355

PROFESSIONAL-DATA-ENGINEER Question #355: Real Exam Question with Answer & Explanation

Option A is correct because the standard CI/CD pattern for Cloud Composer DAGs is to use Cloud Build triggered by Git commits to copy DAG files directly to the Cloud Storage bucket associated with each Composer environment - first to the dev bucket for testing, then to the prod b

Submitted by marco_it· Mar 30, 2026Building and operationalizing data processing systems

Question

You are creating the CI/CD cycle for the code of the directed acyclic graphs (DAGs) running in Cloud Composer. Your team has two Cloud Composer instances: one instance for development and another instance for production. Your team is using a Git repository to maintain and develop the code of the DAGs. You want to

Options

  • B1. Use Cloud Build to build a container with the code of the DAG and the KubernetesPodOperator to deploy the code to the Google Kubernetes Engine (GKE)
  • C1. Use Cloud Build to build a container and the KubernetesPodOperator to deploy the code of the DAG to the Google Kubernetes Engine (GKE) cluster of the
  • D1. Use Cloud Build to copy the code of the DAG to the Cloud Storage bucket of the development instance for DAG testing.

Explanation

Option A is correct because the standard CI/CD pattern for Cloud Composer DAGs is to use Cloud Build triggered by Git commits to copy DAG files directly to the Cloud Storage bucket associated with each Composer environment - first to the dev bucket for testing, then to the prod bucket after validation. Cloud Composer automatically syncs DAGs from its linked GCS bucket, making this the native, intended deployment path.

Options B and C are wrong because they use the KubernetesPodOperator to deploy containers to GKE, which is a pattern for running tasks inside a DAG (containerized workloads), not for deploying the DAG code itself. DAGs are Python files, not container images.

Option D is a partial answer - it only covers the development stage and omits the promotion step to the production instance, which is essential for a complete CI/CD cycle spanning both environments.

Memory tip: Think "DAGs live in buckets, not clusters." Cloud Composer reads DAG .py files from Cloud Storage - so your CI/CD pipeline should push files to GCS, not build and push Docker images. If you see KubernetesPodOperator in a deployment answer, it's describing task execution, not DAG deployment.

Topics

#Cloud Composer#CI/CD#Cloud Build#DAG Deployment

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-DATA-ENGINEER PracticeBrowse All PROFESSIONAL-DATA-ENGINEER Questions