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.
An enterprise organization is designing an automated CI/CD pipeline in Google Cloud to build and manage container images across staging and production environments. The cloud architecture and security teams have established the following requirements:
Which solution should the cloud architect implement?
This architecture leverages Google Cloud Build triggers configured with dedicated user-specified service accounts, parameterized build substitutions, and Google Cloud Artifact Registry integrated with Artifact Analysis for end-to-end supply chain security.
roles/artifactregistry.writer and roles/logging.logWriter), you prevent builds from executing with broad default project-level permissions.$PROJECT_ID) and user-defined substitutions (such as ${_LOCATION} and ${_REPOSITORY}) in a single cloudbuild.yaml allows the exact same build template to deploy across staging and production environments dynamically.
Native integration between Cloud Build, Artifact Registry, and Artifact Analysis provides fully managed, serverless, and hardened CI/CD execution without needing third-party plugins or managing underlying build runner infrastructure.
This approach relies on downloading static service account JSON keys, storing them inside version control repositories, building container images locally or on unmanaged VM hosts, and using Cloud Storage buckets as an image repository.
You were archiving raw uncompiled code archives for disaster recovery backup rather than establishing a modern container CI/CD pipeline.
This option proposes using Cloud Deploy as the build engine, storing build outputs in an Artifact Registry remote repository configured with upstream caching, and disabling vulnerability scanning.
The primary goal was to cache open-source public images from Docker Hub in a local region to improve pull latency and availability.
This option uses the legacy default Cloud Build service account with broad privileges across the project, hardcoded configuration files per environment, and manual checks inside Cloud Workstations.
roles/editor) that are unnecessarily broad, violating least-privilege principles.cloudbuild.yaml files for each separate environment introduces configuration duplication and maintenance overhead rather than reusing parameterized templates via substitutions.The organization had a requirement to conduct ad-hoc, interactive debugging within cloud-hosted IDEs rather than an automated, unattended CI/CD pipeline.
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