You are setting up a CI/CD pipeline to deploy containerized applications to your production clusters on Google Kubernetes Engine (GKE). You need to prevent containers with known vulnerabilities from being deployed. You have the following requirements for your solution:
Must be cloud-native
Must be cost-efficient
Minimize operational overhead
How should you accomplish this? (Choose two.)
Correct Answer: A,E
A). Create a Cloud Build pipeline that will monitor changes to your container templates in a Cloud Source Repositories repository. Add a step to analyze Container Analysis results before allowing the build to continue:
Use Cloud Build to automate your CI/CD pipeline.
Integrate Container Analysis to scan container images for vulnerabilities during the build process.
If vulnerabilities are found, configure the build to fail, preventing deployment of insecure containers.
E). In your CI/CD pipeline, add an attestation on your container image when no vulnerabilities have been found. Use a Binary Authorization policy to block deployments of containers with no attestation in your cluster:
Use Binary Authorization to enforce deploy-time security policies.
Configure your CI/CD pipeline to generate attestations for container images that pass vulnerability scans.
Binary Authorization will then block deployments of any containers without valid attestations, ensuring only secure images are deployed.
References:
Cloud Build Overview
Container Analysis
Binary Authorization