Associate-Cloud-Engineer試験無料問題集「Google Associate Cloud Engineer 認定」

A. 1. In Stackdriver Logging, create a filter to view only Compute Engine logs.2. Click Create Export.3.
Choose BigQuery as Sink Service, and the platform-logs dataset as Sink Destination.

B. 1. In Stackdriver Logging, create a logs export with a Cloud Pub/Sub topic called logs as a sink.2.
Create a Cloud Function that is triggered by messages in the logs topic.3. Configure that Cloud Function to drop logs that are not from Compute Engine and to insert Compute Engine logs in the platform-logs dataset.

C. 1. Create a Cloud Function that has the BigQuery User role on the platform-logs dataset.2. Configure this Cloud Function to create a BigQuery Job that executes this query:INSERT INTO dataset.platform- logs (timestamp, log)SELECT timestamp, log FROM compute.logsWHERE timestamp > DATE_SUB (CURRENT_DATE(), INTERVAL 1 DAY)3. Use Cloud Scheduler to trigger this Cloud Function once a day.

D. 1. Give the BigQuery Data Editor role on the platform-logs dataset to the service accounts used by your instances.2. Update your instances' metadata to add the following value: logs-destination: bq://platform- logs.

A. kubectl delete pod nginx-84748895c4-k6bzl -no-restart 2

B. kubectl delete deployment nginx

C. kubectl delete inginx

D. kubectl delete -deployment=nginx

A. Write a lifecycle management rule in XML and push it to the bucket with gsutil lifecycle set config-xml- file.

B. Write a script that runs gsutil Is -| - gs://myapp-gcp-ace-logs/** to find and remove items older than 90 days. Schedule the script with cron.

C. Write a script that runs gsutil Is -Ir gs://myapp-gcp-ace-logs/** to find and remove items older than 90 days. Repeat this process every morning.

D. Write a lifecycle management rule in JSON and push it to the bucket with gsutil lifecycle set config- json-file.

A. In the Instance Template, add a startup script that sends a heartbeat to the metadata server.

B. In the Instance Template, add the label 'health-check'.

C. Select Multi-Zone instead of Single-Zone when creating the Managed Instance Group.

D. Create a health check on port 443 and use that when creating the Managed Instance Group.

A. When creating the VM, use machine type n1-standard-96.

B. Create the VM using Compute Engine default settings. Use gcloud to modify the running instance to have 96 vCPUs.

C. Start the VM using Compute Engine default settings, and adjust as you go based on Rightsizing Recommendations.

D. When creating the VM, use Intel Skylake as the CPU platform.

A. 1. Deploy your application on Cloud Run on GKE with the connectivity set to Internal.2. Create a Cloud Pub/Sub subscription for that topic.3. In the same Google Kubernetes Engine cluster as your application, deploy a container that takes the messages and sends them to your application.

B. 1. Grant the Pub/Sub Subscriber role to the service account used by Cloud Run.2. Create a Cloud Pub
/Sub subscription for that topic.3. Make your application pull messages from that subscription.

C. 1. Create a Cloud Function that uses a Cloud Pub/Sub trigger on that topic.2. Call your application on Cloud Run from the Cloud Function for every message.

D. 1. Create a service account.2. Give the Cloud Run Invoker role to that service account for your Cloud Run application.3. Create a Cloud Pub/Sub subscription that uses that service account and uses your Cloud Run application as the push endpoint.

A. Run a select count (*) to get an idea of how many records your query will look through. Then convert that number of rows to dollars using the Pricing Calculator.

B. Use the command line to run a dry run query to estimate the number of bytes returned. Then convert that bytes estimate to dollars using the Pricing Calculator.

C. Use the command line to run a dry run query to estimate the number of bytes read. Then convert that bytes estimate to dollars using the Pricing Calculator.

D. Arrange to switch to Flat-Rate pricing for this query, then move back to on-demand.

A. 1. Using Cloud VPN or Interconnect, create a tunnel to a VPC in GCP.2. Use Cloud Router to create a custom route advertisement for 199.36.153.4/30. Announce that network to your on-premises network through the VPN tunnel.3. In your on-premises network, configure your DNS server to resolve *.googleapis.com as a CNAME to restricted.googleapis.com.

B. 1. Using Cloud VPN, create a VPN tunnel to a Virtual Private Cloud (VPC) in Google Cloud Platform (GCP).2. In this VPC, create a Compute Engine instance and install the Squid proxy server on this instance.3. Configure your servers to use that instance as a proxy to access Cloud Storage.

C. 1. Use Migrate for Compute Engine (formerly known as Velostrata) to migrate those servers to Compute Engine.2. Create an internal load balancer (ILB) that uses storage.googleapis.com as backend.
3. Configure your new instances to use this ILB as proxy.

D. 1. Use nslookup to get the IP address for storage.googleapis.com.2. Negotiate with the security team to be able to give a public IP address to the servers.3. Only allow egress traffic from those servers to the IP addresses for storage.googleapis.com.

A. 1. Verify that you are assigned the Organizational Administrator IAM role for this project.
2. Locate the project in the GCP console, enter the project ID and then click Shut down.

B. 1. Verify that you are assigned the Project Owners IAM role for this project.
2. Switch to the project in the GCP console, locate the resources and delete them.

C. 1. Verify that you are assigned the Organizational Administrators IAM role for this project.
2. Switch to the project in the GCP console, locate the resources and delete them.

D. 1. Verify that you are assigned the Project Owners IAM role for this project.
2. Locate the project in the GCP console, click Shut down and then enter the project ID.

A. Verify that the instance template being used by the instance group contains valid syntax. Delete any persistent disks with the same name as instance names. Set the disks.autoDelete property to true in the instance template.

B. Create an instance template that contains valid syntax which will be used by the instance group. Delete any persistent disks with the same name as instance names.

C. Create an instance template that contains valid syntax that will be used by the instance group. Verify that the instance name and persistent disk name values are not the same in the template.

D. Delete the current instance template and replace it with a new instance template. Verify that the instance name and persistent disk name values are not the same in the template. Set the disks.autoDelete property to true in the instance template.

A. Create a Metadata entry on the Compute Engine page with key compute/zone and value europe-west1- d.

B. In the Settings page for Compute Engine under Default location, set the zone to europe-west1-d.

C. In the CLI installation directory, create a file called default.conf containing zone=europe-west1-d.

D. Set the europe-west1-d zone as the default zone using the gcloud config subcommand.

A. Change the region property setting in the existing App Engine application from us-central to asia- northeast1.

B. Create a second App Engine application in the existing GCP project and specify asia-northeast1 as the region to serve your application.

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.

A. Create a Shared VPC network between both projects. Grant the VM Service Account the role Storage Object Creator on corp-iot-insights.

B. Move both projects under the same folder.

C. Grant the VM Service Account the role Storage Object Creator on corp-aggregate-reports-storage.

D. Make corp-aggregate-reports-storage public and create a folder with a pseudo-randomized suffix name.Share the folder with the IoT team.

A. Download your Cloud Identity user account key. Place the key file in a folder on your machine where gcloud CLI can find it.

B. Run gcloud config set compute/zone $my_zone to set the default zone for gcloud CLI.

C. Run gcloud config set project $my_project to set the default project for gcloud CLI.

D. Run gcloud auth login, enter your login credentials in the dialog window, and paste the received login token to gcloud CLI.

E. Create a Google Cloud service account, and download the service account key. Place the key file in a folder on your machine where gcloud CLI can find it.