Explanation:
To deploy an application, packaged in a container image, in a new project with an HTTP endpoint that receives very few requests per day while minimizing costs, you should deploy the container on Cloud Run on GKE.
Explanation:
To grant your support team permission to monitor your Cloud Spanner environment without giving them access to table data, you can add the support team group to the roles/spanner.database user role. This role grants users the ability to read metadata, such as schema and indexes, for a specific Cloud Spanner database but does not provide access to read or modify data.
Explanation:
To implement a cost-effective approach for log file retention in a scenario where hundreds of Google Cloud projects need to store audit log files for three years, you can create an export to the sink that saves logs from Cloud Audit to BigQuery.
Explanation:
Suppose your application needs access to Cloud Storage, but your security policies prevent the servers hosting the application from having public IP addresses or access to the internet. In that case, you can follow Google-recommended practices to provide the application access to Cloud Storage by migrating your servers to Compute Engine and creating an internal load balancer (ILB) with storage.googleapis.com as a backend.
Explanation:
To run a single caching HTTP reverse proxy on GCP for a latency-sensitive website with a 30-GB in-memory cache and an additional 2 GB of memory for the rest of the processes while minimizing cost, you should run it on a Compute Engine instance with a custom machine type.