
Explanation:
Option D is the correct answer because it directly addresses the requirement to generate build provenance to demonstrate software integrity against supply chain threats. SLSA (Supply Chain Levels for Software Artifacts) is a Google-endorsed framework specifically designed for securing software supply chains, and SLSA Level 3 provides strong provenance-based assurances. Using Cloud Build to generate SLSA Level 3 provenance and viewing it in the Security Insights panel aligns with Google Cloud best practices and tools. The community discussion strongly supports D with 100% consensus and upvoted comments referencing official Google documentation. Other options are less suitable: A involves external audits which may not provide automated, verifiable provenance; B uses PGP signing which lacks the comprehensive framework of SLSA; and C focuses on open-source review rather than generating formal build provenance.
Ultimate access to all questions.
No comments yet.
Your organization develops software involved in many open-source projects and is concerned about software supply chain threats. You need to generate build provenance to demonstrate that the software has not been tampered with.
What should you do?
A
B
C
D