NEW
Font size
WorksheetsGCP VMs
Total questions: 11
Worksheet time: 2hrs 50mins
You need to create an autoscaling managed instance group for an HTTPS web application. You want to make sure that unhealthy VMs are recreated. What should you do?
Create a health check on port 443 and use that when creating the Managed Instance Group.
Select Multi-Zone instead of Single-Zone when creating the Managed Instance Group.
In the Instance Template, add the label 'health-check'.
In the Instance Template, add a startup script that sends a heartbeat to the metadata server.
An application generates daily reports in a Compute Engine virtual machine (VM). The VM is in the project corp-iot-insights. Your team operates only in the project corp-aggregate-reports and needs a copy of the daily exports in the bucket corp-aggregate-reports-storage. You want to configure access so that the daily reports from the VM are available in the bucket corp-aggregate-reports-storage and use as few steps as possible while following Google-recommended practices. What should you do?
Move both projects under the same folder.
Grant the VM Service Account the role Storage Object Creator on corp-aggregate-reports-storage.
Create a Shared VPC network between both projects. Grant the VM Service Account the role Storage Object Creator on corp-iot-insights.
Make corp-aggregate-reports-storage public and create a folder with a pseudo-randomized suffix name. Share the folder with the IoT team.
You are monitoring an application and receive user feedback that a specific error is spiking. You notice that the error is caused by a Service Account having insufficient permissions. You are able to solve the problem but want to be notified if the problem recurs. What should you do?
In the Log Viewer, filter the logs on severity 'Error' and the name of the Service Account.
Create a sink to BigQuery to export all the logs. Create a Data Studio dashboard on the exported logs.
Create a custom log-based metric for the specific error to be used in an Alerting Policy.
Grant Project Owner access to the Service Account.
You have a virtual machine that is currently configured with 2 vCPUs and 4 GB of memory. It is running out of memory. You want to upgrade the virtual machine to have 8 GB of memory. What should you do?
Rely on live migration to move the workload to a machine with more memory.
Use gcloud to add metadata to the VM. Set the key to required-memory-size and the value to 8 GB.
Stop the VM, change the machine type to n1-standard-8, and start the VM.
Stop the VM, increase the memory to 8 GB, and start the VM.
You want to run a single caching HTTP reverse proxy on GCP for a latency-sensitive website. This specific reverse proxy consumes almost no CPU. You want to have a 30-GB in-memory cache, and need an additional 2 GB of memory for the rest of the processes. You want to minimize cost. How should you run this reverse proxy?
Create a Cloud Memorystore for Redis instance with 32-GB capacity.
Run it on Compute Engine, and choose a custom instance type with 6 vCPUs and 32 GB of memory.
Package it in a container image, and run it on Kubernetes Engine, using n1-standard-32 instances as nodes.
Run it on Compute Engine, choose the instance type n1-standard-1, and add an SSD persistent disk of 32 GB.
You need to manage a third-party application that will run on a Compute Engine instance. Other Compute Engine instances are already running with default configuration. Application installation files are hosted on Cloud Storage. You need to access these files from the new instance without allowing other virtual machines (VMs) to access these files. What should you do?
Create the instance with the default Compute Engine service account. Grant the service account permissions on Cloud Storage.
Create the instance with the default Compute Engine service account. Add metadata to the objects on Cloud Storage that matches the metadata on the new instance.
Create a new service account and assign this service account to the new instance. Grant the service account permissions on Cloud Storage.
Create a new service account and assign this service account to the new instance. Add metadata to the objects on Cloud Storage that matches the metadata on the new instance.
You will have several applications running on different Compute Engine instances in the same project. You want to specify at a more granular level the service account each instance uses when calling Google Cloud APIs. What should you do?
When creating the instances, specify a Service Account for each instance.
When creating the instances, assign the name of each Service Account as instance metadata.
After starting the instances, use gcloud compute instances update to specify a Service Account for each instance.
After starting the instances, use gcloud compute instances update to assign the name of the relevant Service Account as instance metadata.
You have deployed multiple Linux instances on Compute Engine. You plan on adding more instances in the coming weeks. You want to be able to access all of these instances through your SSH client over the internet without having to configure specific access on the existing and new instances. You do not want theCompute Engine instances to have a public IP. What should you do?
Configure Cloud Identity-Aware Proxy for HTTPS resources.
Configure Cloud Identity-Aware Proxy for SSH and TCP resources
Create an SSH keypair and store the public key as a project-wide SSH Key.
Create an SSH keypair and store the private key as a project-wide SSH Key.
You are about to deploy a new Enterprise Resource Planning (ERP) system on Google Cloud. The application holds the full database in-memory for fast data access, and you need to configure the most appropriate resources on Google Cloud for this application. What should you do?
Provision preemptible Compute Engine instances.
Provision Compute Engine instances with GPUs attached.
Provision Compute Engine instances with local SSDs attached.
Provision Compute Engine instances with M1 machine type.
Your company has workloads running on Compute Engine and on-premises. The Google Cloud Virtual Private Cloud (VPC) is connected to your WAN over aVirtual Private Network (VPN). You need to deploy a new Compute Engine instance and ensure that no public Internet traffic can be routed to it. What should you do?
Create the instance without a public IP address.
Create the instance with Private Google Access enabled.
Create a deny-all egress firewall rule on the VPC network.
Create a route on the VPC to route all traffic to the instance over the VPN tunnel.
You have been asked to create robust Virtual Private Network (VPN) connectivity between a new Virtual Private Cloud (VPC) and a remote site. Key requirements include dynamic routing, a shared address space of 10.19.0.1/22, and no overprovisioning of tunnels during a failover event. You want to follow Google- recommended practices to set up a high availability Cloud VPN. What should you do?
Use a custom mode VPC network, configure static routes, and use active/passive routing.
Use an automatic mode VPC network, configure static routes, and use active/active routing.
Use a custom mode VPC network, use Cloud Router border gateway protocol (BGP) routes, and use active/passive routing.
Use an automatic mode VPC network, use Cloud Router border gateway protocol (BGP) routes, and configure policy-based routing.
