Option 1 is the correct answer. Google Cloud recommends that domain validation be done through a domain host. At that time, domain ownership is verified by adding the validation record received from Cloud Identity to the DNS settings. Cloud Identity provides validation records to add to your domain's DNS settings. When Cloud Identity verifies the existence of the record, it verifies the ownership of the domain. Confirmation records do not affect websites or emails.

Option 2 is incorrect. There is no need to change firewall rule settings for domain validation.

Option 3 is incorrect. For domain validation, you do not need to change the load balancer policy settings.

Option 4 is incorrect. The virtual network name resolution option is a feature that enables name resolution within a virtual network to enable domain discovery. This has nothing to do with domain validation.

【reference】https://cloud.google.com/identity/docs/verify-domain

Option 2 is the correct answer. In order to use the Operations Suite to collect metric data from a Compute Engine instance and Cloud Logging to collect logs from a Compute Engine instance, the Operations Suite Agent must be installed on all target VMs.

The Google Cloud Operations suite provides the following agents for collecting metrics on Linux and Windows VM instances:

Ops agent: The primary and recommended agent for collecting telemetry from Compute Engine instances. This agent integrates logging and metrics into a single agent. It provides a YAML-based configuration for collecting logs and metrics, as well as high-throughput logging capabilities.

Former Monitoring Agent: Collect system and application metrics from virtual machine instances and send the collected information to Cloud Monitoring. By default, the old Monitoring agent collected disc, CPU, network, and process metrics. You can configure the agent to monitor third-party applications to get a complete list of agent metrics.

Option 1 is incorrect. You don't need to create a BigQuery dataset for logging or monitoring with the Operations Suite.

Option 3 is incorrect. You don't need to create a Cloud Storage bucket for logging or monitoring with the Operations Suite.

Option 4 is incorrect. You do not need to create Compute Engine storage space for logging and monitoring with the Operations Suite.

【reference】https://cloud.google.com/products/operations

Option 3 is the correct answer. For efficient management of VM scaling configurations, create a Google Kubernetes Engine cluster and enable horizontal pod autoscaling to be based on the CPU and memory usage of the target pod. You can increase or decrease the number of pods.

Kubernetes is an orchestration tool that automatically manages and scales clusters of one or more containers. All Kubernetes objects, which are containerized applications, run on the cluster. You can enable automatic scaling for your cluster, which will perform metric-based scaling. Pods are the smallest unit of application you can run on Kubernetes.

Pod can coexist multiple containers from one container. Pods always run on nodes and run on virtual machines. Kubernetes has the following automatic scaling functions.

Horizontal pod autoscaling:

You can increase or decrease the number of pods based on the CPU and memory usage of the target pods.

Vertical Pod Auto Scaling:

You can automatically increase or decrease the amount of CPU and memory allocated to the container.

Cluster autoscaling:

Scales the number of nodes in the cluster.

【reference】https://cloud.google.com/kubernetes-engine/docs/how-to/cluster-autoscaler

Option 4 is the correct answer. Kubernetes Engine collects log data written to standard output (STDOUT) and standard error (STDERR) by default. Kubernetes Engine can get the standard output / standard error logs of the container with the kubectl logs command.

Option 1 is incorrect. SYSLOG is a standard client / server protocol that forwards log messages over IP networks and is not relevant here.

Option 2 is incorrect. Kubernetes Engine does not collect input to standard input (STDIN).

Option 3 is incorrect. SYSOUT is not used in Kubernetes Engine.

【reference】

https://cloud.google.com/blog/products/management-tools/using-logging-your-apps-running-kubernetes-engine

Option 3 is the correct answer. In Google Cloud, Spanner and Cloud SQL databases are relational databases with SQL interfaces.

Spanner is a fully managed relational database with unlimited scaling, strong integrity and up to 99.999% availability. Unlimited scaling allows you to take advantage of relational semantics and SQL features. Cloud SQL is a fully managed relational database service that can utilize MySQL, PostgreSQL, and SQL Server. It is possible to build an industry standard SQL database.

Options 1 and 4 are incorrect. Cloud Bigtable is Google's fully managed NoSQL database service.

Option 2 is incorrect. Datastore is a highly scalable NoSQL database for web and mobile apps.

【reference】

https://cloud.google.com/spanner?hl=JA https://cloud.google.com/sql?hl=ja

Option 3 is the wrong command and is the correct answer. You don't have the authority bigquery.tables.read. The following three permissions are required to read data into BigQuery.

bigquery.tables.create

bigquery.tables.updateData

bigquery.jobs.create

These permissions are required when reading data into a new table or partition, or when adding or overwriting data to a table or partition.

【reference】

https://cloud.google.com/bigquery/docs/batch-loading-data

https://cloud.google.com/bigquery/docs/access-control

Option 2 is the correct answer. When you execute the command `kubectl autosclae rc [replication controller name] --min = [minimum number of pods] --max = [maximum number of pods] --cpu-percent = [CPU usage threshold]`, the CPU usage rate will increase. Performs scaling to adjust the number of pods between the specified minimum and maximum pods so that CPU utilization falls below the threshold when the specified threshold is exceeded.

You can use the kubectl command line tool to control your Kubernetes cluster. Set autoscaling with autosclae rc. Therefore, by setting max = 8, the number of bots can be increased up to 8 when scaling.

Option 1 is incorrect. Like gcloud kubectl autoscale, you don't need gcloud. Control your Kubernetes cluster with the kubectl command.

Option 3 is incorrect. There is no command called gcloud containers. Control your Kubernetes cluster with the kubectl command.

Option 4 is incorrect. Use autosclae rc instead of kubectl apply to set autoscaling.

【reference】

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#autoscale

Option 1 is the correct answer. Lifecycle rules in Cloud Storage allow you to schedule data to be migrated or deleted from other storage systems. This allows you to assign lifecycle management configurations to buckets. If the object meets the rule criteria you set, Cloud Storage automatically performs the specified operation on the object. In this scenario, the life cycle rule automates the operation of automatically moving an object to nearline storage 30 days after it is uploaded by specifying that the object should move from current storage to nearline storage after 30 days.

Option 2 is incorrect. Set lifecycle rules instead of JSON file definitions.

Option 3 is incorrect. Set lifecycle rules, not object property settings.

Option 4 is incorrect. Set life cycle rules, not object rule settings.

【reference】

https://cloud.google.com/storage/docs/lifecycle

Option 1 is the correct answer. The Google Cloud Operations Suite can monitor resources not only in Google Cloud, but also in AWS and on-premises data centers. However, IBM Cloud is not monitored. The Google Cloud Operations Suite is a basic monitoring tool that allows you to monitor and troubleshoot application performance in your Google Cloud environment. Cloud Logging automatically captures Google Cloud audit logs and platform logs. Cloud Monitoring allows you to view all Google Cloud metrics for free and integrates with various providers for monitoring other than Google Cloud.

Option 2 is incorrect. The Google Cloud Operations Suite can be applied to your on-premises environment.

Option 3 is incorrect. The Google Cloud Operations Suite can be applied to AWS.

Option 4 is incorrect. The Operations Suite is a basic feature of Google Cloud.

【reference】

https://cloud.google.com/stackdriver/docs

The option 2 bucket is incorrect because it is not a component used for organizational hierarchies or configurations. Organizations, folders, and projects are components used to manage the Google Cloud organizational hierarchy. On the other hand, buckets, directories, and subdirectories are used to organize storage.

Option 1 is incorrect. The Google Cloud project is the basis for creating, enabling, and using all Google Cloud services, including managing APIs, enabling billing, adding and removing collaborators, and managing permissions on Google Cloud resources.

Option 3 is incorrect. Folders are nodes in the Cloud Platform resource hierarchy. Within the folder, there are projects and other folders. Folders allow you to group projects on organizational nodes in your hierarchy. For example, your organization may have multiple departments, each using its own set of Google Cloud resources. Folders allow you to group these resources by department.

Option 4 is incorrect. Your organization is the root node of your Google Cloud resource hierarchy and the hierarchical supernode of your project.

【reference】

https://cloud.google.com/resource-manager/docs/creating-managing-organization