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.
You are deploying a reporting service as a Pod on Google Kubernetes Engine (GKE). The service needs to read data files from a specific Cloud Storage bucket.
Your deployment must meet the following security requirements:
Which authentication method should you configure?
Workload Identity Federation for GKE is the Google-recommended approach for authenticating applications running inside Google Kubernetes Engine to Google Cloud APIs. It establishes a secure mapping between a Kubernetes service account (KSA) operating within the cluster and a Google Cloud service account (GSA) in Cloud IAM. This allows the application Pod to seamlessly authenticate to external services using short-lived tokens without requiring credential files.

PROJECT_ID.svc.id.goog).serviceAccountName in their Pod manifest, requiring zero code changes when using standard Google Cloud client libraries.Workload Identity replaces risky static private keys and overly broad node-level permissions with native, automated, and secure short-lived tokens, making it the industry standard for GKE workload authentication.
This method requires creating an exportable service account private key in JSON format from Cloud IAM, encoding that file into a native Kubernetes Secret, and mounting it into the Pod's filesystem. The application container then reads the file by referencing the GOOGLE_APPLICATION_CREDENTIALS environment variable.
get or view permissions on Secrets in that Kubernetes namespace can extract the plaintext private key.The application workload were running in a legacy on-premises environment or on a third-party cloud provider that cannot establish an OpenID Connect (OIDC) trust relationship with Google Cloud IAM.
Google Cloud security best practices strongly advise against downloading service account private keys whenever native options like Workload Identity Federation are available.
This option proposes attaching an IAM service account to the GKE control plane and relying on node access scopes to regulate Cloud Storage interactions. In GKE, the control plane hosts the Kubernetes API server and control loops, while access scopes are legacy Compute Engine settings that define the upper bound of API access for an instance's default service account.
You were provisioning a legacy Compute Engine VM directly and needed to establish baseline API boundary limits for the VM's default service account.
Best practice for modern GKE clusters is to configure node pools with the cloud-platform access scope and manage all granular security boundaries using Workload Identity and Cloud IAM.
In Google Kubernetes Engine, cluster worker nodes are Compute Engine virtual machines. Each node pool runs using an attached service account (frequently the Compute Engine default service account). If workloads inside the cluster do not have individual identities configured, calls to Google Cloud APIs fall back to the identity of the host node.
The workload was a node-level daemon (such as a DaemonSet for host logging or node monitoring) where every node in the cluster uniformly required identical permissions to send telemetry to Google Cloud.
Relying on node-level service accounts is an obsolete design pattern that violates multi-tenant security practices. Modern GKE architectures should isolate workloads at the Pod level.
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