Option 1 is the correct answer. As a way to notify team members when something goes wrong on your Kubernetes cluster, you can use the notifications feature of the Operations Suite to set up SMS, Slack, and email. When you enable integration of Cloud Operations for GKE with Cloud Logging and Cloud Monitoring in your cluster, logs are stored in a dedicated persistent data store. This allows you to take advantage of Cloud Monitoring's operational suite to set up notifications via SMS, Slack, and email.

Option 2 is incorrect. Stackdriver alerts are an older feature of the Operations Suite and now run in the Operations Suite.

Option 3 is incorrect. The Operation Suite Agent is a function that is installed in a virtual machine and used to acquire log information.

Option 4 is incorrect. There is no function called operation alert. You can set SMS, Slack, and Email in the monitoring settings in the Operations Suite.

【reference】

https://cloud.google.com/stackdriver/docs/solutions/gke/managing-logs

https://cloud.google.com/stackdriver/docs/solutions/slo-monitoring/ui/create-alert

Option 3 is the correct answer. The correct command to display information about roles is gcloud iam roles describe [ROLE-ID]. describe is typically used to display more detailed information about a resource.

Option 2 is incorrect. gcloud iam roles list [ROLE-ID] uses list instead of describe. list is typically used to display a brief description of multiple resources.

Options 1 and 4 are incorrect. There are no commands that use View or show.

【reference】

https: //cloud.google.com/sdk/gcloud/reference/iam/roles/describe

Option 3 is the correct answer. You can use a region cluster in Standard mode to replicate each node pool to three zones in the control plane region.

When you create a Kubernetes cluster, choose one of the following operational modes:

Autopilot: Provides a fully provisioned managed cluster configuration. Cluster configuration options are automatically created for clusters created in Autopilot mode. Autopilot clusters are preconfigured with an optimized cluster configuration for production workloads.

Standard: Provides a high degree of configuration flexibility for the underlying infrastructure of the cluster. For clusters created using Standard mode, users determine the configuration required for production workloads. In Autopilot mode, a highly available configuration using regions is automatically applied, but in Standard mode, you can select a configuration using regions or zones from the following:

■ Single zone cluster A single zone cluster contains one control plane operating in one zone. This control plane manages workloads on nodes running in the same zone.

■ Multi-zone cluster A multi-zone cluster contains one replica of the control plane operating in one zone and multiple nodes operating in multiple zones. The workload continues to operate during cluster upgrades and when the zone in which the control plane operates is down. However, you cannot configure the cluster or the nodes and workloads within it until the control plane is available. Multi-zone clusters provide a consistent workload while balancing availability and cost.

■ Region cluster A region cluster contains multiple replicas operating in multiple zones within a particular region. Nodes in a region cluster can run in multiple zones or a single zone, depending on the location of the configured nodes. By default, GKE replicates each node pool into three zones in the control plane region. When you create a cluster or add a new node pool, you can change the default configuration by specifying the zone in which the nodes of the cluster run. All zones must be in the same region as the control plane.

Options 1 and 4 are incorrect. In Autopilot mode, highly available regional configurations are automatically applied. Therefore, you cannot select the cluster configuration.

Option 2 is incorrect. A multi-zone cluster contains one replica of the control plane operating in one zone and multiple nodes operating in multiple zones, but the redundancy of replicating the nodes into three zones is guaranteed.

【reference】

https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-autoscaler

Option 2 is the correct answer. Name information such as containers in the Cloud Run configuration is stored in the K_Configuration environment variable. When Cloud Run starts the container, K_Configuration, K_Revision, K_Service, and Port are created as environment variables. In K_Configuration, specify the configuration in which the container was created. If you use a Docker container, use the CMD command in your Dockerfile configuration to specify the command to run at startup.

Option 1 is incorrect. Contains the name of the Cloud Run service that is running.

Option 3 is incorrect. Contains the name of the Cloud Run revision that is running.

Option 4 is incorrect. There is no configuration file called CloudRun metadata.

【reference】

https: //cloud.google.com/run/docs/reference/container-contract

Option 2 is the correct answer. The Monitoring agent collects system and application metrics from virtual machine instances and sends the collected information to Cloud Monitoring. By default, the Monitoring agent collects disk, CPU, network, and process metrics. To monitor third-party applications. You need to configure the Monitoring agent for the server to get the agent metrics.

When you configure the Monitoring agent, the load_5m metric allows you to retrieve data about the CPU load from your instance every 5 minutes.

Option 3 is the correct answer. You can export your billing data to a Cloud Storage bucket in CSV or JSON format. You can then use these files to see your billing details. You can also export your billing data to BigQuery for detailed analysis and visualization of your billing.

Options 1 and 2 are incorrect. DataStore cannot be specified as the destination for billing data exports.

Option 4 is incorrect. DataStore cannot be specified as the destination for billing data exports.

【reference】

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

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

Option 4 is the correct answer. The only setting required to enable automatic backup is the backup start time. Follow the steps below to set up automatic backup in Google Cloud Console:

1. Go to Cloud SQL Instances

2. Click the instance name to open the instance overview page.

3. Select Backup from the SQL navigation menu.

4. Click Edit next to Settings.

5. Select a time frame for automatically backing up your data.

6. Click Save.

Option 1 is incorrect. CloudSQL automatically creates a snapshot as a backup type. It does not need to be specified by the user.

Option 2 is incorrect. In CloudSQL, the backup destination is automatically set on the Google Cloud side as a managed service. Therefore, it does not need to be specified by the user.

Option 3 is incorrect. In CloudSQL, there are no settings such as backup life cycle rules.

【reference】

https://cloud.google.com/sql/docs/mysql/backup-recovery/backing-up#disabling_automated_backups

Option 4 is the correct answer. You can delete the specified instance template by running the command `gcloud compute instance-templates delete [instance template name]`.

Options 1, 2 and 3 are not valid commands.

【reference】

https://cloud.google.com/sdk/gcloud/reference/compute/instance-templates/delete

Option 3 is the correct answer. Persistent disk snapshots only save increments from previous snapshots. Therefore, if you add another 5GB of data to the persistent disk and then take the snapshot again, only the additional 5GB will be taken as a snapshot.

The Compute Engine uses delta snapshots, so each snapshot contains only the data that has changed since the last snapshot. Deleting a snapshot does not delete all the data on that snapshot, because later snapshots may require the information stored in the previous snapshot.

【reference】

https://cloud.google.com/compute/docs/disks/create-snapshots

Option 4 is the correct answer. The managed service provides the main operation management items such as infrastructure, OS and software patch management on the Google Cloud side.

Managed services have limited user access, but can leave a lot of administrative responsibility and work to the vendor.