Google Associate Cloud Engineer Exam練習テスト2024年最新のAssociate-Cloud-Engineerストレスなしで合格させちゃう！
練習Google Cloud Certified Associate-Cloud-Engineer問題集オンライン試験練習テストと詳細な解説付き！
質問 # 61
You need to set up permissions for a set of Compute Engine instances to enable them to write data into a particular Cloud Storage bucket. You want to follow Google-recommended practices. What should you do?
- A. Create a service account with an access scope. Use the access scope 'https://www.googleapis.com/auth/ cloud-platform'.
- B. Create a service account and add it to the IAM role 'storage.objectCreator' for that bucket.
- C. Create a service account with an access scope. Use the access scope 'https://www.googleapis.com/auth/ devstorage.write_only'.
- D. Create a service account and add it to the IAM role 'storage.objectAdmin' for that bucket.
正解：A
解説：
Explanation/Reference: https://towardsdatascience.com/enlightened-datalab-notebooks-35ce8ef374c0
質問 # 62
You need to track and verity modifications to a set of Google Compute Engine instances in your Google Cloud project. In particular, you want to verify OS system patching events on your virtual machines (VMs). What should you do?
- A. Review the Compute Engine activity logs Select and review the System Event logs
- B. Review the Compute Engine activity logs Select and review the Admin Event logs
- C. Install the Cloud Logging Agent In Cloud Logging review the Compute Engine syslog logs
- D. Install the Cloud Logging Agent In Cloud Logging, review the Compute Engine operation logs
正解：B
質問 # 63
Your company runs its Linux workloads on Compute Engine instances. Your company will be working with a new operations partner that does not use Google Accounts. You need to grant access to the instances to your operations partner so they can maintain the installed tooling. What should you do?
- A. Set up Cloud VPN between your Google Cloud VPC and the internal network of the operations partner.
- B. Ask the operations partner to generate SSH key pairs, and add the public keys to the VM instances.
- C. Enable Cloud IAP for the Compute Engine instances, and add the operations partner as a Cloud IAP Tunnel User.
- D. Tag all the instances with the same network tag. Create a firewall rule in the VPC to grant TCP access on port 22 for traffic from the operations partner to instances with the network tag.
正解：D
解説：
Explanation/Reference: https://cloud.google.com/vpc/docs/firewalls
質問 # 64
You created a Google Cloud Platform project with an App Engine application inside the project.
You initially configured the application to be served from the us-central region. Now you want the application to be served from the asia-northeast1 region. What should you do?
- A. Create a second App Engine application in the existing GCP project and specify asia-northeast1 as the region to serve your application.
- B. Change the region property setting in the existing App Engine application from us-central to asia- northeast1.
- C. Change the default region property setting in the existing GCP project to asia-northeast1.
- D. Create a new GCP project and create an App Engine application inside this new project.
Specify asia-northeast1 as the region to serve your application.
正解：D
解説：
Each Cloud project can contain only a single App Engine application, and once created you cannot change the location of your App Engine application.
https://cloud.google.com/appengine/docs/flexible/nodejs/managing-projects-apps-billing#create
質問 # 65
You created a cluster.YAML file containing
resources:
name: cluster
type: container.v1.cluster
properties:
zone: europe-west1-b
cluster:
description: My GCP ACE cluster
initialNodeCount: 2
You want to use Cloud Deployment Manager to create this cluster in GKE. What should you do?
- A. gcloud deployment-manager deployments create my-gcp-ace-cluster --config cluster.yaml
- B. gcloud deployment-manager deployments apply my-gcp-ace-cluster --config cluster.yaml
- C. gcloud deployment-manager deployments create my-gcp-ace-cluster --type container.v1.cluster --config cluster.yaml
- D. gcloud deployment-manager deployments apply my-gcp-ace-cluster --type container.v1.cluster --config cluster.yaml
正解：B
解説：
Explanation
gcloud deployment-manager deployments create creates deployments based on the configuration file.
(Infrastructure as code). All the configuration related to the artifacts is in the configuration file. This command correctly creates a cluster based on the provided cluster.yaml configuration file.
Ref: https://cloud.google.com/sdk/gcloud/reference/deployment-manager/deployments/create
質問 # 66
You have a single binary application that you want to run on Google Cloud Platform. You decided to automatically scale the application based on underlying infrastructure CPU usage. Your organizational policies require you to use virtual machines directly. You need to ensure that the application scaling is operationally efficient and completed as quickly as possible. What should you do?
- A. Create a Google Kubernetes Engine cluster, and use horizontal pod autoscaling to scale the application.
- B. Create an instance template, and use the template in a managed instance group with autoscaling configured.
- C. Use a set of third-party tools to build automation around scaling the application up and down, based on Stackdriver CPU usage monitoring.
- D. Create an instance template, and use the template in a managed instance group that scales up and down based on the time of day.
正解：B
解説：
Managed instance groups offer autoscaling capabilities that let you automatically add or delete instances from a managed instance group based on increases or decreases in load (CPU Utilization in this case). Autoscaling helps your apps gracefully handle increases in traffic and reduce costs when the need for resources is lower.
You define the autoscaling policy and the autoscaler performs automatic scaling based on the measured load (CPU Utilization in this case). Autoscaling works by adding more instances to your instance group when there is more load (upscaling), and deleting instances when the need for instances is lowered (downscaling). Ref:
https://cloud.google.com/compute/docs/autoscaler
質問 # 67
Your development team has asked for your help. They need a simple, reproducible way to create and terminate a new Compute Engine instance so that they can automate it as a part of their CI/CD process. What is the best option for accomplishing that?
- A. Show them how to use a Docker container. Then they can get rid of the need for the VM.
- B. Show them how to use the gcloud component of the Cloud SDK.
- C. Show them how to use the Console to create and terminate instances.
- D. Recommend that they use the REST API to develop the functionality in the language of their choosing.
正解：B
質問 # 68
You are running a data warehouse on BigQuery. A partner company is offering a recommendation engine based on the data in your data warehouse. The partner company is also running their application on Google Cloud. They manage the resources in their own project, but they need access to the BigQuery dataset in your project. You want to provide the partner company with access to the dataset. What should you do?
- A. Ask the partner to create a Service Account in their project, and have them give the Service Account access to BigQuery in their project.
- B. Create a Service Account in your own project, and grant this Service Account access to BigQuery in your project.
- C. Create a Service Account in your own project, and ask the partner to grant this Service Account access to BigQuery in their project.
- D. Ask the partner to create a Service Account in their project, and grant their Service Account access to the BigQuery dataset in your project.
正解：D
質問 # 69
You are running multiple VPC-native Google Kubernetes Engine clusters in the same subnet. The IPs available for the nodes are exhausted, and you want to ensure that the clusters can grow in nodes when needed.
What should you do?
- A. Add an alias IP range to the subnet used by the GKE clusters.
- B. Create a new VPC, and set up VPC peering with the existing VPC.
- C. Create a new subnet in the same region as the subnet being used.
- D. Expand the CIDR range of the relevant subnet for the cluster.
正解：D
解説：
Explanation
gcloud compute networks subnets expand-ip-range NAME gcloud compute networks subnets expand-ip-range
- expand the IP range of a Compute Engine subnetwork
https://cloud.google.com/sdk/gcloud/reference/compute/networks/subnets/expand-ip-range
質問 # 70
You are deploying an application to App Engine. You want the number of instances to scale based on request rate. You need at least 3 unoccupied instances at all times. Which scaling type should you use?
- A. Automatic Scaling with min_idle_instances set to 3.
- B. Manual Scaling with 3 instances.
- C. Basic Scaling with max_instances set to 3.
- D. Basic Scaling with min_instances set to 3.
正解：A
解説：
Reference:
https://cloud.google.com/appengine/docs/standard/python/how-instances-are-managed
質問 # 71
You have a Google Cloud Platform account with access to both production and development projects. You need to create an automated process to list all compute instances in development and production projects on a daily basis. What should you do?
- A. Go to Cloud Shell and export this information to Cloud Storage on a daily basis.
- B. Create two configurations using gcloud config. Write a script that sets configurations as active, individually. For each configuration, use gcloud compute instances list to get a list of compute resources.
- C. Go to GCP Console and export this information to Cloud SQL on a daily basis.
- D. Create two configurations using gsutil config. Write a script that sets configurations as active, individually. For each configuration, use gsutil compute instances list to get a list of compute resources.
正解：B
解説：
gcloud compute instances list - list Google Compute Engine instances
gcloud compute instances list displays all Google Compute Engine instances in a project.
By default, instances from all zones are listed. The results can be narrowed down using a filter: -- filter="zone:( ZONE ... )".
https://cloud.google.com/sdk/gcloud/reference/compute/instances/list
質問 # 72
Your company uses BigQuery for data warehousing. Over time, many different business units in your company have created 1000+ datasets across hundreds of projects. Your CIO wants you to examine all datasets to find tables that contain an employee_ssn column. You want to minimize effort in performing this task. What should you do?
- A. Go to Data Catalog and search for employee_ssn in the search box.
- B. Write a shell script that uses the bq command line tool to loop through all the projects in your organization.
- C. Write a script that loops through all the projects in your organization and runs a query on INFORMATION_SCHEMA.COLUMNS view to find the employee_ssn column.
- D. Write a Cloud Dataflow job that loops through all the projects in your organization and runs a query on INFORMATION_SCHEMA.COLUMNS view to find employee_ssn column.
正解：A
解説：
Explanation
https://cloud.google.com/bigquery/docs/quickstarts/quickstart-web-ui?authuser=4
質問 # 73
You have a Google Cloud Platform account with access to both production and development projects. You need to create an automated process to list all compute instances in development and production projects on a daily basis. What should you do?
- A. Go to Cloud Shell and export this information to Cloud Storage on a daily basis.
- B. Create two configurations using gcloud config. Write a script that sets configurations as active, individually. For each configuration, use gcloud compute instances list to get a list of compute resources.
- C. Go to GCP Console and export this information to Cloud SQL on a daily basis.
- D. Create two configurations using gsutil config. Write a script that sets configurations as active, individually. For each configuration, use gsutil compute instances list to get a list of compute resources.
正解：B
質問 # 74
You have a Dockerfile that you need to deploy on Kubernetes Engine. What should you do?
- A. Create a docker image from the Dockerfile and upload it to Cloud Storage.
Create a Deployment YAML file to point to that image.
Use kubectl to create the deployment with that file. - B. Create a docker image from the Dockerfile and upload it to Container Registry.
Create a Deployment YAML file to point to that image.
Use kubectl to create the deployment with that file. - C. Use gcloud app deploy <dockerfilename>.
- D. Use kubectl app deploy <dockerfilename>.
正解：B
質問 # 75
You have one GCP account running in your default region and zone and another account running in a non- default region and zone. You want to start a new Compute Engine instance in these two Google Cloud Platform accounts using the command line interface. What should you do?
- A. Create two configurations using gcloud config configurations create [NAME].Run gcloud configurations listto start the Compute Engine instances.
- B. Activate two configurations using gcloud configurations activate [NAME].Run gcloud configurations listto start the Compute Engine instances.
- C. Activate two configurations using gcloud configurations activate [NAME].Run gcloud config listto start the Compute Engine instances.
- D. Create two configurations using gcloud config configurations create [NAME].Run gcloud config configurations activate [NAME]to switch between accounts when running the commands to start the Compute Engine instances.
正解：C
解説：
Explanation/Reference: https://cloud.google.com/sdk/gcloud/reference/config/configurations/activate
質問 # 76
You want to configure an SSH connection to a single Compute Engine instance for users in the dev1 group.
This instance is the only resource in this particular Google Cloud Platform project that the dev1 users should be able to connect to. What should you do?
- A. Enable block project wide keysfor the instance. Generate an SSH key for each user in the dev1 group. Distribute the keys to dev1 users and direct them to use their third-party tools to connect.
- B. Set metadata to enable-oslogin=truefor the instance. Set the service account to no service accountfor that instance. Direct them to use the Cloud Shell to ssh to that instance.
- C. Set metadata to enable-oslogin=truefor the instance. Grant the dev1 group the compute.osLogin role. Direct them to use the Cloud Shell to ssh to that instance.
- D. Enable block project wide keysfor the instance. Generate an SSH key and associate the key with that instance. Distribute the key to dev1 users and direct them to use their third-party tools to connect.
正解：D
解説：
Explanation/Reference: https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys
質問 # 77
You need to connect to one of your Compute Engine instances using SSH. You've already authenticated gcloud, however, you don't have an SSH key deployed yet. In the fewest steps possible, what's the easiest way to connect to the app?
- A. Create a key with the ssh-keygen command. Then use the gcloud compute ssh command.
- B. Create a key with the ssh-keygen command. Upload the key to the instance. Run gcloud compute instances list to get the IP address of the instance, then use the ssh command.
- C. Use the gcloud compute ssh command.
- D. Run gcloud compute instances list to get the IP address of the instance, then use the ssh command.
正解：C
質問 # 78
You've finally been given a new laptop, but you need to install all of the tools you need. You already installed the Cloud SDK, but none of the commands seem to be working correctly. What step did you likely forget?
- A. gcloud application_init
- B. gcloud config_list
- C. gcloud init
- D. gcloud config list
正解：C、D
質問 # 79
You are using Google Kubernetes Engine with autoscaling enabled to host a new application. You want to expose this new application to the public, using HTTPS on a public IP address. What should you do?
- A. Create a Kubernetes Service of type ClusterIP for your application. Configure the public DNS name of your application using the IP of this Service.
- B. Create a Kubernetes Service of type NodePort to expose the application on port 443 of each node of the Kubernetes cluster. Configure the public DNS name of your application with the IP of every node of the cluster to achieve load-balancing.
- C. Create a Kubernetes Service of type NodePort for your application, and a Kubernetes Ingress to expose this Service via a Cloud Load Balancer.
- D. Create a HAProxy pod in the cluster to load-balance the traffic to all the pods of the application. Forward the public traffic to HAProxy with an iptable rule. Configure the DNS name of your application using the public IP of the node HAProxy is running on.
正解：C
解説：
Reference:
https://cloud.google.com/kubernetes-engine/docs/tutorials/http-balancer
質問 # 80
Your company implemented BigQuery as an enterprise data warehouse. Users from multiple business units run queries on this data warehouse. However, you notice that query costs for BigQuery are very high, and you need to control costs. Which two methods should you use? (Choose two.)
- A. Split your BigQuery data warehouse into multiple data warehouses for each business unit.
- B. Split the users from business units to multiple projects.
- C. Change your BigQuery query model from on-demand to flat rate. Apply the appropriate number of slots to each Project.
- D. Create separate copies of your BigQuery data warehouse for each business unit.
- E. Apply a user- or project-level custom query quota for BigQuery data warehouse.
正解：C、E
解説：
https://cloud.google.com/bigquery/docs/custom-quotashttps://cloud.google.com/bigquery/pricing#flat_rate_prici
質問 # 81
You are managing several Google Cloud Platform (GCP) projects and need access to all logs for the past 60 days. You want to be able to explore and quickly analyze the log contents. You want to follow Google- recommended practices to obtain the combined logs for all projects. What should you do?
- A. Create a Stackdriver Logging Export with a Sink destination to a BigQuery dataset. Configure the table expiration to 60 days.
- B. Navigate to Stackdriver Logging and select resource.labels.project_id="*"
- C. Create a Stackdriver Logging Export with a Sink destination to Cloud Storage. Create a lifecycle rule to delete objects after 60 days.
- D. Configure a Cloud Scheduler job to read from Stackdriver and store the logs in BigQuery. Configure the table expiration to 60 days.
正解：A
解説：
Explanation
Navigate to Stackdriver Logging and select resource.labels.project_id=*. is not right.
Log entries are held in Stackdriver Logging for a limited time known as the retention period which is 30 days (default configuration). After that, the entries are deleted. To keep log entries longer, you need to export them outside of Stackdriver Logging by configuring log sinks.
Ref: https://cloud.google.com/blog/products/gcp/best-practices-for-working-with-google-cloud-audit-logging Configure a Cloud Scheduler job to read from Stackdriver and store the logs in BigQuery. Configure the table expiration to 60 days. is not right.
While this works, it makes no sense to use Cloud Scheduler job to read from Stackdriver and store the logs in BigQuery when Google provides a feature (export sinks) that does exactly the same thing and works out of the box.Ref: https://cloud.google.com/logging/docs/export/configure_export_v2 Create a Stackdriver Logging Export with a Sink destination to Cloud Storage. Create a lifecycle rule to delete objects after 60 days. is not right.
You can export logs by creating one or more sinks that include a logs query and an export destination.
Supported destinations for exported log entries are Cloud Storage, BigQuery, and Pub/Sub.Ref: https://cloud.google.com/logging/docs/export/configure_export_v2 Sinks are limited to exporting log entries from the exact resource in which the sink was created: a Google Cloud project, organization, folder, or billing account. If it makes it easier to exporting from all projects of an organication, you can create an aggregated sink that can export log entries from all the projects, folders, and billing accounts of a Google Cloud organization.Ref: https://cloud.google.com/logging/docs/export/aggregated_sinks Either way, we now have the data in Cloud Storage, but querying logs information from Cloud Storage is harder than Querying information from BigQuery dataset. For this reason, we should prefer Big Query over Cloud Storage.
Create a Stackdriver Logging Export with a Sink destination to a BigQuery dataset. Configure the table expiration to 60 days. is the right answer.
You can export logs by creating one or more sinks that include a logs query and an export destination.
Supported destinations for exported log entries are Cloud Storage, BigQuery, and Pub/Sub.Ref: https://cloud.google.com/logging/docs/export/configure_export_v2 Sinks are limited to exporting log entries from the exact resource in which the sink was created: a Google Cloud project, organization, folder, or billing account. If it makes it easier to exporting from all projects of an organication, you can create an aggregated sink that can export log entries from all the projects, folders, and billing accounts of a Google Cloud organization.Ref: https://cloud.google.com/logging/docs/export/aggregated_sinks Either way, we now have the data in a BigQuery Dataset. Querying information from a Big Query dataset is easier and quicker than analyzing contents in Cloud Storage bucket. As our requirement is to Quickly analyze the log contents, we should prefer Big Query over Cloud Storage.
Also, You can control storage costs and optimize storage usage by setting the default table expiration for newly created tables in a dataset. If you set the property when the dataset is created, any table created in the dataset is deleted after the expiration period. If you set the property after the dataset is created, only new tables are deleted after the expiration period.For example, if you set the default table expiration to 7 days, older data is automatically deleted after 1 week.Ref: https://cloud.google.com/bigquery/docs/best-practices-storage
質問 # 82
You want to configure 10 Compute Engine instances for availability when maintenance occurs. Your requirements state that these instances should attempt to automatically restart if they crash. Also, the instances should be highly available including during system maintenance. What should you do?
- A. Create an instance template for the instances. Set the 'Automatic Restart' to on. Set the 'On-host maintenance' to Migrate VM instance. Add the instance template to an instance group.
- B. Create an instance group for the instances. Set the 'Autohealing' health check to healthy (HTTP).
- C. Create an instance template for the instances. Set 'Automatic Restart' to off. Set 'On-host maintenance' to Terminate VM instances. Add the instance template to an instance group.
- D. Create an instance group for the instance. Verify that the 'Advanced creation options' setting for 'do not retry machine creation' is set to off.
正解：A
解説：
Create an instance template for the instances so VMs have same specs. Set the "":Automatic Restart' to on to VM automatically restarts upon crash. Set the ""On-host maintenance' to Migrate VM instance. This will take care of VM during maintenance window. It will migrate VM instance making it highly available Add the instance template to an instance group so instances can be managed.
* onHostMaintenance: Determines the behavior when a maintenance event occurs that might cause your instance to reboot.
* [Default] MIGRATE, which causes Compute Engine to live migrate an instance when there is a maintenance event.
* TERMINATE, which stops an instance instead of migrating it.
* automaticRestart: Determines the behavior when an instance crashes or is stopped by the system.
* [Default] true, so Compute Engine restarts an instance if the instance crashes or is stopped.
* false, so Compute Engine does not restart an instance if the instance crashes or is stopped.
Enabling automatic restart ensures that compute engine instances are automatically restarted when they crash.
And Enabling Migrate VM Instance enables live migrates i.e. compute instances are migrated during system maintenance and remain running during the migration.
Automatic Restart If your instance is set to terminate when there is a maintenance event, or if your instance crashes because of an underlying hardware issue, you can set up Compute Engine to automatically restart the instance by setting the automaticRestart field to true. This setting does not apply if the instance is taken offline through a user action, such as calling sudo shutdown, or during a zone outage.Ref: https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options#autorestart Enabling the Migrate VM Instance option migrates your instance away from an infrastructure maintenance event, and your instance remains running during the migration. Your instance might experience a short period of decreased performance, although generally, most instances should not notice any difference. This is ideal for instances that require constant uptime and can tolerate a short period of decreased performance.Ref: https://cloud.google.com/compute/docs/instances/setting-instance-scheduling-options#live_mi
質問 # 83
......
時間限定！今すぐ無料アクセスAssociate-Cloud-Engineer練習問題：https://drive.google.com/open?id=11gNEI7TOOoiu_94A7XWe65FlVLKZ99Mv
最適なAssociate-Cloud-Engineer試験学習資料と準備材料を提供しています：https://jp.fast2test.com/Associate-Cloud-Engineer-premium-file.html