Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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?
This pattern configures an inverted deployment pipeline where an in-cluster controller attempts to reach out across the network to trigger jobs on a Jenkins CI server, bypassing standard Git repository reconciliation and pushing binaries over unmanaged SSH sessions to individual worker nodes.
You were provisioning bare-metal virtual machines using legacy configuration management tools (such as Ansible or Chef) without container orchestrators.
This approach represents a traditional push-based CI/CD deployment pipeline where the Jenkins CI server assumes direct administrative control over the target Google Kubernetes Engine (GKE) cluster control plane via kubectl apply commands.
kubectl apply only evaluates state during active job execution; it cannot detect subsequent configuration drift or provide automated cluster self-healing.The organization had a legacy workflow with no GitOps controller installed and permitted direct push-based deployments executed under ephemeral, workload-identity-federated service accounts.
This configuration attempts to store heavy compiled container image layers directly within a Git source control repository while setting the in-cluster GitOps controller to access the repository without authentication.
The workload was an open-source public demonstration where configuration manifests were entirely public and no private container assets or credentials were involved.
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.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated