https://cloud.google.com/billing/docs/how-to/export-data-bigquery

Creating a development environment for writing code and a test environment for configurations, experiments, and load testing is the best practice to reduce the number of bugs and outages in production and to enable testers to load test new features. This way, the production environment is isolated from changes that could affect its stability and performance.

The correct answer is B, Increase the memory limit in the application deployment.
The application is experiencing a memory leak, which means that it is allocating memory that is not freed or reused. This causes the heap usage to grow constantly until it reaches the memory limit of the pod, which triggers a restart by Kubernetes. Increasing the memory limit in the application deployment can help mitigate the problem by allowing the application to run longer before reaching the limit. However, this is not a permanent solution, as the memory leak will still occur and eventually exhaust the available memory. The best solution is to identify and fix the source of the memory leak in the application code, using tools like Cloud Profiler and pprof12.
Reference:
Using Cloud Profiler with Go, Troubleshooting memory leaks. Profiling Go Programs, Heap profiles.

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.