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 is designing an automated machine learning workflow using Vertex AI Pipelines to process sensitive analytical datasets stored in Cloud Storage and BigQuery.
The security and governance team establishes the following operational constraints:
Which architectural approach should you implement to satisfy these security and governance requirements?
roles/editor role, and configure VPC egress firewall rules to restrict outbound traffic to specific IP ranges.This configuration uses the Compute Engine default service account (PROJECT_NUMBER-compute@developer.gserviceaccount.com) with the broad Editor (roles/editor) primitive role to run Vertex AI Pipelines and relies on network-level VPC firewall egress rules for traffic restriction.
The goal was rapid, non-production prototyping where security boundary controls and least-privilege access were not required.
roles/iam.serviceAccountUser role specifically on this service account; and enclose the project and storage resources inside a VPC Service Controls perimeter.This architecture establishes a robust, zero-trust operational security posture for Vertex AI Pipelines by combining granular Identity and Access Management (IAM) controls with VPC Service Controls (VPC SC) perimeters.
roles/aiplatform.user, roles/storage.objectUser, and BigQuery dataset roles) rather than broad project-wide privileges.roles/iam.serviceAccountUser) role directly on the specific service account resource allows authorized engineers to run pipelines using that identity without granting them broad access to other service accounts in the project.This approach directly aligns with Google Cloud security best practices by combining context-aware boundary defense (VPC Service Controls) with resource-level identity delegation (roles/iam.serviceAccountUser), ensuring full isolation and minimal blast radius.
This configuration relies on the internal Google APIs Service Agent (PROJECT_ID@cloudservices.gserviceaccount.com), applies object-level Access Control Lists (ACLs) on Cloud Storage buckets, and distributes long-lived downloadable JSON service account keys to individual data engineers.
You were configuring legacy systems outside of Google Cloud requiring static API keys without access to native IAM role bindings or federated identity.
roles/resourcemanager.projectIamAdmin role, configure Private Google Access on the subnet, and assign the roles/iam.serviceAccountAdmin role to engineers.This option creates a service account possessing the Project IAM Admin (roles/resourcemanager.projectIamAdmin) role, enables Private Google Access for internal subnet communication with Google APIs, and gives engineers administrative power over service accounts via Service Account Admin (roles/iam.serviceAccountAdmin).
roles/resourcemanager.projectIamAdmin to the pipeline runtime identity allows the pipeline itself to alter IAM policies on the project, creating massive privilege escalation vulnerabilities.roles/iam.serviceAccountAdmin allows engineers to create, modify, and delete service accounts, but does not specifically configure the right permission (iam.serviceAccounts.actAs contained within roles/iam.serviceAccountUser) required to execute workloads on behalf of that service account.The objective was to build an automated infrastructure provisioning pipeline responsible for managing IAM bindings across projects rather than running ML pipelines.
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