PROFESSIONAL-CLOUD-DEVELOPER · Question #359
You are responsible for improving the security of your Cloud Run services to protect these services against supply chain threats. You need to ensure that there are adequate security controls such as…
The correct answer is B. Use Cloud Build to build container images. Configure a Binary Authorization policy on the Cloud. Cloud Build natively supports SLSA Level 3 build provenance-it runs builds in a hermetic, isolated environment and generates a cryptographically signed, non-falsifiable build provenance attestation stored in Artifact Registry. Binary Authorization can then be configured on…
Question
You are responsible for improving the security of your Cloud Run services to protect these services against supply chain threats. You need to ensure that there are adequate security controls such as SLSA Level 3 builds for container images and non-falsifiable provenance for container images by using Google Cloud tools. What should you do?
Options
- AAsk developers to build container images locally and ensure strict version controls by using
- BUse Cloud Build to build container images. Configure a Binary Authorization policy on the Cloud
- CUse Cloud Deploy to generate authenticated and non-falsifiable build provenance for container
- DUse Cloud Build to build container images. Use Cloud Scheduler to automate delivery of your
How the community answered
(47 responses)- A15% (7)
- B72% (34)
- C9% (4)
- D4% (2)
Explanation
Cloud Build natively supports SLSA Level 3 build provenance-it runs builds in a hermetic, isolated environment and generates a cryptographically signed, non-falsifiable build provenance attestation stored in Artifact Registry. Binary Authorization can then be configured on Cloud Run to enforce a policy that only allows deployment of images with valid, verified provenance from Cloud Build. Together, these tools form a supply chain security posture that satisfies the requirement. Option A (local builds) cannot guarantee SLSA Level 3 compliance since the build environment is not controlled or auditable by Google Cloud. Option C (Cloud Deploy) handles deployment orchestration, not build provenance generation. Option D adds Cloud Scheduler, which automates delivery timing but has no role in generating or verifying build provenance.
Topics
Community Discussion
No community discussion yet for this question.