Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A financial enterprise is designing a secure continuous integration (CI) build pipeline on Google Cloud. The organization must comply with the Supply-chain Levels for Software Artifacts (SLSA) framework to achieve SLSA Level 3 compliance.
The build architecture must satisfy the following requirements:
Which Cloud Build architecture should you implement to satisfy these security requirements?
This approach uses a shared GKE cluster where CI pipeline tasks (such as Tekton or Kubernetes Jobs) mount persistent shared storage volumes (via Persistent Volume Claims) to cache build dependencies, compiled libraries, and intermediary container layers across multiple pipeline invocations.
The primary architectural goal was reducing build times by aggressively caching non-sensitive open-source package repositories on internal persistent disks.
Default Cloud Build shared worker pools run containerized build steps on a multi-tenant compute layer managed by Google, where internet access is open by default. Manually running Docker-in-Docker commands to output metadata involves scripting build attestations within user-controlled build tasks.
in-toto metadata files within a build step violates SLSA Level 3 provenance requirements. SLSA Level 3 mandates that build provenance must be generated by the build service itself rather than by user-controlled commands inside the build script, ensuring build provenance is non-falsifiable and tamper-proof.A team required a zero-cost, quick-start build pipeline for non-sensitive public open-source projects where public internet access is needed and basic manual metadata tagging suffices.
A self-hosted Jenkins server is a long-running, persistent virtual machine (Compute Engine) running CI controller and worker services to process build jobs sequentially or concurrently on local disk storage.
An organization had legacy build scripts tied to proprietary plugins that could only execute on a monolithic, perpetually running build server.
Cloud Build private pools are dedicated, isolated, and highly configurable worker pools hosted in a managed Google tenant project and peered directly with a customer's Virtual Private Cloud (VPC). Private pools provide isolated compute resources that run ephemeral build steps while preventing cross-build contamination and unwanted external egress.
Using Cloud Build private pools with VPC integration provides the ideal combination of managed infrastructure, strict network segmentation, ephemeral execution environments, and native provenance generation required for enterprise software supply chain security.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated