Professional-Cloud-DevOps-Engineer Exam Dumps - Google Cloud Certified - Professional Cloud DevOps Engineer Exam

Google Workload Identity is the recommended method to allow GKE workloads to securely access Google Cloud APIs using short-lived credentials without managing keys.

"Workload Identity is the recommended way to access Google Cloud services from GKE. It replaces the older method of using service account keys."

— Workload Identity Overview

"You can configure a Kubernetes service account to impersonate a Google Cloud service account by granting the roles/iam.workloadIdentityUser role and using the iam.gke.io/gcp-service-account annotation."

— Configure Workload Identity

This satisfies the customer’s requirement for PoLP and avoids long-lived keys.

https://cloud.google.com/blog/products/gcp/available-or-not-that-is-the-question-cre-life-lessons

The best option for preparing to handle the predicted growth is to verify the maximum node pool size, enable a Horizontal Pod Autoscaler, and then perform a load test to verify your expected resource needs. The maximum node pool size is a parameter that specifies the maximum number of nodes that can be added to a node pool by the cluster autoscaler. You should verify that the maximum node pool size is sufficient to accommodate your expected growth rate and avoid hitting any quota limits. The Horizontal Pod Autoscaler is a feature that automatically adjusts the number of Pods in a deployment or replica set based on observed CPU utilization or custom metrics. You should enable a Horizontal Pod Autoscaler for your application to ensure that it runs enough Pods to handle the load. A load test is a test that simulates high user traffic and measures the performance and reliability of your application. You should perform a load test to verify your expected resource needs and identify any bottlenecks or issues.

Comprehensive and Detailed Explanation:

Cloud Run scales down to zero when idle. If CPU is allocated only during request processing, background telemetry tasks (like OpenTelemetry traces) may not complete before the container shuts down.

Solution: Configure CPU to be always-allocated → This ensures that background tasks (like trace exports) continue even when the service is idle.

📌Why not other options?

A (Increasing CPU to 4 cores)❌→ More CPU won’t help if traces are being cut off due to shutdown.

B (Using an HTTP health check)❌→ Doesn’t affect OpenTelemetry traces.

C (CPU only during request processing)❌→ This causes the problem because traces need CPU after request completion to be exported.

📌Official Reference:

Cloud Run Tracing with OpenTelemetry

Cloud Run Always-Allocated CPU

The correct answer is B. Apply the constraints/iam.disableServiceAccountKeyCreation constraint to the organization.

According to the Google Cloud documentation, the constraints/iam.disableServiceAccountKeyCreation constraint is an organization policy constraint that prevents the creation of user-managed service account keys1.User-managed service account keys are long-lived credentials that can be downloaded as JSON or P12 files and used to authenticate as a service account2.These keys pose severe security risks if they are leaked, stolen, or misused by unauthorized entities34.By applying this constraint to the organization, you can completely eliminate the risks associated with the use of JSON service account keys and enforce a more secure alternative for authentication, such as Workload Identity or short-lived access tokens12. This also minimizes operational overhead by avoiding the need to manage, rotate, or revoke user-managed service account keys.

The other options are incorrect because they do not completely eliminate the risks associated with the use of JSON service account keys. Option A is incorrect because it only restricts the IAM permissions to create, list, get, delete, or sign service account keys, but it does not prevent existing keys from being used or leaked. Option C is incorrect because it only disables the upload of user-managed service account keys, but it does not prevent the creation or download of such keys. Option D is incorrect because it only limits the IAM role that can create and manage service account keys, but it does not prevent the keys from being distributed or exposed to unauthorized entities.

The best option for making the third-party application work while following Google-recommended security practices is to add a rule to set the iam.disableServiceAccountKeyCreation policy to off in your project and create a key. The iam.disableServiceAccountKeyCreation policy is an organization policy that controls whether service account keys can be created in a project or organization. By default, this policy is set to on, which means that service account keys cannot be created. However, you can override this policy at a lower level, such as a project, by adding a rule to set it to off. This way, you can create a service account key for your project without affecting other projects or organizations. You should also follow the best practices for managing service account keys, such as rotating them regularly, storing them securely, and deleting them when they are no longer needed.