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.
A financial enterprise is deploying an automated transaction processing application on Compute Engine virtual machines (VMs). The application needs to read input batch files from a raw ingestion Cloud Storage bucket and write processed summary outputs to a designated archive bucket.
The security architecture must satisfy the following compliance requirements:
grp-fin-admins@example.com) permission to administer bucket configurations and policies without granting full administrative rights across the entire project.Which combination of actions should the cloud architect recommend?
This option relies on fine-grained access control using object-level Access Control Lists (ACLs), keeps the default Compute Engine service account with basic Editor privileges, and grants project Owner permissions to administrators.
roles/editor) role grants broad read/write access across almost all Google Cloud services in the project rather than scoping permissions to specific storage buckets.roles/owner) role gives full control over billing, IAM policies, and all cloud services, far exceeding the requirement to manage storage configurations.This design would only be applicable in a legacy development prototype where individual file ownership must be transferred among heterogeneous external accounts using legacy S3-compatible APIs and fine-grained ACL mechanisms.
Uniform Bucket-level Access disables object-level Access Control Lists (ACLs) across a Cloud Storage bucket, ensuring that access to all objects in the bucket is managed uniformly and exclusively through Google Cloud Identity and Access Management (IAM). Coupling this with user-managed service accounts and predefined IAM roles establishes least-privilege security tailored to application workloads.

roles/storage.objectViewer on the raw data bucket and roles/storage.objectCreator or roles/storage.objectUser on the archive bucket) ensures the VM can only access required resources.roles/storage.admin) to grp-fin-admins@example.com at the bucket or storage level gives them full administrative control over storage resources without exposing project-wide management rights.roles/editor or roles/owner.This solution adheres directly to Google Cloud security best practices by combining IAM-only bucket security with dedicated service accounts and role-based access control, eliminating the maintenance complexity of ACLs while strictly enforcing least privilege.
This option retains fine-grained object ACLs to specify read and write permissions on individual files in Cloud Storage, while assigning the project-wide basic Editor role to the finance administrator group.
roles/editor) allows administrators to modify all computing, networking, and security resources in the project rather than scoping access to storage administration.The application required per-object access management where distinct end-users own and individually grant access to individual files within a single shared bucket.
This option enables Uniform Bucket-level Access but authenticates the VM by downloading and embedding a long-lived service account JSON key into a startup script, while assigning the basic Viewer role (roles/viewer) at the project level.
grp-fin-admins@example.com).Exported service account keys are generally only acceptable for workloads hosted outside of Google Cloud on-premises or in other clouds where Workload Identity Federation cannot be configured.
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