Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise machine learning team is implementing automated training pipelines on Google Cloud using managed Vertex AI Custom Training (TrainingPipeline). To protect intellectual property, prevent model weight exfiltration, and enforce the principle of least privilege, the security architect establishes the following requirements:
gs://company-model-registry/output/) without having permission to read, overwrite, or delete existing model files.Which identity and access management (IAM) configuration fulfills these requirements?
roles/artifactregistry.reader on the image repository, roles/logging.logWriter on the project, and roles/storage.objectCreator on the output Cloud Storage bucket. Grant the ML engineers roles/iam.serviceAccountUser on the service account and roles/aiplatform.user in the project.This solution establishes a least-privilege security posture for fully managed PaaS training workloads (Vertex AI TrainingPipeline) by separating the interactive user's identity from a dedicated, fine-grained user-managed service account attached to the training job.
roles/artifactregistry.reader role at the specific repository level grants the custom training worker nodes read-only access to pull required container images without allowing modifications or pushes.roles/logging.logWriter allows the training environment to output standard runtime logs and execution events directly to Cloud Logging.roles/storage.objectCreator on the destination Cloud Storage bucket allows the training script to upload newly generated model weights (via $AIP_MODEL_DIR) while strictly denying storage.objects.get, storage.objects.delete, and list permissions. This prevents the training workload or compromised code from inspecting or exfiltrating existing intellectual property.roles/iam.serviceAccountUser (iam.serviceAccounts.actAs) on the dedicated service account alongside roles/aiplatform.user enables them to launch automated pipelines while completely abstracting direct access to backend storage and repositories.Under Google Cloud's shared responsibility model for managed PaaS training, the platform handles the underlying host VMs, OS hardening, and hypervisors. The customer remains responsible for identity configuration, container security, and data access. Using a dedicated service account with roles/storage.objectCreator and roles/artifactregistry.reader perfectly enforces zero-trust boundaries without over-granting primitive or administrative roles.
roles/artifactregistry.repoAdmin and roles/storage.legacyBucketWriter on the bucket. Grant the ML engineers roles/owner on the Vertex AI dataset and model resources.This option uses the Cloud Build service account as the runtime identity for Vertex AI training and grants repository administration (roles/artifactregistry.repoAdmin) along with legacy bucket write permissions.
roles/artifactregistry.repoAdmin grants full administrative control over Artifact Registry, including deleting repositories and changing IAM policies.roles/storage.legacyBucketWriter is a legacy role that grants broader permissions than modern granular IAM roles and does not conform to enterprise fine-grained access control standards.roles/owner gives users unconstrained control, violating least-privilege boundaries.legacyBucketWriter.The requirement was to configure a CI/CD build pipeline in Cloud Build responsible for managing repository settings and pushing compiled Docker images.
roles/editor on the project and roles/storage.objectAdmin on the destination bucket. Grant the ML engineers roles/aiplatform.admin on the project.This option relies on the Compute Engine default service account and assigns broad primitive roles (roles/editor) along with administrative Cloud Storage roles (roles/storage.objectAdmin) and full AI Platform administration.
roles/editor role contains broad permissions across almost all Google Cloud services, violating least-privilege security principles and exposing project assets to privilege escalation.roles/storage.objectAdmin role allows full read, write, update, and delete access (storage.objects.get, storage.objects.delete). A malicious or compromised training script could read, tamper with, or exfiltrate existing proprietary model weights.roles/editor includes dangerous permissions such as deleting infrastructure or viewing sensitive data across services.roles/storage.objectAdmin does not restrict access to write-only operations.A developer were spinning up a temporary proof-of-concept in an isolated sandbox environment with no intellectual property protections, data access restrictions, or compliance mandates.
Google Cloud security best practices strongly recommend disabling automatic IAM grants for default service accounts and substituting dedicated user-managed service accounts.
roles/artifactregistry.writer, roles/logging.admin, and roles/storage.objectViewer on the destination bucket. Grant the ML engineers roles/storage.admin on the project.This configuration assigns repository push permissions (roles/artifactregistry.writer), administrative logging privileges (roles/logging.admin), read-only storage permissions (roles/storage.objectViewer), and broad storage administration to developers.
roles/storage.objectViewer only grants read access (storage.objects.get and storage.objects.list). The training script would fail during execution because it cannot write or export model artifacts to the destination bucket.roles/artifactregistry.writer allows the training execution service account to push and overwrite container images, which is unnecessary for a training job that only needs to pull images.roles/storage.admin allows them to directly view, download, and delete all model files across the project, violating the requirement that developers should not have direct access to model files.roles/storage.objectViewer explicitly lacks the storage.objects.create permission required for model export.roles/artifactregistry.writer is designed for CI/CD build pipelines (such as Cloud Build), not runtime training jobs.roles/logging.admin allows modifying log sinks and retention policies rather than just appending log entries.The workload were an artifact validation pipeline designed to pull data, inspect models, build new container images, and administer Cloud Logging configurations.
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