Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your company is deploying a new web application on a Compute Engine virtual machine (VM). The application requires access to read image files stored in a single, specific Cloud Storage bucket, but should not have access to any other project resources.
Following Google-recommended security practices and the principle of least privilege, what should you do?
Service agents are internal service accounts created and managed entirely by Google Cloud on behalf of specific services. Identifiable by standard email patterns such as service-PROJECT_NUMBER@compute-system.iam.gserviceaccount.com, they allow Google Cloud services to run background processes and interact with resources in your project.
roles/compute.serviceAgent) granted automatically.Service agents are used exclusively by Google Cloud platform services to carry out their managed background operations. You do not assign or attach them to compute resources; they function automatically once the associated APIs are activated.
A user-managed service account is an identity created and maintained by administrators within an Identity and Access Management (IAM) project. Unlike default service accounts or human user identities, user-managed service accounts can be tailored specifically for single-purpose workloads, applications, and compute resources such as Compute Engine instances.
roles/storage.objectViewer) role directly on the designated bucket resource rather than project-wide. This ensures the VM can only read objects from that bucket and cannot touch any other resources.Creating a custom, user-managed service account with targeted IAM permissions is the recommended architectural standard in Google Cloud. Default service accounts carry broad default permissions that present severe security risks, while service agents are internal Google-managed identities that cannot be attached to VMs. Creating a dedicated account ensures full control over access and adheres strictly to least privilege.
A default service account is a user-managed service account created automatically by Google Cloud when specific APIs—such as the Compute Engine API—are first enabled in a project. For Compute Engine, this account follows the format PROJECT_NUMBER-compute@developer.gserviceaccount.com.
roles/editor) at the project level upon creation. The Editor role allows broad read and write access to almost all cloud resources across the entire project, far exceeding the read-only bucket requirement.roles/editor by default, which allows modifying infrastructure, disks, databases, and storage across the project.Relying on the default service account is generally only acceptable during initial sandbox experimentation or rapid proof-of-concept prototyping where simplicity outweighs security controls. In production and standard enterprise architectures, Google explicitly recommends disabling automatic role grants and using dedicated accounts instead.
Access scopes are a legacy mechanism used by Compute Engine instances to define default OAuth 2.0 scopes for calls made from the instance to Google Cloud APIs. They act as a coarse network-level ceiling on the permissions available to the attached service account when using OAuth.
https://www.googleapis.com/auth/devstorage.read_only). They cannot distinguish between individual Cloud Storage buckets, meaning the VM could read every bucket in the project rather than just the single designated bucket.roles/editor) it possesses. If the account is used elsewhere or impersonated, those broad project-level permissions remain accessible.cloud-platform) and delegating all access decisions exclusively to granular IAM roles on a user-managed service account.Configuring restrictive access scopes was common in legacy Compute Engine deployments before IAM provided fine-grained role-based access control. Today, setting restricted access scopes is considered an outdated pattern superseded by dedicated user-managed service accounts and IAM policies.
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