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.
An enterprise DevOps team manages a Cloud Build CI/CD pipeline that builds container images, executes vulnerability scans using the On-Demand Scanning API, and publishes validated artifacts to Artifact Registry.
To meet compliance mandates, all cloud development environments and build pipelines are enclosed within a VPC Service Controls (VPC-SC) service perimeter. During pipeline execution, the build step running gcloud artifacts docker images scan fails with a VPC Service Controls security perimeter violation, halting the CI/CD pipeline.
Which combination of actions should the DevOps engineer implement to resolve the perimeter violation and allow the vulnerability scanning gate to succeed?
This option modifies identity permissions by granting the Artifact Analysis Occurrences Viewer role (roles/containeranalysis.occurrences.viewer) to the build runner and attempts to route outbound API calls through a Cloud NAT gateway.
occurrences.viewer role only grants read permissions, which is insufficient for running scans that require creating new vulnerability occurrences.The failure were caused by an HTTP 403 Forbidden IAM authorization error rather than a VPC Service Controls perimeter violation.
This option attempts to resolve the perimeter failure by adding containerscanning.googleapis.com to the list of restricted services and configuring external public DNS forwarding for Artifact Registry domains.
containerscanning.googleapis.com) is a surfaceless API that operates behind Artifact Analysis. It stores metadata and scan occurrences inside containeranalysis.googleapis.com. Because it lacks independent network endpoints, adding containerscanning.googleapis.com to the perimeter is unnecessary and does not resolve the issue.pkg.dev traffic over public DNS routes to external public IPs violates VPC Service Controls perimeter policies, which immediately drops requests originating from inside the perimeter.restricted.googleapis.com or private.googleapis.com, requests to *.pkg.dev are rejected.containeranalysis.googleapis.com leaves the metadata storage engine outside the perimeter configuration.containerscanning.googleapis.com were a standalone network-exposed service requiring explicit perimeter declaration and public endpoints were accessible across the perimeter without private Google access.
This solution properly integrates Artifact Analysis and Artifact Registry within a VPC Service Controls (VPC-SC) security perimeter by securing the underlying APIs and establishing private network routing.
containeranalysis.googleapis.com) and Artifact Registry API (artifactregistry.googleapis.com) are added as protected services inside the VPC-SC perimeter, authorizing authenticated API requests originated within the perimeter boundaries.pkg.dev domain. Configuring DNS resolution for *.pkg.dev to point to restricted.googleapis.com (or private.googleapis.com) routes container pull, push, and scan traffic over private Google Cloud networks rather than public IP routes, preventing perimeter ingress and egress blocks.containerscanning.googleapis.com) is a surfaceless API that deposits results into Artifact Analysis, meaning it does not require standalone perimeter definition once containeranalysis.googleapis.com is protected.gcloud artifacts docker images scan) inside automated Cloud Build runners.This approach directly targets the root causes of VPC-SC violations for container tooling: missing protected API definitions and unroutable pkg.dev domain requests that otherwise attempt to exit via public internet paths.
This option disables automated vulnerability scanning on the target repository and moves the vulnerability scanning process outside the automated CI/CD pipeline.
--disable-vulnerability-scanning flag disables automatic on-push scanning on the repository. It does not remediate VPC-SC blocking errors encountered when Cloud Build invokes the On-Demand Scanning API (gcloud artifacts docker images scan).The organization intentionally chose to eliminate centralized automated CI/CD scanning and replace it with manual developer workstation reviews.
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