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 runs a multi-tier analytics application on Google Kubernetes Engine (GKE). A backend workload running in the data-processing namespace requires access to Cloud Storage and Cloud Bigtable.
The security team mandates the following requirements:
Which architectural approach should you implement to satisfy these requirements?
This approach attempts to use an external GKE Ingress controller to route outbound traffic to Google Cloud APIs, and applies Google Cloud Armor security policies to restrict inter-pod communication inside the cluster.
You needed to expose a public web service hosted on GKE to external internet clients with WAF protection and DDoS mitigation.
This option relies on generating downloadable service account private keys, storing them as base64-encoded Kubernetes Secrets, and mounting the keys into container filesystems to set the GOOGLE_APPLICATION_CREDENTIALS environment variable. It then attempts to control network traffic using VPC firewall rules applied to cluster VM instances.
This approach would only be considered in legacy or hybrid on-premises environments where native Google Cloud Workload Identity Federation is unsupported.
This approach assigns broad Google Cloud IAM permissions directly to the Compute Engine default service account or a custom VM service account attached to the GKE node pool, and attempts to use Kubernetes Role-Based Access Control (RBAC) to restrict network egress.
The goal was solely to restrict developers and operators from modifying Kubernetes API objects within specific namespaces.
Workload Identity is the recommended best practice for managing authentication and authorization for GKE workloads accessing Google Cloud services. It links a Kubernetes Service Account (KSA) directly to an IAM Google Service Account (GSA). Kubernetes Network Policies provide Layer 3 and Layer 4 packet filtering directly at the Pod and namespace boundaries.
data-processing namespace to a dedicated GSA ensures that only Pods running with that KSA obtain temporary OAuth 2.0 tokens for Cloud Storage and Cloud Bigtable.This architecture avoids node-level privilege escalation, adheres strictly to Google Cloud security best practices for GKE multi-tenancy, and protects the cluster's network perimeter without requiring intrusive application-level code modifications.
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