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 organization deploys containerized microservices to Google Kubernetes Engine (GKE) clusters across development, staging, and production environments using Cloud Build and Cloud Deploy. A recent security assessment identified critical vulnerabilities in their pipeline secret management:
Which end-to-end architecture should the DevOps engineer implement to enforce least privilege, eliminate build-time secret exposure, and ensure comprehensive audit logging?
This approach generates downloaded service account key JSON files, commits them into version control, and uses Cloud Build to inject secret payloads into deployment manifests as plain environment variables.
iam.disableServiceAccountKeyCreation organization policy constraint.The workloads were running on external legacy infrastructure with no connectivity to Google Cloud authentication endpoints or Workload Identity Federation.
This option uses Cloud Key Management Service (Cloud KMS) to decrypt encrypted secret files inside the CI/CD pipeline worker during the build phase and writes the plaintext credentials into the container filesystem before pushing the image to Artifact Registry.
An application strictly required static encrypted configuration files to be packaged offline without external cloud API access, though runtime decryption would still be mandatory.
This approach uses a single shared service account in Cloud Deploy to pull the newest version of secrets from Secret Manager via the latest alias and syncs them into base64-encoded native Kubernetes Secrets during the deployment release phase.
latest alias can cause runtime outages if a new secret version is published before the application code is updated to handle it.AccessSecretVersion; only Data Access audit logs capture secret payload retrieval.The target environment was a legacy cluster without Workload Identity support where Kubernetes Secrets were configured with application-layer envelope encryption and restricted RBAC.
This architecture establishes a secure-by-design secret lifecycle by combining project-level environmental segmentation, runtime secret injection, metadata-based identity federation, and end-to-end audit log enrichment across Google Cloud services.
latest alias ensures reproducible deployments and prevents breaking changes during automated secret rotation.AccessSecretVersion) captures all secret read operations, while passing the pipeline execution ID via the X-Goog-Request-Reason HTTP header enriches logs for direct correlation between CI/CD pipeline runs and infrastructure operations.Runtime injection directly from Secret Manager via Workload Identity removes secrets completely from CI/CD pipeline definitions and container registries, while organization-level Data Access logs and custom request reason headers deliver complete, unbroken auditability.
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