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.
Your organization uses a GitOps workflow with Config Sync to manage Kubernetes resource manifests and security policies across multiple Google Kubernetes Engine (GKE) clusters.
To prevent broken configurations and security policy regressions from reaching production clusters, you need to establish an automated gating and approval process with the following requirements:
Which solution should you implement?
enforcementAction: deny and allow developers to merge pull requests directly without automated CI checks.This option relies solely on the Policy Controller Admission Controller running in the production Kubernetes clusters configured with enforcementAction: deny to reject non-compliant resources when Config Sync attempts to apply them.
deny actions without prior CI validation can halt Config Sync reconciliations and disrupt ongoing workload management.The organization already had a complete pre-merge CI pipeline and needed a final, cluster-level admission firewall to block runtime API calls from unauthorized sources.
nomos status on clusters every hour and email failure reports to reviewers before they manually approve pull requests.This option sets up a periodic Cloud Scheduler job to inspect existing cluster state using nomos status and sends email notifications regarding synchronization errors on running clusters.
nomos status checks the current synchronization state of live clusters rather than validating proposed Git changes ahead of time.The goal was to periodically audit and alert on cluster drift or synchronization errors across running fleets rather than gating pull requests before merge.
nomos vet containerized validation, configure Git branch protection rules requiring this status check to pass, and require merge approvals from platform and security Code Owners.This solution integrates automated CI validation directly into the Git repository workflow using Cloud Build and branch protection rules. By executing the nomos vet command on every change request, the pipeline automatically verifies that all Config Sync manifests are syntactically correct and structurally valid before any human intervention occurs.
nomos vet in a container to validate the configuration syntax.nomos vet check runs within standard container environments, providing repeatable results across development and CI/CD pipelines.This approach aligns with CI/CD and GitOps best practices by establishing a strict gating pipeline where automated testing serves as a mandatory gate for manual approval. It protects cluster stability while enforcing peer review requirements across platform and security teams.
This option places validation logic entirely within client-side Git pre-commit hooks on local developer machines and grants platform team members the ability to bypass protected branch policies.
git commit --no-verify) or omitted entirely on new machines.The objective was merely to provide optional local developer tooling to catch basic formatting errors before pushing commits to a remote repository.
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