Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise is establishing a secure continuous integration and continuous delivery (CI/CD) architecture across Google Kubernetes Engine (GKE) clusters using Git, Jenkins, and a GitOps delivery controller. Corporate security policies require eliminating direct deployment access from CI runners to GKE clusters and prohibiting the use of individual human credentials for automated pipeline tasks.
How should the DevOps team design this pipeline to enforce automated state reconciliation and secure execution?
Configure the in-cluster GitOps controller to trigger Jenkins webhook endpoints to pull raw binary artifacts and push them directly to GKE nodes via SSH.
Configure Jenkins to commit built container images directly to the Git repository, and configure the GitOps controller to run with default unauthenticated public access.
Configure Jenkins to execute deployment scripts using kubectl apply directly against the GKE control plane by mounting individual developer personal access tokens into the Jenkins agent workspace.
Configure Jenkins to update deployment manifests in a dedicated Git configuration repository using a machine user token, and configure the in-cluster GitOps controller with credentials stored in a Kubernetes Secret to pull and reconcile the desired state.
Configure the in-cluster GitOps controller to trigger Jenkins webhook endpoints to pull raw binary artifacts and push them directly to GKE nodes via SSH.
Configure Jenkins to commit built container images directly to the Git repository, and configure the GitOps controller to run with default unauthenticated public access.
Configure Jenkins to execute deployment scripts using kubectl apply directly against the GKE control plane by mounting individual developer personal access tokens into the Jenkins agent workspace.
Configure Jenkins to update deployment manifests in a dedicated Git configuration repository using a machine user token, and configure the in-cluster GitOps controller with credentials stored in a Kubernetes Secret to pull and reconcile the desired state.
This architecture establishes a pull-based GitOps deployment pattern where continuous integration (CI) and continuous delivery (CD) responsibilities are cleanly decoupled. Jenkins handles application builds, automated testing, and artifact pushing, while the GitOps controller running inside Google Kubernetes Engine (GKE) continuously observes and synchronizes cluster state with a version-controlled Git repository.
kubectl permissions to the GKE control plane. Jenkins only interacts with the Git repository.git-creds) to continuously pull manifests and reconcile live state against desired state without manual intervention.This pattern strictly satisfies enterprise compliance by replacing vulnerable push-based deployment credentials with in-cluster, pull-based reconciliation and dedicated non-human machine credentials.