1.3 Designing a CI/CD Architecture Stack in Google Cloud, Hybrid, and Multi-Cloud Environments PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice Questions (Page 2)

Questions 6–10

1. 6application · medium

   Your team develops both container images and Python packages. You want to store both in Artifact Registry, with separate repositories for each type. You also want to ensure that only authenticated members of your team can push, but anyone in your organization can pull. What should you do?

   • ACreate a Docker repository and a Python repository in Artifact Registry, and configure IAM roles so that the team has Artifact Registry Writer and the organization has Artifact Registry Reader.
   • BCreate two repositories but give everyone in the organization Writer access.
   • CCreate a single repository and store both Docker images and Python packages in it.
   • DUse Container Registry for Docker images and Artifact Registry for Python packages.
   Reveal Solution Discussion Select an answer first
2. 7application · medium

   Your organization uses Argo CD for GitOps-based deployments to GKE. You want to integrate this with Google Cloud's CI/CD services while keeping Argo CD as the deployment tool. What is the best approach?

   • AUse Cloud Build for CI and have it push the built image to Artifact Registry, then update the Kubernetes manifests in the Git repository that Argo CD monitors.
   • BUse Cloud Build to deploy directly to GKE, bypassing Argo CD.
   • CUse Jenkins to build and deploy, and keep Argo CD only for monitoring.
   • DReplace Argo CD with Cloud Deploy for all deployments.
   Reveal Solution Discussion Select an answer first
4. 8application · medium

   You are designing a CI pipeline in Cloud Build that builds a container image and pushes it to Artifact Registry. You need to ensure that secrets such as API keys are not exposed in the build logs or in the source code. What should you do?

   • AStore secrets in the build config file as plain text substitutions.
   • BStore secrets in Secret Manager and access them in Cloud Build steps using the 'secretEnv' field.
   • CUse a Docker build argument to pass the secret directly in the build step.
   • DEncrypt secrets with KMS and include the encrypted value in the build config.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   What is the primary role of Skaffold in a Cloud Deploy pipeline?

   • ATo manage secrets and credentials for CI/CD
   • BTo create and manage GKE clusters
   • CTo automate the build, push, and deploy of applications to Kubernetes
   • DTo provide a UI for monitoring deployments
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   You have a Kubernetes application with a base manifest that is identical across dev, staging, and prod. Each environment requires different replica counts and resource limits. You are using Cloud Deploy for delivery. How should you manage the environment-specific differences?

   • AUse a single manifest and modify it in the cluster after deployment.
   • BCreate a Kustomize overlay for each environment and configure Skaffold to use the appropriate overlay for each target.
   • CMaintain three separate copies of the manifest, one for each environment.
   • DUse environment variables in the manifest and substitute them at deploy time.
   Reveal Solution Discussion Select an answer first