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 enterprise operates a hybrid and multi-cloud infrastructure consisting of multiple Google Kubernetes Engine (GKE) clusters managed under a centralized fleet. You are implementing a GitOps continuous delivery workflow using Config Sync and Kustomize to continuously enforce declarative cluster configurations, network policies, and security baselines across all environments.
Your security team has established the following operational requirements:
Which configuration strategy should you implement?
This option uses Eventarc and Cloud Pub/Sub to react to events and run imperative Google Cloud CLI (gcloud) update commands against existing GKE clusters.
gcloud container clusters update forces rolling node pool restarts, causing significant workload disruption rather than maintaining a stable declarative state.You needed to trigger asynchronous event-driven compute actions in response to custom Pub/Sub message publishing.
This solution pairs Config Sync and Kustomize with GKE Dataplane V2 inter-node transparent encryption across Standard GKE clusters, applying declarative GitOps principles while adhering to the technical and architectural constraints of multi-cluster encryption.
kubectl operations with an automated reconciliation loop managed by Config Sync.This approach respects all documented platform boundaries for GKE multi-cluster networking and Dataplane V2 while leveraging native Google Cloud declarative GitOps tooling.
This option assigns broad Security Command Center administrative roles (roles/securitycentermanagement.admin) to node service agents and attempts to manage network security via Packet Mirroring and Pod CIDR-based VPC firewall rules through Config Sync.
roles/securitycentermanagement.admin to node service accounts violates IAM least-privilege principles and is irrelevant to cluster synchronization.The primary goal was configuring centralized Security Command Center Threat Detection modules across Google Cloud projects without dataplane encryption.
This option attempts to standardize the multi-cluster fleet on GKE Autopilot while enabling FQDN network policies and inter-node transparent encryption through Config Sync.
The workloads did not require inter-node transparent encryption and instead relied exclusively on Autopilot's managed baseline security with application-layer mTLS.
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