Correct Answer: It eliminates the need to store and manage static JSON keys for service accounts inside Kubernetes secrets
Workload Identity allows Kubernetes service accounts to impersonate GCP service accounts, providing a secure, identity-based way for pods to access Google APIs....
Correct Answer
It eliminates the need to store and manage static JSON keys for service accounts inside Kubernetes secrets
Why This Answer Is Correct
Workload Identity allows Kubernetes service accounts to impersonate GCP service accounts, providing a secure, identity-based way for pods to access Google APIs.
This question evaluates your knowledge of Google Kubernetes Engine (GKE) — a core concept tested in Professional Cloud Architect. Understanding Google Kubernetes Engine (GKE) is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
Your company is running a stateful application on GKE. You need to ensure that when a pod is rescheduled to a different node, it can still access its persistent data. What must you use?
A global enterprise needs to implement a Disaster Recovery (DR) solution for their multi-region GKE deployment. They want to ensure that in the event of a regional failure, user traffic is automatically rerouted to the secondary region with minimal latency. What is the key component?
To prevent unauthorized lateral movement in a GKE cluster if a pod is compromised, what security feature should you implement?
Scenario: To secure a GKE cluster for a HIPAA-compliant workload, an architect wants to ensure that all administrative actions (e.g., creating a deployment) are logged. Which tool is essential?
How can you securely store and retrieve secrets in GKE without hardcoding them in your application code or Dockerfile?