You are running an application on Compute Engine and collecting logs through Stackdriver. You discover that some personally identifiable information (PII) is leaking into certain log entry fields. You want to prevent these fields from being written in new log entries as quickly as possible. What should you do?

• A. Use the filter-record-transformer Fluentd filter plugin to remove the fields from the log entries in flight.
• B. Stage log entries to Cloud Storage, and then trigger a Cloud Function to remove the fields and write the entries to Stackdriver via the Stackdriver Logging API.
• C. Use the fluent-plugin-record-reformer Fluentd output plugin to remove the fields from the log entries in flight.
• D. Wait for the application developers to patch the application, and then verify that the log entries are no longer exposing PII.

Your company is creating a new cloud-native Google Cloud organization. You expect this Google Cloud organization to first be used by a small number of departments and then expand to be used by a large number of departments. Each department has a large number of applications varying in size. You need to design the VPC network architecture. Your solution must minimize the amount of management required while remaining flexible enough for development teams to quickly adapt to their evolving needs. What should you do?

• A. Create a separate VPC for each application and use Private Service Connect to connect the VPCs.
• B. Create a separate VPC for each department and connect the VPCs with Cloud VPN.
• C. Create a separate VPC for each department and use Private Service Connect to connect the VPCs.
• D. Create a separate VPC for each department and connect the VPCs with VPC Network Peering.

Some of your production services are running in Google Kubernetes Engine (GKE) in the eu-west-1 region.
Your build system runs in the us-west-1 region. You want to push the container images from your build system to a scalable registry to maximize the bandwidth for transferring the images to the cluster. What should you do?

• A. Push the images to Google Container Registry (GCR) using the eu.gcr.io hostname.
• B. Push the images to Google Container Registry (GCR) using the gcr.io hostname.
• C. Push the images to a private image registry running on a Compute Engine instance in the eu-west-1 region.
• D. Push the images to Google Container Registry (GCR) using the us.gcr.io hostname.

You manage a retail website for your company. The website consists of several microservices running in a GKE Standard node pool with node autoscaling enabled. Each microservice has resource limits and a Horizontal Pod Autoscaler configured. During a busy period, you receive alerts for one of the microservices.
When you check the Pods, half of them have the status OOMKilled, and the number of Pods is at the minimum autoscaling limit. You need to resolve the issue. What should you do?

• A. Update the node pool to use a machine type with more memory.
• B. Increase the memory resource limit of the microservice.
• C. Increase the maximum number of nodes in the node pool.
• D. Increase the maximum replica limit of the Horizontal Pod Autoscaler.

Your organization is starting to containerize with Google Cloud. You need a fully managed storage solution for container images and Helm charts. You need to identify a storage solution that has native integration into existing Google Cloud services, including Google Kubernetes Engine (GKE), Cloud Run, VPC Service Controls, and Identity and Access Management (IAM). What should you do?

• A. Use Docker to configure a Cloud Storage driver pointed at the bucket owned by your organization.
• B. Configure Container Registry as an OCI-based container registry for container images.
• C. Configure Artifact Registry as an OCI-based container registry for both Helm charts and container images.
• D. Configure an open source container registry server to run in GKE with a restrictive role-based access control (RBAC) configuration.