Your company has an application running as a Deployment in a Google Kubernetes Engine (GKE) cluster. You have separate clusters for development, staging, and production. You have discovered that the…

Question

Options

• AConfigure a Kubernetes lifecycle hook to prevent the container from starting if it is not approved
• BImplement a corporate policy to prevent teams from deploying Docker images to an environment
• CConfigure binary authorization policies for the development, staging, and production clusters.
• DCreate a Kubernetes admissions controller to prevent the container from starting if it is not

• A
  17% (4)
• B
  9% (2)
• C
  70% (16)
• D
  4% (1)

Explanation

https://cloud.google.com/architecture/prep-kubernetes-engine-for-prod#binary-authorization The most common Binary Authorization use cases involve attestations. An attestation certifies that a specific image has completed a previous stage, as described previously. You configure the Binary Authorization policy to verify the attestation before allowing the image to be deployed. At deploy time, instead of redoing activities that were completed in earlier stages, Binary Authorization only needs to verify the attestation. https://cloud.google.com/binary-authorization/docs/overview

No community discussion yet for this question.