Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise is establishing an artifact management architecture across Google Cloud CI/CD pipelines for Maven and npm workloads. The architecture must satisfy several key requirements:
pom.xml / settings.xml and .npmrc) must query a single endpoint per format rather than managing multiple repository endpoints.Which Artifact Registry repository architecture should you establish?
This approach reverses the intended roles of repository modes by creating remote repositories for internal code and manually maintaining copies of public dependencies inside standard repositories via scheduled Cloud Build cron jobs.
npm publish or mvn deploy commands from internal build pipelines.Artifact Registry lacked pull-through caching capabilities and required manual pipeline automation to vendor and sync external dependencies into private storage.
This option proposes using gcr.io repositories in Artifact Registry to manage packages and containers, combined with Binary Authorization policies to inspect package hashes during build compilation.
gcr.io repositories in Artifact Registry are strictly for backwards-compatible container image management transitioning from Container Registry and do not support language package formats like Maven or npm.gcr.io mode does not provide remote pull-through caching or virtual aggregation with priority ordering for language packages.gcr.io domain support is restricted to container images and multi-regional endpoints.The primary goal were migrating legacy gcr.io container workloads to Artifact Registry without modifying container URLs, while enforcing container deployment signatures before deployment to GKE.
This approach involves creating standard repositories for internal packages and having developers configure multiple repository URLs in client configuration files (such as .npmrc or Maven settings.xml), listing both the private Artifact Registry repository and external public registries (npmjs.com or Maven Central).
There were no security requirements regarding dependency confusion, no need to cache third-party dependencies locally, and client tools had native, deterministic priority resolution configured locally.
This architecture establishes a multi-tiered repository design using three native Artifact Registry repository modes:
npm, mvn, gradle) to the single virtual repository endpoint, eliminating the need to configure multiple mirrors or dual registry paths in local client configurations.Using native virtual and remote repository modes in Artifact Registry removes the operational burden of managing external repository managers or writing custom synchronization scripts. It directly satisfies dependency resolution priority, caching, and single-endpoint access natively within Google Cloud.
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